Skip to content
PMPCAPM

Agile Estimation Techniques

Agile estimation techniques are lightweight methods used by agile teams to estimate the size, effort, or complexity of work items, including story points, planning poker, T-shirt sizing, and relative estimation.

Share:

Know it well enough for the exam? Questions on Agile Estimation Techniques are scenario-based, not definitional.

Practice it free

Explanation

Agile estimation techniques differ from traditional estimation in that they focus on relative sizing rather than absolute time estimates. Story points are the most common unit, representing the overall effort, complexity, and uncertainty of a user story relative to other stories. Planning poker (a form of Wideband Delphi) is a popular technique where team members independently estimate, reveal simultaneously, and discuss differences before converging.

Other agile estimation techniques include T-shirt sizing (using S, M, L, XL categories for rough sizing), affinity estimation (grouping stories by similar size), and ideal days. These techniques are designed to be quick, collaborative, and to leverage the collective wisdom of the team rather than relying on a single estimator.

Agile estimation is intentionally imprecise at the individual story level but becomes quite accurate in aggregate over multiple iterations. Teams use their velocity (the average number of story points completed per iteration) to forecast delivery timelines and capacity. The emphasis is on consistency of estimation rather than absolute accuracy.

Key Points

  • •Focus on relative sizing rather than absolute time estimates
  • •Story points measure effort, complexity, and uncertainty
  • •Planning poker uses independent estimation with group convergence
  • •Aggregate accuracy improves over multiple iterations via velocity tracking

Exam Tip

Know that agile estimation focuses on relative sizing, not absolute hours. Planning poker combines independent estimation with group discussion, similar to Wideband Delphi.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Matrix Diagrams

Matrix diagrams are a data representation technique that uses a grid format to show relationships between two or more groups of factors, commonly used for responsibility assignments and prioritization.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Risk Register

The risk register is a project document that records the details of individual project risks, including their identification, analysis results, response plans, and current status.

Part of

Tools & Techniques

Study full domain →

Practice Agile Estimation Techniques

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.