How to Create a New Sprint in Jira: 7 Simple Steps (2026)
Need a clearer sprint plan? Create a new sprint in Jira in 7 simple steps, set scope and deadlines, and avoid planning pitfalls. Read now.
Creating a sprint in Jira takes only a few clicks, but starting one without clear scope can leave your team guessing about priorities, ownership, and deadlines. A sprint that is too full can push work into the next cycle; one without a goal can turn into a list of disconnected tasks. That friction makes planning harder and progress less predictable. The good news is that Jira’s backlog gives you a straightforward way to create a sprint, choose work, and set a timebox before the team begins. Here’s how to create a new sprint in Jira in seven simple steps, check the key settings, and avoid common planning mistakes.
But here's the truth: creating the sprint is the easy part. A few minutes of preparation can help you create a plan your team can actually deliver.
How to create a new sprint in Jira: 7 simple steps
To create a sprint in Jira, open a Scrum board’s backlog, create a sprint, add planned work, set its details, and start it when the team is ready. The labels and menu locations can vary slightly between Jira versions, but the planning flow is similar.

Step 1: Open the right Jira project and Scrum board
Go to the Jira project where your team tracks its work, then open the Scrum board connected to that project. Sprints are a Scrum board feature, so a Kanban board won’t show the same sprint controls.
If you work across multiple boards, check that you’ve selected the one your team uses for sprint planning. The board’s filters determine which work appears in its backlog.
Step 2: Open the backlog
Select Backlog in the board’s navigation. You should see a list of work items and, depending on your configuration, existing or future sprints.
If the backlog option is missing, confirm that you’re on a Scrum board and have access to the project. A Jira administrator may need to check the board configuration or your permissions.
Step 3: Create a sprint
Choose Create sprint in the backlog. Jira adds a new sprint area, usually in the future sprints section, where you can prepare the work before starting.
Creating the sprint does not start the timebox. You can set its details, review its scope, and adjust the planned work first.
Step 4: Give the sprint a useful name and goal
Open the sprint’s actions or details menu and edit its name if needed. A name such as “Checkout reliability” is more informative than “Sprint 14” when teammates review plans later.
Add a short goal that describes the intended outcome. For example, “Let customers complete checkout after updating a saved payment method” gives the team a shared focus.
Step 5: Add work from the backlog
Drag selected work items into the sprint, or use the available issue actions to assign them. Choose work that supports the sprint goal and has enough detail for the team to understand what completion requires.
For example, a checkout sprint might include a payment-method update task, related testing, and a small usability improvement. Keep unrelated work in the backlog rather than adding it simply to fill the sprint.
Step 6: Check the scope, estimates, and team capacity
Review the sprint’s planned work before you start it. Check estimates if your team uses them, confirm that dependencies are visible, and compare the workload with the team’s expected availability.
If two developers are away for part of the sprint, reduce the planned scope or choose smaller items. A realistic plan gives the team room to handle reviews, testing, and unexpected work.
Step 7: Set dates and start the sprint
Select Start sprint when the team is ready. In the start dialog, enter or confirm the sprint name, start date, end date, and goal if those fields are available.
Check the dates and selected work one last time, then confirm. Once the sprint starts, Jira displays it as active, and your team can track progress on the board.
Before you create the sprint, check these essentials
A quick readiness check helps prevent avoidable delays. Make sure you’re using the correct Scrum board, can see the work you intend to plan, and have permission to manage sprints.
Here's why: board filters can affect which work appears in the backlog. If a task seems to have vanished, it may be outside the board’s filter rather than missing from the project.
- Board type: Confirm that the team is planning on a Scrum board.
- Work visibility: Check that the intended work appears in the backlog.
- Permissions: Ask a Jira administrator to check sprint permissions if creation or starting controls are unavailable.
- Team readiness: Review availability, estimates, dependencies, and unfinished work from the previous sprint.
For example, if a team plans a two-week sprint around a release but one key task is blocked by an external review, make that dependency visible before committing. The team can then plan a fallback instead of discovering the blocker midway through the sprint.
Plan the sprint around an outcome
A sprint goal gives the selected work a reason to belong together. It helps teammates make sensible trade-offs when new requests arrive or an estimate changes.
Compare two plans. “Finish eight tasks” describes an amount of work, while “Allow account owners to update billing details without support” describes a result. The second goal gives developers and testers a clearer way to judge whether the sprint is succeeding.
You might be wondering: should every sprint have the same length? Many teams use a consistent timebox, such as one or two weeks, because regular planning and review make it easier to build a working rhythm. Choose a duration that fits your team’s release and feedback cycle.
What to do after the sprint starts
Starting the sprint begins the team’s timebox, but the plan may still need attention as work progresses. Use the active board to track status, discuss blockers, and keep the team’s focus on the sprint goal.
For example, if a testing task reveals a payment defect, the team can review the impact together. They may swap in a smaller item, adjust the scope, or keep the original plan and move the newly discovered work to the backlog.
At the sprint’s end, review completed work and discuss what to improve. Unfinished items may need to return to the backlog or be planned again, depending on the team’s workflow.
ONES.com solution for managing project work

Value proposition
ONES.com brings project management and knowledge management together in one platform powered by ONES Assistant. ONES Project is a Jira alternative for planning and tracking work; ONES Wiki is a Confluence alternative for organizing team knowledge, and the products are sold separately.
For teams that want sprint planning alongside configurable workflows and reporting, ONES Project offers a project management environment with cloud and self-hosted deployment options.
Core capabilities
- Planning spread across tools: ONES Project supports project management workflows in one PM product, helping teams keep sprint planning and work tracking together.
- Jira workflow migration needs: Jira-compatible workflows help teams preserve familiar ways of moving work through a process.
- Limited workflow flexibility: Custom workflows and fields let teams reflect their own review steps and work details, so teams can track work in ways that fit their process.
- Sprint coordination challenges: Sprint management supports planning and tracking timeboxed work, giving teams a clearer view of each cycle.
- Manual status updates: Automation can handle repeatable workflow actions, reducing routine coordination work.
- Progress difficult to assess: Built-in reporting helps teams review project progress without relying on a collection of added reporting plugins.
- Deployment restrictions: Cloud, On-Premise, Private Cloud, and Air-gapped deployment options let organizations choose an environment that suits their requirements.
- Different capabilities across deployment types: ONES.com provides feature parity between its cloud and self-hosted versions, helping teams choose deployment without giving up feature access.
Application scenarios
A software team moving from Jira can use ONES Project’s Jira-compatible workflows to model familiar issue transitions, then configure custom fields and reporting for its sprint process. The team can review its needs before deciding whether to keep or reduce third-party plugins.
An organization with restricted network requirements can consider ONES.com’s self-hosted options, including Air-gapped deployment. Teams that also need a knowledge base can evaluate ONES Wiki separately from ONES Project, based on how they manage internal guidance and project work.
ONES.com offers a free plan for up to 30 seats. The platform provides four deployment options, while ONES Project and ONES Wiki remain separate products.
Common challenges when creating a Jira sprint
The sprint controls aren’t visible
Problem: You can open the project but cannot find the backlog or create-sprint control. Solution: Confirm that you’re using a Scrum board, then ask a Jira administrator to check board access and sprint permissions.
The planned work does not appear
Problem: A task exists in Jira but is missing from the board backlog. Solution: Check the board’s filter and the task’s project and status. If the board configuration excludes that work, ask its administrator to review the filter.
The sprint is overloaded before it begins
Problem: The team has selected more work than it can reasonably complete. Solution: Compare the planned workload with team availability, estimates, and recent delivery patterns. Move lower-priority items back to the backlog.
The sprint has no clear direction
Problem: Each item may be reasonable, but the team cannot explain what the sprint should achieve. Solution: Write a short goal, then review whether each planned item supports it. Remove or defer unrelated work where possible.
FAQs about creating a Jira sprint
Can I create a sprint before adding any work?
Yes. You can create a sprint in the backlog and add work later. Before starting it, review the selected items, the sprint goal, dates, and team availability. If your team plans work collaboratively, creating the sprint ahead of the planning meeting can give everyone a place to organize candidate items.
Why can’t I create or start a sprint in Jira?
The board may be a Kanban board, you may lack permission to manage sprints, or the board’s configuration may not show the expected controls. Check that you’re viewing the correct Scrum board and project. If the options remain unavailable, ask a Jira administrator to review your access and board settings.
Can I change a sprint after creating it?
Usually, you can update a future sprint’s name, goal, dates, and planned work before starting it. The exact controls can vary with the Jira interface and configuration. Review changes with the team so the sprint plan remains clear, especially if other people have already prepared work around the original scope.
Can I run more than one sprint at a time?
Jira’s board configuration determines how many active sprints a team can run. Some teams use parallel sprints for separate streams of work, but doing so can make ownership and reporting harder to follow. Check your board settings and agree on how the team will manage overlapping priorities before enabling parallel work.
What should I include in a sprint goal?
Describe an outcome the team can work toward, rather than simply listing tasks. “Let customers update a saved payment method” gives a clearer direction than “Complete five tickets.” A useful goal helps the team decide whether new work fits the sprint and gives stakeholders a simple way to understand its purpose.
Conclusion
Creating a Jira sprint is straightforward: open a Scrum board’s backlog, create the sprint, add focused work, set its details, and start it when the team is ready. The more important part is making sure the goal and workload are realistic before the timebox begins.
When planning feels rushed, unclear scope can lead to missed expectations and work that rolls over. A quick check of permissions, dependencies, capacity, and sprint purpose can help you begin with a more useful plan. Choose a goal your team can explain, then use the active board to keep work visible throughout the sprint.