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
Attn: PMP® or CAPM® Certified Professionals.
Get your Advanced Master Certificate in IS/IT Project Management or Applied Project Management, 100% online from Villanova. Learn more now and save $945! ERP Evaluation Toolkit. Focus analysts have gathered all of the information you need into one definitive document. Explore all aspects of the ERP market, and get insight into specific areas of interest. Decision-making tools and worksheets also included. ERP is a strategic investment. Download your free in-depth ERP Toolkit now. A CRM solution can have an enormously positive effect on your business's bottom line, but a lot can go wrong during a rollout if you haven't planned properly. Download the CRM Evaluation and Implementation Toolkit, from InsideCRM, to learn more about hosted CRM, 10 Steps to a Successful CRM Implementation and more.
|
| ||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||