Saturday, September 24th, 2016
The first step in order to make good estimations, is understand clearly the difference between estimates, targets, commitments and plans:
A statement of probability, a prediction, a tentative or preliminary calculation of the cost of a project.
A description of a desirable business objective.
A promise to deliver defined functionality at a specific level of quality by a certain date.
A statement of how and when a project’s objectives are to be achieved, by showing the major products, milestones, activities and resources required on the project.
– 1st sprint: 30 days, two people: prototype+proof of concept
– 2nd sprint: 30 days, three people: user histories 1, 2 and 3
– 3rd sprint: 30 days, three people: user histories 4, 5″
Summary: An Estimate is for decision support. Numbers without probabilities aren’t Estimates. We have to take into account that our estimates don’t become commitments; they are two different things.
Depending of how different are the Estimate and the Target, the Project Plan will need to account a different level of risk. The more the gap, the bigger the risk.
- The post Software project estimates – and targets and commitments.
- The book Software Estimation: Demystifying the Black Art, by Steve McConnell.
- The post Separate Estimating from Committing, by Mike Cohn.