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
CA Technologies' Innovation Management survey is a study into the barriers to innovation success and the measures companies are taking to improve performance. Each survey respondent will receive a complimentary copy of the report containing the survey's results. Please participate now!
Build and deploy interactive reports and dashboards — without any hidden costs. Our in-the-cloud free trial lets you see for yourself — no download required. SAP Crystal Reports Server 60-day Free Trial
Enable Agile Process; Support Agile Teams Enterprise hardware and software evolve faster than your customers can consume new versions and features. Overcome this gap: learn how professional services can boost product consumption and speed repurchasing in TSIA/Compuware white paper. Read now Packaged Services Success: Join us on Sept 8 for this Free Webinar as RTM Consulting and Tenrox discuss the competitive and financial benefits of Leveraging Automation to meet the Rising Demand for Productized Professional Services. EARN 1 PDU. Register Here Today to receive a Free White Paper.
|
| |||||||||||||||||||||||||||||||||
|
| |||||||||||||||||||||||||||||||||||