Brief summary of this article:
Iteration Planning views are part of Capacity Planning capabilities on Team level. They allow to compare demand as planned workload with available capacity of teams who do the work. It is especially helpful to Product Owners and Scrum Masters as they determine whether the overall iteration goals can be achieved with the available team.
The view allows to distribute backlog items (user stories, bugs) across team iterations (sprints) for a single team. Usually teams plan a next or track a current sprint with this view.
The view helps to ensure that total amount of assigned items does not exceed planned Capacity or Velocity of a given team.
Total Effort of assigned backlog items is considered as demand and compared with Capacity of the team in a team iteration.
For efficient planning, effort of every work item should be estimated. Capacity (or velocity) of the Team Iteration should be defined as well.
Create View
To set up the view, follow the steps below:
- Create a new Board view
- Choose one Team and all related Projects in Projects and Teams selector.
- Choose User Stories and Bugs as cards.
- Choose Teams as rows.
- Choose Team Iterations as columns.
- Apply Filter to Team Iterations, to show only current or next Team Iterations and hide past ones.
- Finish Setup.
Calculate Capacity from past Velocity
Planning capacity for future Team Iterations based on previous periods is quite a typical case among our customers. Scrum Masters, Product Owners, or Team Leads calculate average team velocity over the last N time periods and use it as a starting point for the next team iterations. As soon as these calculations are automated, there is no more need to calculate capacity manually.
See Also
More information about this topic:
Still have a question?
We're here to help! Just contact our friendly support team.
Find out more about our APIs, Automation Rules, Mashups and custom extensions.