- Scrum spaces only, and the permissions you need
- Stage one: create the sprint
- Stage two: fill it with work
- Stage three: start it
- What a good sprint goal looks like
- Changing scope mid-sprint
- Stage four: complete it
- Sprints in Linear and Azure DevOps
- My advice for a team's first sprint
- Frequently asked questions
In a company-managed Jira space, open the Backlog tab, scroll to the Backlog section and click Create sprint on the far right. Add work items to it, then select Start sprint to set the name, dates and goal. Only Scrum teams can use sprints, so Kanban spaces don't have them at all.
Scrum spaces only, and the permissions you need
A sprint, also called an iteration, is a short period in which the team delivers a potentially shippable piece of work. In Jira, only Scrum teams can use them. If your space is Kanban, there's no Create sprint button to find, because sprints don't apply there.
You'll also need the right permissions. Most sprint actions need the Manage Sprints space permission. Adding or removing work items also needs Schedule work items and Edit work items. These steps are for company-managed spaces; Atlassian now calls issues work items, so that's the term I'll use.
Stage one: create the sprint
Open your company-managed software space and select the Backlog tab. Scroll past any existing sprints to the Backlog section and select Create sprint on the far right. That makes a new, empty sprint. You can create one for the current iteration or several future sprints to plan ahead.
Stage two: fill it with work
Move work items from the backlog into the sprint. Be realistic: a sprint is a timebox, not a wish list. For teams new to sprints, Atlassian recommends a fixed two-week duration, which is long enough to finish something and short enough to correct course.
Stage three: start it
- On the Backlog tab, select Start sprint.
- Update the Sprint name.
- Choose the Start date and End date.
- Add a Sprint goal if you want one.
- Select Start.
When you start, the planned time and date are replaced by a suggested time and date matching the moment you click, and you can change them. The goal is worth writing. It appears on the Sprint Report and the Burndown Chart, so anyone looking later knows what the sprint was for.
Want more than one sprint running at once? That needs parallel sprints enabled first.
What a good sprint goal looks like
A sprint goal is one sentence that says what will be true at the end, not a list of tickets. 'Work on the website' is too vague and says nothing about what's done. 'Client can book a discovery call from the new landing page' is clear, testable and easy to report on. If your team can't agree on a single sentence, the sprint has too much in it.
Changing scope mid-sprint
Once a sprint is active, adding or removing a work item counts as a scope change, and it shows in reports such as the Burndown Chart. That's useful honesty: if the chart keeps jumping, the team keeps changing its mind. Agree with whoever sets priorities that new work waits for the next sprint unless it's urgent.
Stage four: complete it
At the end, open Active sprints and select Complete Sprint. You'll need to be a Jira Administrator or have Manage Sprints permission. Incomplete work items can go to the Backlog, a future sprint or a new sprint.
Atlassian Support flags the detail to watch here. If you complete a sprint with a parent work item that isn't marked Done, it moves to a future sprint or the Backlog, and sub-tasks must be Done before completion. Tidy those up in the last day of the sprint so nothing gets carried over by accident.
Sprints in Linear and Azure DevOps
Linear calls them cycles: time-boxed periods where a team completes a pre-defined set of work, and Linear creates upcoming cycles automatically when the feature's switched on.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
In Azure Boards you assign start and end dates for your team's sprints, with the Iteration path field tracking sprints and releases.
If Jira feels heavy for your team, my roundup of Jira alternatives and my guide to project management software cover lighter options.
My advice for a team's first sprint
Keep it to two weeks, write a one-sentence goal, and put in less work than you think you can finish. Protect the scope once it starts, and close it on time even if some items are left. You'll learn more from an honest first sprint than a perfect plan.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Where do I create a sprint in Jira?
On the Backlog tab of a company-managed software space, using the Create sprint button in the Backlog section.
Can I create sprints in a Kanban space?
No. Sprints don't apply to Kanban spaces.
What permission do I need?
Most sprint actions need Manage Sprints. Adding work items also needs Schedule work items and Edit work items.
How long should a sprint be?
For teams new to sprints, Atlassian recommends a fixed two weeks.
Can I run two sprints at once?
Only after enabling parallel sprints.
