Summary

Problem Statement 

In advanced roadmap planning, the team's capacity is calculated based on the length of the Sprint and the capacity hours per week. However, it is important to note that the capacity for the active Sprint differs from that of future Sprints when checked on the timeline.

Reasoning

The future sprint starts from the 0th hour of the sprint start day and ends at the 24th hour of the sprint end day whereas the active sprint includes the 0th hour of the active sprint start day and ends at the 24th hour of active sprint end day -1.

Eg - 

Environment

Cloud 

Diagnosis

1. In Jira, there is global time tracking, with the default setting being 8 hours/day and 5 working days/week. The Jira plan will respect this setting. Now for example if the team capacity is 32 weekly hours and 5 working days/week; therefore, for this team, the daily capacity would be 32/5 = 6.4 hours/day.
   
2. For example, let's consider sprint with name Mobile Sprint 2 runs from 27 December 2023 to 10 January 2024, which includes 11 working days (based on the setting of 5 working days/week). For this sprint, the total working hours would be 11 days * 6.4 hours/day = 70.4 hours, which is equivalent to 8.8 days.
3. However, for Mobile Sprint 1, although the total number of days is 11, when calculating the active sprint, we consider the number of days from the start date/ start time to the previous date of the end time. In that case, the total working days amount to 10, resulting in working hours of 10 days * 6.4 hours/day = 64 hours, which is equivalent to 8 days.
   
4. The method of calculating the total number of days for active sprints and future sprints differs, which is the reason for it showing one day less for the active sprint.
5.  Included a graph to facilitate a better understanding of the issue.