Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Know it well enough for the exam? Questions on Relative Estimation are scenario-based, not definitional.
Practice it freeExplanation
Humans are generally better at comparing things than estimating absolute values. Relative estimation leverages this by asking teams to compare items: Is this item about the same size as that one? Is it roughly twice as large? This comparative approach is faster, more consistent, and less influenced by individual speed differences.
Common relative estimation techniques include Planning Poker, T-shirt sizing (XS, S, M, L, XL), and affinity estimation (grouping items into size categories on a wall). Story points are the most common unit for relative estimation. A reference story is established as a baseline, and all other items are estimated relative to it.
Relative estimation works because teams can reliably judge that one item is twice as complex as another even if they cannot predict exactly how many hours it will take. Over time, the team's velocity translates relative estimates into predictable throughput, enabling accurate sprint and release planning.
Key Points
- •Compares items against each other rather than using absolute time units
- •Faster and more accurate than absolute estimation
- •Common techniques: Planning Poker, T-shirt sizing, affinity estimation
- •Uses a reference story as a baseline for comparison
Exam Tip
Relative estimation is preferred in agile because it is faster, less contentious, and more reliable than absolute estimation. Teams estimate size, and velocity translates that into time.
Frequently Asked Questions
Related Topics
Story Points
Story points are a unit of measure used in agile to estimate the overall effort, complexity, and uncertainty involved in completing a user story or product backlog item.
Planning Poker
Planning Poker is a consensus-based agile estimation technique where team members privately select cards representing their estimate, reveal them simultaneously, and discuss differences to reach agreement.
Velocity
Velocity is the amount of work a Scrum team completes in a Sprint, typically measured in story points, used to forecast how much work the team can handle in future sprints.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
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.
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.
Sprint Review
The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.
Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.
Timeboxing
Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.
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.
Part of
Agile & Hybrid
Practice Relative Estimation
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.