Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Create powerful rules to start automating your manual, repetitive processes.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
The end of a sprint is the time where your team takes stock of its progress. This usually includes demonstrations of the work completed during the sprint, followed by a sprint retrospective to analyze where improvements can be made.
As the team lead, Scrum master, or product owner, you can also use this time to check how your team is progressing against the overall version, and provide feedback to your stakeholders.
Before you begin
Sprints only apply to Scrum boards. If you are using a Kanban board, check out Deploying a release instead.
To complete a sprint, you must be a Jira Administrator or a user with the Manage Sprints permission.
If you can't complete a sprint, your board's filter may be complex, and Jira Software is unable to determine which projects will be returned by the query. See Using Manage Sprints permission for advanced cases if you need help.
Completing the active sprint
Go to the Active sprints of your Scrum board.
If necessary, select the sprint you want to complete from the sprint drop-down.
Note that if you have multiple sprints in the Active sprints of your board, the 'Complete Sprint' button will not appear until you select one of the sprints.
Click Complete Sprint. All completed issues will move out of Active sprints.
If the sprint has incomplete issues, select from one of the following:
Backlog, to move the issues to the backlog
Any future sprint, to move the issues to any future sprint that's already created
New sprint, to create a new sprint and then move the issues to the new sprint
Note that your issues won't be marked with the date the sprint was closed; however, you can always view the sprint for an issue to find out when the sprint ended.
For sprints that have parent issues and sub-tasks:
If you have parent issues that are 'Done' but sub-tasks that are not 'Done', you won't be able to end the sprint. You must complete the sub-tasks first.
If you have parent issues that are not 'Done' but have sub-tasks that are all 'Done', the parent issues will still be moved to the selected future sprint or to the Backlog. If these parent issues are part of another active sprint, the previously completed sub-tasks are still 'Done'.
Other tasks to complete at the end of a sprint
Conduct a retrospective and link your notes to the sprint
Typically, at the end of a sprint, you conduct a sprint retrospective. This is a meeting where your team discusses the completed sprint, including the things they need to start doing, stop doing, or continue doing. The outcome of this meeting should be actions for improvements in future sprints.
When you complete a sprint in Jira Software, you will be shown the 'Sprint Report', which provides helpful data about your sprint for your team's retrospective. If you have Confluence linked to Jira Software, you can also create your retrospective notes as Confluence pages and link them to your Sprint Report. See Linking a Confluence page to a sprint for more information.
Check the progress of your version
The end of a sprint is a great time to check how your version is progressing. See Checking the progress of a version for more information.
Release the sprint as a version (optional)
Your team may not need to release a version at the end of a sprint — but if you need to, it's easy to do. In the Completed Issues section of the Sprint Report, just click View in Issue Navigator. You should have already pre-assigned issues to a version before starting work on them, (which results in better reports). However, if you need to specify a version for issues at this stage, use Jira's Bulk Edit to assign all of the issues to the relevant version (see Editing multiple issues at the same time for more information). Note that you will not be able to do this if your 'Done' column sets an issue's status to 'Closed', as issues are not editable once they are 'Closed' (but 'Resolved' is fine). Also, note you can only Bulk Edit the 'Fix Version' for issues from one project at a time.
Start planning your next sprint!
Once you have completed a sprint in Jira Software, you can start getting ready for a new one.
You can only have one active sprint at a time, unless you've enabled parallel sprints.
Need help? If you can't find the answer you need in our documentation, we have other resources available to help you. See Getting help.
Was this helpful?