Why Traditional Project Planning Often Fails

Home  >  Articles  > 







Why Traditional Project Planning Often Fails

by Doug DeCarlo

September 4, 2007


A colleague of mine, Ravi Mohan, founder of ProjectScape once quipped, “Your project plan is obsolete even before you hit the print button.” Ravi was referring to traditional project planning as applied to software development projects.
 
I accepted his pronouncement as intuitively obvious and never gave it much more thought until the other day when I happened to be leafing through Mike Cohn’s excellent book, entitled Agile Estimating and Planning. (1)
 
Here’s a summary of Mike’s four reasons why traditional approaches to planning often fail:
 
1. Planning is by activity rather than by feature
In traditional approaches, work breakdown structures are based on activities.



Please login/register to read the entire article.





sponsored announcements and special offers
Position yourself for success with Florida Tech's MBA in Project Management, accredited by PMI® GAC. There's no GMAT or GRE required, and you'll also qualify for 1,500 experience hours that can be used toward earning a prestigious PMP® credential.
The Enterprise PPM and PMO Blue Print. Learn strategies and best practices for taking a top-down, enterprise-wide approach to PPM processes and system deployment. To learn more and register now, click here!



"It's no coincidence that in no known language does the phrase "As pretty as an airport" appear."
- Douglas Adams