Summary

This article provides a comprehensive guide to the Team Spend per Point report in Jira Align. It aims to empower teams and stakeholders to leverage this powerful tool for data-driven decision-making and continuous improvement. By understanding how the report calculates team effort relative to story points, users can gain valuable insights into their performance, identify potential roadblocks, and optimize capacity planning.

This report is particularly beneficial for:

• Scrum Masters: Gain a clear understanding of team velocity and identify impediments impacting sprint performance.

• Team Leads: Track team efficiency, identify areas for improvement, and facilitate better estimation practices.

• Product Owners: Gain insights into team capacity for more accurate sprint planning and forecasting.

• Agile Coaches: Guide teams in using the report effectively to improve their Agile practices and achieve higher performance.

• Management: Monitor team progress, identify potential bottlenecks across multiple teams, and make informed decisions about resource allocation.

By regularly reviewing and analyzing the Team Spend per Point report, these stakeholders can foster a culture of continuous improvement, enhance predictability, and ultimately deliver greater value.

Environment

Jira Align

Solution

The Team Spend per Point report provides valuable insights into a team's effort relative to story points. It helps analyze how much time a team spends, on average, per story point, enabling better estimation, capacity planning, and identification of potential bottlenecks.

1. How the Report Works

The report calculates the average time spent per story point for a selected team and time period. It displays this data per sprint and presents a trendline to visualize changes over time.

2. Calculation

The Team Spend per Point is calculated using the following formula:

Team Spend per Point = (Total Time Spent by the Team on Stories in a Sprint) / (Total Story Points Completed in that Sprint)

Example 1:

• Sprint 1: A team completes stories totaling 20 story points and logs a total of 80 hours of effort.

• Calculation: 80 hours / 20 story points = 4 hours/story point

Example 2:

• Sprint 2: The same team completes stories totaling 15 story points and logs a total of 52.5 hours of effort.

• Calculation: 52.5 hours / 15 story points = 3.5 hours/story point

3. Accessing the Report

To access this report go to: Portfolio → Select a Portfolio → Reports → Spend per points

4. Interpreting the Report

• Average Spend per Point: This metric indicates the average time spent per story point across the selected sprints.

• Sprint-by-Sprint Breakdown: This shows the spend per point for each individual sprint, allowing you to identify variations in effort and potential anomalies.

• Trendline: This visual representation helps identify patterns and changes in team performance over time. An upward trend might indicate growing complexity or unforeseen issues, while a downward trend could signify improved efficiency.

5. Benefits of Using the Report

• Improved Estimation: Consistent deviations from the average spend per point can highlight estimation inaccuracies.

• Bottleneck Identification: Spikes in time spent per point may indicate impediments or other issues slowing down the team.

• Capacity Planning: Understanding the average time spent per point helps teams accurately estimate their capacity for upcoming sprints.

• Performance Tracking: The trendline allows teams to monitor their progress in becoming more efficient and identify areas for improvement.