Understanding sprints
The content on this page only applies to Scrum teams.
Scrum teams work in sprints (or iterations), and these teams release incremental features of their product at the end of each sprint. If you're planning work for Scrum teams, we highly recommend that you use the corresponding boards as the issue sources in your plan, and not projects.
Using Scrum boards as issue sources lets you manage the sprints that come from those boards, plan the capacity of future sprints, and assign issues to sprints — all directly from your Portfolio plan. More importantly, if you use the project as an issue source, Portfolio cannot readily associate the sprints of that board with the project. The sprints will then appear as external sprints in your plan.
On this page:
- What is a sprint?
- Viewing sprints
- Types of sprints
- Sprint details in capacity bars
- Estimation and velocity in sprints
What is a sprint?
A sprint is a fixed period of time during which a Scrum team works on issues that they've committed to complete during that period. The issues can be feature stories or bug fixes, depending on how the team works. At the end of the sprint, what typically happens is the Scrum team bundles up all the issues they've completed, and will then release this bundle as a version of their software product.
In both Jira and Portfolio for Jira, a sprint is a 2-week period by default, which is essentially 10 working days. Depending on team size and capacity, you can adjust the number of days in a sprint as needed.
Viewing sprints
Make sure you've already grouped issues by teams so you can view the sprints for each team in the plan. The issues will be grouped in swimlanes by teams, and the capacity details for each sprint will be displayed.
| 1 | Issues are grouped in team swimlanes. Expand the team to show the issues assigned to that team. |
| 2 | Clicking the capacity bar of a sprint will display the capacity details for each sprint. |
| 3 | If you've configured the plan to show rolled-up values, then sprint values will be rolled up, from child issues up to the corresponding parent issues. |
Types of sprints
| Completed sprints | Any sprints that have been completed in Jira Software will display as completed sprints in the timeline of a Portfolio plan.
Sample completed sprint in the timeline of a plan You can choose to view the sprint in Jira Software, as well as filter the issues by the sprint in your plan. By default, completed issues disappear from the plan 30 days after completion. Though this setting can be configured, this means that the capacity details of a completed sprint will not take into account any completed issues assigned to that sprint that are no longer in the plan. |
| Past sprints | If by chance a team has not defined any sprints in the past, but it already has a currently active sprint and some sprints following that, Portfolio will display these past sprints in the timeline. Portfolio for Jira can infer the dates of these past sprints, based on the sprint duration and velocity set for the team, and can thereby display these past sprints.
Sample past sprint in the timeline of a plan Note that since past sprints do not really exist in the first place, so there are no capacity details that can be displayed. |
| Active sprints | Any sprints that are currently in progress in Jira Software will display as active sprints in the timeline of a Portfolio plan. Note that in Jira Software, a sprint can only be given its start and end dates when it's started, and thus become an active sprint.
Sample active sprint in the timeline of a plan Based on the sprint duration and velocity set for the team, Portfolio is able to auto-schedule work into these active sprints as needed. Any issues that go beyond the velocity of active sprints will be allocated into future sprints or projected sprints. You can choose to view the sprint in Jira Software, as well as filter the issues by the sprint in your plan. |
| Future sprints | Any sprints that already exist in Jira Software, and are scheduled after a currently active sprint, will display as future sprints in the timeline of a Portfolio plan.
Sample future sprint in the timeline of a plan Even if a sprint can only be given its dates when it becomes active, Portfolio is able to infer the dates of these future sprints, based on the sprint duration and velocity set for the team. This is why future sprints can be displayed in the timeline. Based on the sprint duration and velocity set for the team, Portfolio is able to auto-schedule work into these future sprints as needed. Any issues that go beyond the velocity of active sprints will be allocated into these future sprints. You can choose to view the sprint in Jira Software, as well as filter the issues by the sprint in your plan. |
| Projected sprints | Since Portfolio is able to infer the dates of sprints that can happen in the future, then any sprints that are projected to happen after the future existing sprints can also be displayed in the timeline. Because these sprints do not exist in Jira Software, these will then be displayed as projected sprints. Note, however, that the name of the sprint will just be "Projected sprint" because the sprint does not exist in the first place.
Sample projected sprint in the timeline of a plan Based on the sprint duration and velocity set for the team, Portfolio 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. You can choose filter the issues by the sprint in your plan. |
| External sprints | If a plan is using projects or filters as issue sources, sprint data will still be displayed for the corresponding issues. However, the sprints will be displayed with the EXTERNAL SPRINT lozenge next to them. Because sprints can only be directly associated with board issue sources, then the lozenge indicates that the sprints are not directly associated with project and filter issue sources.
Issues assigned to an external sprint See Scheduling issues according to sprints for more details on handling external sprints. |
Estimation and velocity in sprints
There are several ways to estimate the issues you're working on. Depending on how your team works, you can estimate issues using story points or time-based estimates (days or hours).
The main objective though should be to get better at predicting how much work a team can complete in each sprint. This translated to knowing the team's velocity.
Velocity measures the number of 'estimation units' that a team usually completes from sprint to sprint. It is effectively a productivity rate based on an estimation of volume of work, and it is best worked out in a measure other than 'time'.
We recommend using story points instead of time-based estimates. If you estimate that a story will take 16 hours to complete, there's no guarantee that that estimate is 100% accurate. Story points, on the other hand, focus on estimating the size of an issue. A trivial bug fix may be estimated at 1 or 2 story points. A bigger feature that needs some prior research, however, may be estimated at 8 or 10 story points. Learn more about story point estimation.
Scheduling issues according to sprints
Before you begin, note that this only applies to issues sourced from Scrum boards and when issues are assigned to Scrum teams.
When a team and a sprint are set for an issue, the target start and end dates of that issue are automatically derived from the assigned sprint.
Sample plan, with target dates of issue aligning with sprint dates
Additional notes:
- You can still change the target dates of an issue if needed, even if the target dates are automatically derived from the assigned sprint.
- If you reschedule an issue and its target dates no longer match the dates of the assigned sprint, this will not change the sprint assignment.
See Scheduling issues for more details.