Brief summary of this article:
PI 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 Release Train Engineers, Product Owners and Scrum Masters as they determine whether the overall PI goals can be achieved with the available teams.
This view allows to distribute backlog items (user stories, bugs) across team iterations (sprints) for multiple teams within a single Program Increment (PI). Usually such views are used to plan a next or track a current PI.
Total Effort of assigned backlog items is considered as demand and compared with Capacity of teams in team iterations.
For efficient planning, effort of every significant work item should be estimated in advance. Capacity (availability) of every team should be defined in each Team Iteration in the PI.
Create View
To set up the view for an Agile Release Train (ART), follow the steps below:
- Create a new Board view
- Choose Teams from your ART 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 Team Iterations from current or next PI 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.
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.