Why Traditional Project Planning Often Fails
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. Understandably, the project manager becomes a taskmaster, driven to focus on task completion. But completed tasks (or activities if you prefer) do not necessarily equate to value in the eyes of the customer. Delivering value early and often is a fundamental tenant of agile project management. (This is the underlying reason why “Results Orientation” is one of the 10 Shared Values of eXtreme Project Management (see Happy Clients).
Moreover, in using traditional methods, one could complete all the activities and not necessarily deliver the desired functions and features. Moreover, planning by activity instead of by feature is a leading
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"Get your facts first, and then you can distort them as much as you please." - Mark Twain |




