       |
||||||||||||||||||||||||||||||||
Why Traditional Project Planning Often Fails |
||||||||||||||||||||||||||||||||
|
Home > Articles >
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
"Selecting the Right Requirements Management Tool – Or Maybe None Whatsoever" – Get your free copy of this independent report by Forrester Research, compliments of MKS.
Ever tried to explain what you do to your Mom? It's not always easy…and "not easy," is not good. So, for those out there struggling to explain Quality Management, here's a quick 3 minute video to make life, well, a little easier. View Now! Need to gain control of evolving business requirements? Want to drive clarity and context across the software delivery lifecycle? Watch this brief video discussing "Creating Value through Requirements Definitions." Find out about challenges that plague organizations and techniques, processes and tools to use to visually define, elaborate, collaboratively validate, and effectively manage your requirements. Learn how to develop a measurement program to track project management performance and the impact it has on your organization with PM College's latest white paper, Mastering Performance Measurement!
|
 sponsors
vendor offers
vendor events
| ||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||
