The Productivity Chart displays a rate of productivity for a team during the last 15 iterations. This chart can be used with velocity metrics to estimate future iteration capacity during planning.
- View up to the last 15 iterations, where capacity values have been entered
- View the average productivity rate of iterations on the chart
- Hover over bars in the graph to see detailed statistics on the iteration
- Hover over a point on the line to view the productivity rate trend
- Print the chart from the Actions drop-down menu
- Use the Auto Height setting to automatically adjust the vertical space of the app based on the amount of visible data
Basis of productivity rate
The productivity rate can be a more meaningful metric than the velocity. Velocity can fluctuate depending on changes in resource availability (vacations, holidays, sick leave, loss or addition of team members). However, the productivity rate should remain relatively constant, or ideally improve over time as the team becomes more skilled and efficient and better at estimating the size of stories.
Productivity rate is calculated by dividing the total number of user story points by the available task hour capacity of all team members. For example, if the total hourly capacity of all developers in an iteration is 25, and the team completes 9 points of user story work, their productivity rate is 0.36 points per hour.
Most scrum teams recognize that a team member can only realistically contribute 4-6 hours per day toward their iteration tasks. This number multiplied by the number of days that the team member is available during the iteration (accounting for weekends, vacations, holidays, or any other leave time) is the team member's capacity. The capacity for each team member is recorded for each iteration on the Team Status page. The app attempts to compile data from a maximum of 15 iterations working backward from the most recently completed iteration, but iterations that have not been set up with team member capacities will be excluded.
The productivity rate can also be used as a planning tool to calculate the target number of points that should be scheduled for the next iteration. First, determine the team's total capacity in the next iteration, then multiply that by the average productivity rate. This target number of points can be assigned to the Resources field when creating the next iteration.