Agile Estimation Foundations
Agile Estimation Foundations covers key principles and techniques for accurate project planning in agile settings.
Agile Estimation Foundations is the set of concepts describing how agile teams gauge the size or effort involved in a backlog item, providing input that feeds into prioritization, planning, and the team's understanding of how much work it can realistically take on within a given delivery cycle. Where prioritization determines the order in which items should be addressed, estimation provides one of the inputs prioritization methods such as weighted shortest job first depend on, alongside informing how a team paces its own workload across iterations.
A central distinction in this foundation is between relative estimation, which compares items against one another rather than measuring them in fixed units, and absolute estimation, which attempts to state a specific duration or effort directly. Agile approaches frequently favor relative estimation for its practical advantages, but both approaches remain part of the broader estimation vocabulary, alongside the collaborative techniques teams use to actually arrive at an estimate and the ongoing acceptance that any estimate carries a degree of uncertainty.
The General Concept of Estimation
Agile Estimation Definition
Agile estimation is the practice of judging how much effort or time a given backlog item is likely to require, providing an input to planning and prioritization without claiming the precision of an exact measurement.
Work Estimate Definition
A work estimate is the specific judgment produced by the estimation process for a given backlog item, representing the team's current best understanding of its size rather than a guaranteed or committed figure.
Relative Versus Absolute Approaches
Relative Estimation Definition
Relative estimation compares a backlog item's size against other items rather than assigning it a fixed unit of time, based on the observation that people are often more consistent at judging relative size than at predicting exact durations.
Absolute Estimation Definition
Absolute estimation assigns a backlog item a specific quantity, typically a duration, intended to directly represent how long the item is expected to take, in contrast to the comparative approach used by relative estimation.
Story Point Definition
A story point is a unit used in relative estimation to express a backlog item's size on a comparative scale, with no fixed conversion to a specific duration, allowing teams to compare items to one another without committing to an absolute time prediction.
Ideal Time Definition
Ideal time is a form of absolute estimation expressing how long a task would take if worked on without interruption, distinguished from elapsed calendar time, which includes the interruptions and competing demands a team actually experiences.
Practical Estimation Techniques
Estimation Scale Definition
An estimation scale is a defined, bounded set of values used to express relative size, chosen deliberately to be coarse enough to discourage false precision while still distinguishing meaningfully different item sizes.
Planning Poker Definition
Planning poker is a collaborative estimation technique in which team members independently and simultaneously propose an estimate for a given item, then discuss any significant differences before converging on a shared estimate, reducing the influence of any single participant's opinion dominating the group.
Living With Estimation Uncertainty
Estimation Uncertainty Definition
Estimation uncertainty is the inherent imprecision present in any estimate, accepted as a normal condition within agile approaches rather than treated as a flaw to be eliminated, since early estimates are necessarily based on incomplete information.
Estimate Revision Definition
Estimate revision is the practice of updating a previously given estimate as more information becomes available, consistent with agile's broader expectation that early judgments, including estimates, should be expected to improve rather than remain fixed once first stated.