Running sprints in a Scrum project
A sprint — also known as an iteration — is a short period in which the development team implements and delivers a discrete and potentially shippable application increment, e.g. a working milestone version. If you haven't run sprints before, we recommend using a fixed two-week duration for each sprint. It's long enough to get something accomplished, but not so long that the team isn't getting regular feedback.
Note, sprints do not apply to Kanban projects.
In Jira Software, you view sprints on a board and assign issues to sprints. You can search for issues in upcoming sprints using the Sprint field. You can view the Sprint field on each individual issue as well, to see the sprint that an issue is part of.
To learn more about running sprints, read the following topics:
- To learn how to create and modify a sprint, add issues to a sprint, and start a sprint, see Planning sprints.
- To find out how you can use Active sprints, wallboards, reports, and more, to track a sprint that is in progress, see Monitoring the progress of a sprint.
- To learn how to close a sprint and complete related tasks, like reporting, see Completing a sprint.
- To learn how to reopen a sprint that's already closed, see Reopening a sprint.
- To see how you can link Confluence pages (e.g. 'Retrospective notes') to a sprint, see Linking a Confluence page to a sprint.
Known issues
This table lists known issues in the behavior of and in your work with sprints. Here, you'll also find possible solutions and temporary workarounds.
We are aware of these issues and have planned their resolution in future releases.
Issue | Solution |
|---|---|
Closed and completed sprints get automatically removed from the Sprint issue field when you’re moving issues to a new project. | This is a known issue tracked in the ticket JSWSERVER-13333 - Getting issue details... STATUS |