Projected Sprints in Advance Roadmap
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
What are Projected sprints in a PLAN?
Advanced Roadmaps can infer the dates of sprints that can happen in the future, any sprints that are projected to happen after future existing sprints will also be displayed in the timeline. Because these sprints do not exist in Jira, they are displayed as projected sprints. Note, the name of the sprint will be "Projected sprint" because the sprint does not exist in the first place.
Based on the sprint duration and velocity set for the team, Advanced Roadmaps is able to auto-schedule work into these projected sprints as needed. Any issues that go beyond the velocity of existing future sprints will be allocated into these projected sprints.
How will projected sprints to show up?
The following will be needed:
- A team with planning style set to SCRUM should be in the PLAN.
- An issue source should be defined for the team.
- The team should be assigned to one of the issues in the PLAN.
The duration of the Projected sprints would be the same as defined in the Team settings. Also, they would show up immediately after the current and future sprints. If there are no current and future sprints, they would start showing up immediately, from when you are viewing the plan.
In the above screenshot we see NSC Sprint 1 & 2, which are the sprints that are coming from Jira. Whereas Projected Sprints are actually not present in Jira and are just a mere representation of capacity management done on the basis of team settings.
What if the planning style of the team is Kanban?
Incase the planning style is changed to Kanban, the plan will reflect the prediction on the basis capacity specified in the Team settings in terms of hours/days.
This will lead to projected capacity as shown below: