Study guides / CAPM: Certified Associate in Project Management / Iteration planning & estimation
Iteration planning & estimation
CAPM: Certified Associate in Project Management · quick review
Planning work in iterations: user stories, relative sizing, velocity-based forecasting and the charts that track progress.
The rules
- User story format: "As a [role], I want [capability] so that [benefit]." Good stories are INVEST: independent, negotiable, valuable, estimable, small, testable. Each has acceptance criteria.
- Story points are relative sizes, often on a Fibonacci-like scale; planning poker reaches consensus and exposes different assumptions.
- Velocity is the points a team completes per iteration; use the team's own average to forecast. Velocity isn't comparable between teams.
- Burndown chart: work remaining over time. Burnup chart: work completed and total scope, which shows scope changes.
- A spike is a timeboxed investigation to reduce uncertainty. The definition of ready is a team's check that a story is clear enough to plan.
- Release planning sets roughly which features land in which iterations; the MVP (minimum viable product) is the smallest release that tests the idea with real users.
Formulas
- Iterations remaining: Remaining story points ÷ average velocity
Common traps
- Raising velocity isn't a goal in itself; pushing it leads to inflated estimates.
- Story points measure relative effort and complexity, not hours.
How it's tested
Velocity forecasts, reading burndown and burnup charts, and story quality.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson