The Project Manager's Guide to Mastering Agile
Principles and Practices for an Adaptive Approach
Charles G. Cobb
- English
- ePUB (mobile friendly)
- Available on iOS & Android
The Project Manager's Guide to Mastering Agile
Principles and Practices for an Adaptive Approach
Charles G. Cobb
About This Book
Streamline project workflow with expert agile implementation
The Project Management Profession is beginning to go through rapid and profound transformation due to the widespread adoption of agile methodologies. Those changes are likely to dramatically change the role of project managers in many environments as we have known them and raise the bar for the entire project management profession; however, we are in the early stages of that transformation and there is a lot of confusion about the impact it has on project managers:
- There are many stereotypes and misconceptions that exist about both Agile and traditional plan-driven project management,
- Agile and traditional project management principles and practices are treated as separate and independent domains of knowledge with little or no integration between the two and sometimes seen as in conflict with each other
- Agile and "Waterfall" are thought of as two binary, mutually-exclusive choices and companies sometimes try to force-fit their business and projects to one of those extremes when the right solution is to fit the approach to the project
It's no wonder that many Project Managers might be confused by all of this! This book will help project managers unravel a lot of the confusion that exists; develop a totally new perspective to see Agile and traditional plan-driven project management principles and practices in a new light as complementary to each other rather than competitive; and learn to develop an adaptive approach to blend those principles and practices together in the right proportions to fit any situation.
There are many books on Agile and many books on traditional project management but what's very unique about this book is that it takes an objective approach to help you understand the strengths and weaknesses of both of those areas to see how they can work synergistically to improve project outcomes in any project. The book includes discussion topics, real world case studies, and sample enterprise-level agile frameworks that facilitate hands-on learning as well as an in-depth discussion of the principles behind both Agile and traditional plan-driven project management practices to provide a more thorough level of understanding.
Frequently asked questions
Chapter 1
Introduction to Agile Project Management
- Project Management Institute (PMI)Ā® studies concluded that from 2008 to 2013, the use of agile practices tripled.1
- According to a 2013 survey conducted by VersionOne:2
- 88% of the respondents say that their organizations are practicing agile development, up from 84% in 2012 and 80% in 2011.
- Over half of the respondents (52%) are using agile software to manage the majority of their projects.
- 88% say that they are at least āknowledgeableā about agile software development techniques, up 7% from the previous year.
- This trend has been going on for some time. As early as 2007, a Forrester survey reported:3
- ā26% are already using agile and an additional 42% are aware.ā
- āAdoption of agile increased 56% from 17% in 2006, to 26% in 2007.ā
- āAwareness increased 45% from 29% in 2006, to 42% in 2007.ā
The Chasm in Project Management Philosophies
- There has been only a limited amount of progress on developing a more integrated approach to project management that embraces both agile and traditional plan-driven project management principles and practices.
- Many people seem to see agile and project management principles and practices as competitive approaches that are in conflict with each other, and they are essentially treated as two separate and independent domains of knowledge.
- Considerable polarization between these two communities is based in some part on myths, stereotypes, and misconceptions about what agile and project management is.
- The predominant quality management approach was based on final inspection of products prior to shipping them to the customer and rejecting any that didn't meet quality standards. It's easy to see how that approach was inefficient, because it resulted in a lot of unnecessary rework to correct problems after the fact, and it also wasn't that effective because any inspection approach is based on sampling, and it is impractical to do a 100% sample. For that reason, it can result in mediocre quality.
- A far better approach was to go upstream in the process and eliminate defects at the source by designing the process to be inherently more reliable and free of defects and build quality into the inherent design of the products. That didn't mean that the prior emphasis on quality control and inspection was obsolete and eliminated; it was just not the only way to manage quality and wasn't the most effective approach in all situations.
- To be successful in more uncertain environments, project managers need to be able to take an adaptive approach that is appropriate to the level of uncertainty in the project and integrate quality into the process rather than relying on final acceptance testing at the end of the project to validate the product that is being produced.
- They also need to give up some of the control that has become associated with the project management professionāin some cases, they may need to become more of a coach and a consultant to influence others rather than being in absolute control of a project.
The Evolution of Agile and Waterfall
- It makes it sound like there are only two binary, mutually exclusive choices, agile and waterfall.
- The meaning of the words agile and waterfall are typically not well-defined and are used very loosely.