The book starts describing main problems of the traditional activity-based planning:
- activities are estimated considering that each developers spend all of work time on the activity, but this never happen in reality.
- multitasking appears as a way to do all faster, but it really increase the time in which an activity is executed;
- there is rarely, if ever, enough time to do everything, so it is necessary to estimate with priorities;
- when estimating we have to consider the uncertainty, so we should express the end date as a range of time.
Probably the most important reason of the activity-based planning failure is that it consider only activities and doesn’t consider features. A feature is the most important element that represents a real value for the customers.
The Agile approach to planning projects is the solution.
The estimation of an agile project gives most importance to the features that have to be implemented in the project....Continua