About this report
The dev availability report captures the total estimated development task hours per sprint versus the total development task hours actually logged per sprint. In other words, how did the actual time spent on the tasks compare to what you estimated? This report provides this comparison over the previous 3, 5, or 10 sprints using a bar graph. The X axis of the graph shows the estimated and actual categories being compared, and the Y axis represents the total task hours value.
This report can be used as a coaching tool by Scrum Masters, team leaders, and product owners to assess the accuracy of development task estimates, and also to track actual development time logged per sprint. It is beneficial to review the report with team members during pre- and post-PI meetings, general team meetings, and during sprint review meetings. This report is generated by selecting a specific team tied to a specific program.
To navigate to this report:
If you’re using the new navigation:
- Select Teams in the top navigation bar and select the team you want to view information about.
- On the sidebar, select Reports in the list of options.
- Select Dev availability; the report displays.
If you’re using the old navigation:
- Select the Reports icon from the left Navigation menu.
- Start typing the report's name in the Search box.
- Once found, select the report.
Note: You can also use the categories on the left to search for the needed reports.
- PI must exist in the system and be tied to a program.
- Sprints must be created and tied to a PI.
- Teams must be created and tied to a program.
- Stories must be created and tied to a sprint.
- Tasks must be created and tied to stories.
- Development task hours must be estimated and logged.
How are report values calculated?
- Estimated development task hours are pulled from all development tasks assigned to stories in the specified sprint for the selected team; the development task hour estimates are entered on the tasks page/New Task panel.
- Actual development task hours are pulled from logged development task hours for stories in the specified sprint belonging to the selected team; actual logged development hours are entered by clicking the clock icon for any tasks listed for a story; this can also be performed using the same clock icon in the team room, List view.
How to interpret this report
Ideally, estimated task hours should be fairly equal to actual task hours. Pay particular attention to the variance in height of the two bars in the graph--variance can also be calculated by <Estimate hours> - <Actual hours>. When actual hours are less than the estimate hours, variance is positive and means there are additional task hours remaining for work in the sprint. When actual hours are greater than estimated hours, variance is negative and means extra time was needed to complete the tasks. Over multiple sprints, repeated variance (either positive negative, or both) shows the need for the team to work on creating more accurate estimates.