agile3
Planning & Estimation

Iteration Planning

Planning the work for one short development cycle; Scrum calls it Sprint Planning.

2 min read · Practitioner

In 30 seconds

  • The general agile name for planning one iteration.
  • Same idea as Sprint Planning in Scrum.
  • SAFe teams use the term for team planning within a Program Increment.

Same idea, different names

An iteration is a short, fixed development cycle. Extreme Programming and SAFe call the planning session at its start iteration planning; Scrum calls it Sprint Planning.

A simple agenda

  1. Agree the iteration goal
  2. Check capacity for this iteration
  3. Select top items from the backlog
  4. Break them into tasks and confirm the team can finish them

In SAFe

In SAFe, iteration planning happens inside a Program Increment. Teams refine and commit to the iteration's share of the objectives they set in PI Planning.

Myth vs reality

Myth · Iterations and sprints are different things.
Reality · They're the same concept with different names.
Myth · Iteration planning requires estimates in hours.
Reality · Any sizing approach can work.
Myth · Plans are fixed once made.
Reality · The goal stays; the task plan adapts.

FAQ

How long should iteration planning take?

An hour or two for a two-week iteration if items are refined.

Who attends?

The whole team, with the Product Owner or equivalent.

What is an iteration goal?

A short statement of what the iteration aims to achieve, like a Sprint Goal.