Agile estimation: the complete guide

A practical guide to agile estimation: user stories, planning poker, story points, velocity, and the techniques that hold up when a story turns out bigger than it looked.

Estimation goes wrong in familiar ways: numbers that mean different things to different people, sessions that overrun, forecasts nobody trusts. The fix is rarely a better formula. It’s a shared understanding the whole team owns, and estimates kept as forecasts rather than commitments held against you.

This guide works through the parts that hold up in practice: user stories, planning poker, story points, velocity, and the techniques that keep working when a story turns out bigger than it first looked. When you’re ready to run estimation with your team, estimate in TeamRetro: planning poker with private voting, reusable decks, and final story points that sync straight to your backlog.

Four sticky-note characters seated around a small table, each holding up a numbered card at the same moment.
Chapter 1What is planning poker?

Planning poker is a consensus-based agile estimation technique: teams vote privately, reveal every card at once, and discuss the spread until the estimates converge.

A sticky-note character beside a whiteboard holding up two sand timers, while two seated sticky-notes wait with their cards.
Chapter 2How to run a planning poker session

How to run a planning poker session that gives useful estimates without dragging: prep, the four-phase round, choosing a deck, and ruthless time-boxing.

Two sticky-note characters standing back to back to compare their heights against a mark on the wall, pleased to have settled which is bigger.
Chapter 3What are story points? Estimating effort, not time

Story point estimation sizes the relative effort, complexity and uncertainty of work, not the hours. How to size against a reference story, and the questions that trip teams up.

A worried sticky-note character climbing a staircase whose steps grow taller toward the top.
Chapter 4Why story points use the Fibonacci sequence

Story points climb 1, 2, 3, 5, 8, 13 because the widening gaps encode uncertainty: the scale stops pretending you can tell a 13 from a 14. Here's why the gaps are the point.

A sticky-note character standing between a wall clock and a stack of blocks, holding a hand out to each to keep them apart.
Chapter 5Story points vs hours: why converting them is the trap

Story points measure relative effort; hours measure duration. They are different axes. Build a points-to-hours table and you've quietly gone back to estimating time.

A sticky-note character at a whiteboard tracing a line across six sprint columns, pointing at the steady middle rather than the tallest spike.
Chapter 6Team velocity in agile: how to measure and use it (+ free calculator)

Learn what team velocity is in agile, how to calculate it, and how to plan sprints with it, plus a free velocity calculator.

A cheerful sticky-note character pointing at the larger of two boxes, with a stopwatch set down at its feet.
Chapter 7Relative vs absolute estimation (and why relative wins)

People are bad at 'how long will this take' and good at 'is this bigger than that.' Relative estimation uses the second, and it's why story points work.

A sticky-note character shading its eyes to peer into the wide mouth of a large funnel.
Chapter 8The cone of uncertainty in agile estimation

Early estimates are wide because the work is unknown, not because your team is bad at estimating. What the cone of uncertainty means, and how to narrow it, not pad it.

Three sticky-note characters of different sizes standing in a row, with the middle one holding up a card with a 1 on it.
Chapter 9Epic vs story vs task: the agile hierarchy explained

Epics, stories and tasks are three tiers with three jobs. What each is, which one carries story points, and why pointing the wrong tier makes velocity meaningless.

A sticky-note character stepping back from a wall of clustered notes, considering which one to size.
Chapter 10Agile estimation techniques: which one to use and when

A practical decision guide to agile estimation techniques: planning poker, story points, t-shirt sizing, affinity estimation and velocity, and which to use when.

A sticky-note character placing a card with a 1 on it back into a row of cards on a whiteboard.
Chapter 11Planning poker mistakes and anti-patterns

The recurring ways planning poker sessions go wrong (averaging cards, estimating in hours, weaponized velocity, story-point inflation) and how to fix each.

A sticky-note character holding a checklist with one line ticked and one crossed out, comparing it with a finished drawing on a whiteboard.
Chapter 12Acceptance criteria: how to write them

Acceptance criteria are a story's pass/fail test, written before work starts: the formats that work, worked examples, and how they differ from the definition of done.

A row of sticky-note characters passing story cards toward a doorway labeled Done, with a checklist pinned beside the frame.
Chapter 13Definition of done (DoD): checklist and examples

The definition of done (DoD) is one checklist every story clears before it ships. Example checklists, how to write yours, and DoD vs acceptance criteria.

A sticky-note character with a clipboard at a small gate, waving one story card through while another waits to be checked.
Chapter 14Definition of ready

The definition of ready is the checklist that says a story is sprintable. What a useful one covers, why most get ignored, and the version that actually blocks.

A large character drawing dividing lines across a big story card on a whiteboard, with three smaller sticky-note characters standing below it.
Chapter 15Splitting user stories that won't fit a sprint

A story you can't estimate is usually one you can't ship yet. How to tell when to split, the cut lines that produce shippable slices, and the ones that only fake it.

A sticky-note character with a marker beside a whiteboard showing one tall card cut into vertical slices.
Chapter 16SPIDR story splitting

SPIDR is five reliable ways to split a user story: spike, path, interface, data, rules. Each cut line, when it works, and when it produces a fake slice.

Three sticky-note characters at a whiteboard drawing of a layered cake, one cutting into it with a knife, next to a thin wedge cut from top to bottom.
Chapter 17Horizontal vs vertical slicing

Vertical slices ship value; horizontal slices ship promises. Why splitting by tech layer defers value, and how to slice by user outcome so something ships each sprint.

A sticky-note character reading from a small card to a second one, who sketches what they hear on a whiteboard.
Chapter 18What is a user story?

A user story is a short, plain-language promise of value. The role-goal-benefit format, the three Cs, the INVEST checklist, and the cases where stories are the wrong tool.

A sticky-note character with a marker beside a board of story cards, ticking them off and holding one card up for a closer look.
Chapter 19User story examples: 16 annotated stories, good and bad

Sixteen annotated user story examples across auth, e-commerce, mobile, APIs and bugs, with the bad versions shown next to their rewrites so the difference is visible.

A sticky-note character with a marker filling in a large story card, with three checkboxes on it and the first one ticked.
Chapter 20User story template and acceptance criteria

The classic user story template with a copy-paste card, the variants worth knowing, and one worked example carried from template to acceptance criteria to estimate.

Sticky-note characters wearing size-labeled t-shirts, lined up under one task card to size it together.
Chapter 21T-shirt sizing in agile: how it works and when to use it

What t-shirt sizing is, how to run a session, and how to turn S/M/L into story points, plus when planning poker is the better call.

Sticky-note characters sorting one shared spread of task notes from small to large, with dashed boundary lines grouping the row into buckets and the largest note highlighted.
Chapter 22Affinity estimation: size a big backlog fast

How affinity estimation sizes a whole backlog in one session: the silent-sort steps, when it beats planning poker, and how to turn it into story points.