Mark C. Layton, aka "Mr. Agile¯(TM)," is a veteran of more than 25 years in the project and program management field. He is a Certified Scrum Trainer, a PMP, and an MBA. He holds multiple scrum scaling certifications and is the founder of Platinum Edge, LLC. Steven J. Ostermiller is a coach, mentor, and trainer empowering leaders and teams to become more agile. He holds CSP and PMP designations.
Modernizing Project Management
IN THIS CHAPTER
Understanding why project management needs to change
Finding out about agile project management
Agile project management is a style of project management that focuses on early delivery of business value, continuous improvement of the project's product and processes, scope flexibility, team input, and delivering well-tested products that reflect customer needs.
In this chapter, you find out why agile processes emerged as an approach to software development project management in the mid-1990s and why agile methodologies have caught the attention of project managers, customers who invest in the development of new software, and executives whose companies fund software development departments. This chapter also explains the advantages of agile methodologies over long-standing approaches to project management.
Project Management Needed a Makeover
A project is a planned program of work that requires a definitive amount of time, effort, and planning to complete. Projects have goals and objectives and often must be completed in some fixed period of time and within a certain budget.
Because you are reading this book, it's likely that you are either a project manager or someone who initiates projects, works on projects, or is affected by projects in some way.
Agile approaches are a response to the need to modernize project management. To understand how agile approaches are revolutionizing projects, it helps to know a little about the history and purpose of project management and the issues that projects face today.
The origins of modern project management
Projects have been around since ancient times. From the Great Wall of China to the Mayan pyramids at Tikal, from the invention of the printing press to the invention of the Internet, people have accomplished endeavors big and small in projects.
As a formal discipline, project management as we know it has only been around since the middle of the twentieth century. Around the time of World War II, researchers around the world were making major advances in building and programming computers, mostly for the United States military. To complete those projects, they started creating formal project management processes. The first processes were based on step-by-step manufacturing models the United States military used during World War II.
People in the computing field adopted these step-based manufacturing processes because early computer-related projects relied heavily on hardware, with computers that filled up entire rooms. Software, by contrast, was a smaller part of computer projects. In the 1940s and 1950s, computers might have thousands of physical vacuum tubes but fewer than 30 lines of programming code. The 1940s manufacturing process used on these initial computers is the foundation of the project management methodology known as waterfall.
In 1970, a computer scientist named Winston Royce wrote "Managing the Development of Large Software Systems," an article for the IEEE that described the phases in the waterfall methodology. The term waterfall was coined later, but the phases, even if they are sometimes titled differently, are essentially the same as originally defined by Royce:
- 1. Requirements
- 2. Design
- 3. Development
- 4. Integration
- 5. Testing
- 6. Deployment
On waterfall projects, you move to the next phase only when the prior one is complete - hence, the name waterfall.
Pure waterfall project management - completing each step in full before moving to the next step - is actually a misinterpretation of Royce's suggestions. Royce identified that this approach was inherently risky and recommended developing and testing within iterations to create products - suggestions that were overlooked by many organizations that adopted the waterfall methodology.
SOFTWARE PROJECT SUCCESS AND FAILURE
Unfortunately, the stagnation in traditional project management approaches is catching up with the software industry. In 2015, a software statistical company called the Standish Group did a study on the success and failure rates of 10,000 projects in the US. The results of the study showed that
- 29 percent of traditional projects failed outright. The projects were cancelled before they finished and did not result in any product releases. These projects delivered no value whatsoever.
- 60 percent of traditional projects were challenged. The projects were completed, but they had gaps between expected and actual cost, time, quality, or a combination of these elements. The average difference between the expected and actual project results - looking at time, cost, and features not delivered - was well over 100 percent.
- 11 percent of projects succeeded. The projects were completed and delivered the expected product in the originally expected time and budget.
Of the hundreds of billions of dollars spent on application development projects in the US alone, billions of dollars were wasted on projects that never deployed a single piece of functionality.
The waterfall methodology was the most common project management approach in software development until it was surpassed by improved approaches based on agile techniques around 2008.
The problem with the status quo
Computer technology has, of course, changed a great deal since the last century. Many people have a computer on their wrist with more power, memory, and capabilities than the largest, most expensive machine that existed when people first started using waterfall methodologies.
At the same time, the people using computers have changed as well. Instead of creating behemoth machines with minimal programs for a few researchers and the military, people create hardware and software for the general public. In many countries, almost everyone uses a computer, directly or indirectly, every day. Software runs our cars, our appliances, our homes; it provides our daily information and daily entertainment. Even young children use computers - a 2-year-old is almost more adept with the iPhone than her parents. The demand for newer, better software products is constant.
Somehow, during all this growth of technology, processes were not left behind. Software developers are still using project management methodologies from the 1950s, and all these approaches were derived from manufacturing processes meant for the hardware-heavy computers of the mid-twentieth century.
Today, traditional projects that do succeed often suffer from one problem: scope bloat, the introduction of unnecessary product features in a project.
Think about the software products you use every day. For example, the word-processing program we're typing on right now has many features and tools. Even though we write with this program every day, we use only some of the features all the time. We use other elements less frequently. And we have never used quite a few tools - and come to think of it, we don't know anyone else who has used them, either. The features that few people use are the result of scope bloat.
Scope bloat appears in all kinds of software, from complex enterprise applications to websites that everyone uses. Figure 1-1 shows data from a Standish Group study that illustrates just how common scope bloat is. In the figure, you can see that 64 percent of requested features are rarely or never used.
Copyright 2011 Standish Group
FIGURE 1-1: Actual use of requested software features.
The numbers in Figure 1-1 illustrate an enormous waste of time and money. That waste is a direct result of traditional project management processes that are unable to accommodate change. Project managers and stakeholders know that change is not welcome mid-project, so their best chance of getting a potentially desirable feature is at the start of a project. Therefore, they ask for
- Everything they need
- Everything they think they may need
- Everything they want
- Everything they think they may want
The result is the bloat in features that results in the statistics in Figure 1-1.
The problems associated with using outdated management and development approaches are not trivial. These problems waste billions of dollars a year. The billions of dollars lost in project failure in 2015 (see the sidebar, "Software project success and failure") could equate to millions of jobs around the world.
Over the past two decades, people working on projects have recognized the growing problems with traditional project management and have been working to create a better model: agile project management.
Introducing Agile Project Management
The seeds for agile techniques have been around for a long time. In fact, agile values, principles, and practices are simply a codification of common sense. Figure 1-2 shows a quick history of agile project management, dating to the 1930s with Walter Sherwart's Plan-Do-Study-Act (PDSA) approach to project quality.
FIGURE 1-2: Agile project management timeline.
In 1986, Hirotaka Takeuchi and Ikujiro Nonaka published an article...