Agile Frameworks/Methodologies · Topic 2 of 4
Planning Iterations
CAPM iteration planning: timeboxed iterations, backlog and user stories as scope inputs, turning a WBS into iterations, estimating and adaptive tracking.
- 3 min
- Iterations are fixed timeboxes, usually one to four weeks.
- Scope lives in the prioritized product backlog.
- Epic or feature, then user story, then task.
What it is
An iteration is a short, timeboxed cycle of development, typically one to four weeks, in which the team builds a usable piece of the product. Iteration planning decides which backlog items to take on, based on priority and the team's capacity.
How it works
Logical units of iterations
| Unit | Meaning |
|---|---|
| Release | A set of iterations that delivers a meaningful set of features to users |
| Iteration or sprint | A fixed timebox, the same length each time |
| Feature or epic | A large piece of functionality, split into stories |
| User story | A small piece of value from the user's point of view |
| Task | The technical work the team does to complete a story |
Inputs for scope
In adaptive projects, scope is held in the product backlog: an ordered list of everything that might be built. Inputs include the product vision and roadmap, stakeholder needs, user stories, feedback from earlier iterations and lessons learned.
A user story often follows the form: "As a (type of user), I want (goal) so that (benefit)". Good stories follow INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable.
Translating a WBS into iterations
| Predictive | Adaptive equivalent |
|---|---|
| WBS | Product backlog |
| Deliverable | Feature or epic |
| Work package | User story |
| Activity | Task |
| Schedule | Release and iteration plan |
A worked example: a WBS has a deliverable "online ordering", with work packages "browse menu", "pay online" and "track order". In an adaptive plan, "online ordering" becomes an epic and each work package becomes one or more user stories ranked in the backlog. The team might deliver "browse menu" in iteration 1 and "pay online" in iteration 2.
Estimating
| Technique | How it works |
|---|---|
| Story points | A relative measure of size and effort, not hours |
| Planning poker | Each team member reveals an estimate card at once; differences are discussed and the team re-estimates |
| T-shirt sizing | Rough sizes: XS, S, M, L, XL |
| Affinity estimating | Grouping items of similar size |
Velocity is the amount of work, usually in story points, a team completes per iteration. It helps forecast how many iterations the remaining backlog needs. Velocity belongs to one team and is not used to compare teams.
Pros and cons of iterations
| Pros | Cons |
|---|---|
| Frequent feedback and early value | Needs regular customer involvement |
| Problems are found early | Some work does not split easily |
| Easy to change priorities between iterations | Total scope and end date are less certain up front |
| Regular rhythm and focus | Short timeboxes can feel rushed without good discipline |
Adaptive versus predictive tracking
Predictive tracking compares actuals with a fixed baseline. Adaptive tracking measures completed, working increments each iteration and updates forecasts from real velocity. This makes progress visible sooner and gives early warning when the plan must change.
The iteration length stays fixed. If not all work fits, the team reduces scope for that iteration rather than extending the timebox.
How the exam asks about this
- "What is velocity?" The amount of work a team completes per iteration.
- "In an adaptive project, what replaces the WBS for scope?" The product backlog.
- "Which estimation technique has everyone reveal a card at the same time?" Planning poker.
What to remember for the exam
- Iterations are fixed timeboxes, usually one to four weeks.
- Scope lives in the prioritized product backlog.
- Epic or feature, then user story, then task.
- User stories: "As a ... I want ... so that ..."; INVEST.
- Story points are relative; velocity is points completed per iteration.
- Adaptive tracking measures working increments, not percent of plan.
Do not extend an iteration to finish work. Unfinished items return to the backlog and are reprioritized.
Common mistakes
Treating story points as hours. They are relative size.
Comparing velocity between teams. Each team's points are different.
Planning every iteration in detail up front. Detail is added just in time.
Check yourself
What does INVEST stand for?
Independent, Negotiable, Valuable, Estimable, Small, Testable.
What is the adaptive equivalent of a work package?
A user story in the product backlog.
How is velocity used?
To forecast how many iterations the remaining backlog will take for that team.
Topic 2 of 4 in Agile Frameworks/Methodologies
Test yourself on Agile Frameworks/Methodologies
The full PMI CAPM question bank has 1,049 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by PMI. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.