Much has been made of the advantages of agile project management, yet many organizations are slow to embrace it. Part of the reason is that they misinterpret “agile” as “winging it.” Another reason is that they feel that agile PM is for software development houses not catering to specific customer requirements. A typical comment is: “Maybe a software shop can afford to let the scope evolve, but we need full specific requirements from our customers right up front in order to know how to estimate or bill properly. We can’t afford to guess at the outcome.”
Perhaps agile PM is misunderstood. Or maybe it needs to be made more…shall we say, agile. That way, organizations will accept it more broadly. To start with, let’s recap the main characteristics of agile PM:
Piecemeal iterations with fixed time and cost, but evolving scope as learnings emerge
Rapid and ongoing delivery of value (i.e. working software) throughout the project
Close and frequent collaboration between developers and customers to minimize misunderstandings
Developers are trusted to deliver to customer needs; they are told what is needed, not how to accomplish it
Collectively, these characteristics serve three purposes: