10X: Capacity Planning

About this report

The Capacity Planning report details the team capacity throughout the sprint, and is especially helpful to Scrum Masters as they determine whether the overall goal of the sprint can be achieved with the available team members. It is useful to review the Capacity Planning report during sprint planning and throughout the sprint to assure team commitments can be achieved with available capacity.

The report contains several charts and graphs, outlined below:

  • Sprint Story Load shows the planned effort for the selected sprint in story points.
  • Team Velocity Last 5 Sprints details the accepted story points the team completed during the previous 5 sprints.
  • Average Velocity Last 5 Sprints displays the average of story points accepted over previous 5 sprints.
  • Sprint Task Load shows a bar chart with a roll up of team capacity, allocation of hours dedicated to capacity reducing activities, adjusted capacity, task hours loaded for sprint and actual hours spent on tasks.  
  • Available Capacity displays the hours a team is over or under allocated. 
  • Planned to Burn in the Sprint shows all tasks hours associated to stories planned in selected sprint.
  • Remaining to Burn in Sprint shows the task hours remaining that are in a done status for selected sprint.
  • Allocated Members shows a count of team members available to work in sprint.
  • Bottom section of report displays a breakdown per team member with allocation percentages, available capacity in hours, assigned tasks (Loaded Hours), actual hours to complete tasks (Spent Hours), remaining tasks in hours and remaining capacity.
  • Threshold is a user defined field that allows for a threshold percentage to be set on the Loaded Hours and Remaining Hours fields to highlight with Red (Exceeded user-defined threshold) and Yellow (Below user-defined thresholds).

Navigation

  1. Select the Reports icon from the left Navigation menu.
  2. Start typing the report's name in the Search box. 
  3. Once found, select the report.

Note: You can also use the categories on the left to search for the needed reports.

Prerequisites

  1. PI must exist in the system and be tied to a program. 
  2. Features must be created and tied to the PI. 
  3. Stories, with point values, must be created and tied to features.
  4. Stories must be assigned to sprints. 
  5. Sprints must be created and tied to the PI. 
  6. Tasks must be created and assigned to stories. 
  7. Teams must be created and tied to a program.  

How are report values calculated? 

  • Sprint Story Load
    • Planned Effort = total committed story points from sprint planning or total story points loaded into a sprint as of 11:59 PM on its first day if a planning meeting wasn’t run. 
  • Team Velocity Last 5 Sprints = total story points by sprint accepted by Product Owner for each of the past 5 sprints.
  • Average Velocity Last 5 Sprints = total of story points accepted by Product Owner for past 5 sprints averaged over past 5 sprints.
  • Sprint Task Load 
    • Team Capacity = total capacity hours available for team.
    • Ramp Up/Estimate = total hours allocated for estimation, sprint planning, sprint review and sprint retrospective meetings.  These activities are reduced from total team capacity.
    • Defect Allocation = total hours allocated for defect remediation.  These activities are reduced from total team capacity.
    • Defect Actuals = total of actual hours spent for defect remediation.  These activities are reduced from total team capacity.
    • Discipline Allocation = total hours allocated for discipline allocation (i.e. - internal support).  These activities are reduced from total team capacity.
    • Discipline Actuals = total of actual hours spent for discipline allocation (i.e. - internal support).  These activities are reduced from total team capacity.
    • Task Capacity = total capacity available after reducing allocations for ramp up/estimate, defect allocation and discipline allocation.
    • Team Load = total task hours assigned to stories committed in sprint.
    • Actual Spent = total actual hours spent working on tasks during sprint.
  • Available Capacity = the team total of capacity hours less the loaded task hours for stories committed in sprint.  More capacity than loaded hours will result in under allocation and more loaded hours then capacity hours will result in over allocation. 
  • Planned to Burn in Sprint = cumulative total of all task hours of stories committed in sprint.
  • Remaining to Burn in Sprint =  total tasks hours left to be completed in sprint.
  • Allocated Members = total of all team members with an allocation of greater than 0 in sprint.
  • Allocated = percentage of time available to work in current sprint.
  • Capacity Hours = total available time multiplied by allocation. 
  • Loaded Hours = total task hours assigned.
  • Spent Hours = total hours spent working on task.
  • Remaining Hours = time remaining for task completion.
  • Remaining Capacity = a total of days left in the sprint and daily capacity.

Capacity_Planning_Final.png 

How to interpret this report

The report should be used to determine if the team is set up for success going into a sprint. It tells the story of the sprint, such as: Can we deliver upon our commitments? Is the work distributed equally within the team? Are we progressing as planned or is work taking more/less time than estimated?   

Was this article helpful?
0 out of 0 found this helpful
Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

Join the Atlassian Community!

The Atlassian Community is a unique, highly collaborative space where customers and Atlassians come together. Ask questions and get answers, start discussions, and collaborate with thousands of other Jira Align customers. Visit the Jira Align Community Collection today.

Need to contact Jira Align Support? Please open a support request.