Iteration Planning
The team-level meeting that turns a prioritized backlog into a credible, committed plan for the next sprint — balancing capacity, dependencies, and the definition of done.
Definition
Iteration Planning — sprint planning in Scrum — is the team-level meeting that turns the prioritized backlog into a credible, committed plan for the next iteration. The team selects the work it can complete to the Definition of Done, breaks it into tasks, identifies dependencies, and confirms capacity. It is the moment where ambition becomes commitment.
Why It Matters
An iteration without planning is a hopeful list. An iteration with planning is a forecast the team owns. The meeting is where dependencies surface, capacity is reconciled with reality, and the difference between "we'd like to" and "we will" gets resolved.
The Cadence
- Capacity — adjusted for holidays, on-call, support, and meeting load.
- Backlog priority — already refined to a known acceptance criteria standard.
- Story selection — pull until capacity is met; do not over-commit.
- Task breakdown — each story decomposed into engineering tasks for execution clarity.
- Dependency confirmation — external blockers named with owners.
- Sprint goal — a single sentence the team can rally around when prioritisation calls come mid-sprint.
Real-World IT / Agile Example
A payments squad with chronic over-commitment ran capacity at "team size × 8 hours × 10 days". Net delivery for three sprints was 56% of plan. The team rebuilt capacity from the bottom up: subtract holidays, on-call, support load, meeting load, and a 15% buffer for interruption. Net capacity dropped 38%. Net delivered rose to 91% of plan within two sprints. The same squad, same people, same backlog — the difference was honest capacity planning.
Real-World Construction Analogue
The closest construction analogue is the Last Planner weekly work plan: foremen commit, dependencies are confirmed, capacity is reconciled with manpower. The mechanics are different; the discipline is identical.
Key Takeaways
- Iteration planning converts a prioritized backlog into a commitment.
- Honest capacity beats optimistic capacity every time.
- The sprint goal makes mid-sprint priority calls easier.
- Backlog refinement is the prerequisite — planning is not refinement in disguise.
Expert Tips
- Time-box the meeting strictly — long planning meetings indicate weak refinement.
- Make capacity arithmetic explicit on the wall; private capacity assumptions cause silent over-commitment.
- Surface dependencies as commitments from named owners, not aspirations.
- Track planned vs delivered each sprint; the trend matters more than any single sprint.
- Resist the urge to add "stretch" stories; they teach the team to over-plan.
Common Mistakes
- Treating velocity as capacity; velocity is an output, not a budget.
- Skipping task breakdown; problems found mid-sprint were findable in planning.
- Adding stories without subtracting; the iteration is not infinitely elastic.
- Letting the product owner negotiate scope upward after commitment.
- No sprint goal; the iteration becomes a shopping list.
- Holding planning before refinement is complete; the meeting becomes refinement-by-ambush.
Practical Lessons Learned
- The teams with the steadiest delivery have the most boring planning meetings.
- Capacity honesty is a culture decision, not a technique.
- A defended sprint goal is worth more than five extra stories.
Related Encyclopedia Entries
Related Research Articles, Case Studies & Tools
Frequently Asked Questions
How long should iteration planning take?
Roughly two hours per week of sprint length — less if refinement is healthy.Should the team commit or forecast?
Forecast in modern Scrum; commitment is implicit in the sprint goal.How is capacity different from velocity?
Velocity is observed throughput; capacity is the honest hours available next sprint.What if the team consistently misses plan?
Reduce planned capacity; verify refinement quality; check for invisible interruption work.Do dependencies belong in iteration planning?
Yes — every external dependency named, owned, and accepted before commitment.Should bug fixes be in iteration planning?
Yes — either as stories or as a reserved capacity slice.What is the single most useful artefact?
A visible capacity arithmetic on the wall so over-commitment is impossible to hide.What is a common misconception about Iteration Planning?
That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.Which related encyclopedia entries should I read alongside Iteration Planning?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.How does Dr. Hassan Eliwa's research treat Iteration Planning?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Iteration Planning is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.How is Iteration Planning defined on PMMilestone Research & Insights?
The team-level meeting that turns a prioritized backlog into a credible, committed plan for the next sprint — balancing capacity, dependencies, and the definition of done. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.
People also ask
Follow-up questions practitioners search for next — each one points to the calculator, template or reference entry that answers it.
Where is this in the glossary?
Quick-lookup definitions across 1,200+ PM terms. PM Glossary on PMMilestone.org ↗
Which learning track covers this end-to-end?
Structured tracks from beginner planner to programme controls director. Project Controls Academy ↗
Which book goes deeper than this entry?
Practitioner field handbooks with worked numerical examples. Books & Publications ↗
Which calculator on PMMilestone.org applies here?
The integrated EVM workbook covers most cost-schedule diagnostics. EVM Calculator ↗
Related Entries
More in Agile
- Letter AAcceptance Criteria
The specific, testable conditions a deliverable must meet before the customer accepts it — the contract between a team and the person who will sign off the work.
- Letter BBacklog Refinement
The ongoing practice of clarifying, splitting, estimating, and ordering items on a product backlog so the team always has a healthy queue of ready work for upcoming sprints or releases.
- Letter BBurn-Down Chart
A time-series chart showing remaining work against time, used by agile teams to visualise sprint or release progress and forecast completion.
- Letter CContinuous Integration
The engineering practice of merging code changes into a shared mainline many times a day and verifying each merge with automated builds and tests.
- Letter CCumulative Flow Diagram
A stacked-area chart of work items in each stage over time — the single most informative chart in lean and Kanban flow management.
- Letter DDaily Stand-up
A short, focused, time-boxed daily meeting where the delivery team aligns on progress, plans the next 24 hours of work, and surfaces blockers.
Further reading on PMMilestone.org
Curated companion resources hosted on the flagship platform, PMMilestone.org.
- For practitioners who want to go deeper, the Learning Tracks.
- Engineers researching this topic typically continue with the Books & Publications.
- A practical companion to this entry is the EVM Calculator.
- Closely related on the flagship platform is the Schedule Health Checker.
- Useful alongside this article is the PMMilestone.org knowledge hub.