How to Create a New Sprint in Jira: A Step-by-Step Guide
Wondering how to use jira create new sprint without mistakes? Follow this guide to set dates, manage issues, and launch confidently. Read now!
Creating a sprint in Jira sounds simple until the option is missing, the dates are unclear, or the wrong issues land in the iteration. One small setup mistake can leave your team starting late and reporting against the wrong goal.
That confusion becomes expensive when developers, testers, and product managers work from different assumptions. A sprint may appear active while the team is still planning, or unfinished work may get carried forward without a clear decision.
But here's the truth: creating a sprint takes only a few minutes when your board, permissions, backlog, and sprint goal are ready. This guide shows you exactly how to create, configure, start, and manage a new Jira sprint.
How to Create a New Sprint in Jira
To create a sprint in Jira, open the relevant Scrum board, go to the backlog, select Create sprint, add the right work items, set the dates, and start the sprint when planning is complete.
1. Open the Correct Scrum Board
Sign in to Jira and open the Scrum board connected to your project. You can usually find boards through the main navigation, project area, or board directory.
Check the board name before continuing. A team may have separate boards for mobile development, platform work, maintenance, or several product lines.
If you choose the wrong board, the sprint may use the wrong filter and show an incomplete set of issues. That creates confusion before work even begins.
2. Go to the Backlog
Open the board and select Backlog. In a Scrum project, this area normally shows the product backlog, current sprint, and future sprints.
Look for the Create sprint button near the top of the backlog. Jira may place it above the issue list or near the sprint controls, depending on your version and screen layout.
If you cannot see the button, your board may be a Kanban board. Sprint planning requires a Scrum board, and your Jira permissions may also affect what actions appear.
3. Select Create Sprint
Click Create sprint. Jira adds a new sprint container to the backlog, usually with a temporary name such as “Sprint 1” or “New sprint.”
At this point, the sprint exists as a planning container. It has not started yet, so your team can still adjust its work items, name, dates, and goal.
Keep the sprint in the future until the team has agreed on its scope. Starting it too early can affect reporting and make planning changes harder to interpret.
4. Add Issues to the Sprint
Move issues from the product backlog into the new sprint. Depending on your Jira layout, you can drag issues into the sprint or use the issue action menu.
Choose work that fits the team’s capacity and supports one clear outcome. For example, a checkout improvement sprint might include payment validation, error messaging, and regression testing.
Review each issue before adding it. Confirm that the description is understandable, acceptance criteria are available, and dependencies are visible.
5. Rename the Sprint and Add a Goal
Give the sprint a useful name if your team follows a naming convention. You might use “Sprint 24,” “April Checkout Improvements,” or another label that makes reporting easy to follow.
Add a sprint goal that describes the result the team wants to achieve. “Improve checkout reliability for guest customers” gives stronger direction than “Finish assigned tickets.”
The goal helps the team make trade-offs. When a new request appears, you can ask whether it supports the agreed outcome before adding it.
6. Set the Start Date and End Date
Open the sprint details and choose the planned start and end dates. Many teams use a one- or two-week cadence, although the right duration depends on the product and delivery rhythm.
Make sure the dates match your team calendar. A sprint that ends during a company holiday may need a shorter working period or a different review date.
For example, a two-week sprint starting on Monday and ending on Friday gives the team a predictable planning, review, and retrospective cycle.
7. Review Scope Before Starting
Before you start the sprint, review the selected issues with the team. Look for oversized work, unclear ownership, missing dependencies, and items that belong in a different queue.
Compare the planned scope with recent delivery performance. If your team usually completes 30 story points, planning 70 points creates a warning signal rather than a useful challenge.
Here's why: a sprint backlog is a commitment guide, not a wish list. A smaller, coherent scope makes progress easier to understand.
8. Start the Sprint
When planning is complete, select Start sprint. Jira may ask you to confirm the sprint name and dates before activating it.
Once started, the sprint appears in the active sprint view. Team members can move issues through workflow columns, update estimates, record time, and monitor progress.
After activation, avoid changing the scope casually. If urgent work must enter, record the reason and discuss which existing work should leave.
9. Confirm the Active Sprint View
Open Active sprints and verify that the board displays the expected issues. Check that statuses, assignees, estimates, and priority values look correct.
Ask one team member to confirm that the workflow reflects how work actually moves. For example, a team may need columns for development, code review, testing, and release readiness.
This final check catches setup problems before they affect daily stand-ups or sprint reporting.
What You Need Before Creating a Sprint
Jira can create a sprint quickly, but a good sprint depends on preparation. You need a Scrum board, access to manage sprints, a usable backlog, and enough planning information to make a sensible commitment.
Confirm the Board Type
Scrum boards support planned sprints and sprint reports. Kanban boards focus on continuous flow and usually do not use the same sprint planning process.
If your team works continuously, creating a sprint may add unnecessary ceremony. If your team plans work in fixed cycles, a Scrum board is usually the better fit.
Check Your Permissions
Jira permissions control who can create, edit, start, and manage sprints. A missing button may indicate an access problem rather than a navigation mistake.
Ask a Jira administrator to review your project role and board configuration if you can view issues but cannot manage sprint settings.
Prepare a Refined Backlog
Backlog refinement gives the team enough detail to select realistic work. Useful preparation includes clear acceptance criteria, updated priorities, visible dependencies, and reasonable estimates.
For example, “Improve search” may be too broad for a sprint. “Add spelling suggestions to product search results” gives the team a clearer piece of work.
How to Plan a Sprint That Your Team Can Finish
Creating the sprint is the mechanical part. Planning the right scope requires a conversation about capacity, risk, dependencies, and the outcome that matters most.
Start With Capacity
Check planned holidays, training, support rotations, and other commitments. A team with three engineers away for two days has less delivery capacity than a normal sprint.
Velocity can provide context, but it should not become a rigid quota. Use recent performance as a planning signal alongside real availability and work complexity.
Group Work Around an Outcome
Choose issues that contribute to a meaningful result. A sprint focused on onboarding might include account creation improvements, welcome emails, and analytics validation.
Separate unrelated requests unless they are genuinely urgent. Mixing infrastructure upgrades, marketing changes, and checkout repairs can make the sprint difficult to explain.
Identify Dependencies Early
A blocked issue can consume several days while the team waits for another group. During planning, ask whether work depends on an API, design decision, security review, or external approval.
Link related issues and assign ownership for dependency follow-up. This gives the team a visible action instead of leaving the risk hidden in a comment.
How to Manage Scope After the Sprint Starts
Scope changes happen. A production incident, compliance request, or customer-impacting defect may require immediate attention.
Use a Clear Change Rule
Agree on who can approve new work and how the team records the trade-off. If a new issue enters, remove or defer work with similar effort when possible.
For example, adding a one-day urgent defect may require moving a lower-priority testing task into the next sprint. The decision keeps capacity visible.
Watch the Burndown and Issue Flow
Jira’s sprint reports can show whether remaining work is decreasing as expected. A flat burndown may indicate blocked issues, late testing, or estimates that do not reflect actual effort.
Use the report as a conversation starter. It cannot explain every cause by itself, so compare the chart with team updates and issue history.
Handle Unfinished Work Deliberately
When the sprint ends, review incomplete issues with the team. Decide whether each item should move into the next sprint, return to the backlog, or be closed after the expected outcome changes.
Carrying every unfinished issue forward can hide planning problems. A deliberate decision creates better information for the next cycle.
Common Jira Sprint Problems and Fixes
| Problem |
Likely cause |
Practical fix |
| Create sprint is missing |
The board may be Kanban, or your permissions may be limited. |
Confirm the board type and ask an administrator to review sprint permissions. |
| The wrong issues appear |
The board filter may exclude the project, issue type, or status you need. |
Review the board filter and confirm that the issues meet its conditions. |
| Issues disappear from the sprint |
Someone may have changed the board filter, project, status, or issue location. |
Check the issue details, board configuration, and backlog location. |
| The team cannot start the sprint |
Another sprint may already be active, or the account lacks permission. |
Review active sprints and confirm the user’s sprint management access. |
| The sprint is overloaded |
Capacity, dependencies, or issue size were underestimated. |
Split large issues, remove lower-priority work, and record the planning decision. |
Jira Sprint Management Solution: ONES.com
ONES.com brings project management and knowledge management together through ONES Project and ONES Wiki. ONES Project can support Jira-compatible workflows, sprint planning, reporting, and controlled delivery across cloud or self-hosted environments.
If your team wants a Jira alternative with native capabilities and fewer plugins to maintain, ONES.com can provide a more centralized working environment. ONES Project and ONES Wiki are sold separately.
Core Capabilities
- Scattered sprint planning → ONES Project sprint management → Keep backlog items, sprint scope, estimates, and progress in one project workspace.
- Complex workflow setup → Custom workflows and fields → Adapt issue states and attributes to match your team’s approval and delivery process.
- Heavy plugin dependence → Native project capabilities → Reduce the number of separate extensions needed for reporting, automation, and planning.
- Unclear delivery status → Built-in reporting → Give project leads clearer visibility into sprint progress, workload, and delivery trends.
- Manual recurring actions → Automation → Trigger routine updates and workflow transitions when defined conditions are met.
- Disconnected team knowledge → ONES Wiki → Store product guidance, decision records, and working practices beside project activities.
- Restricted deployment requirements → On-premise, private cloud, or air-gapped deployment → Choose an environment that matches security and network constraints.
- Inconsistent experience across environments → Feature parity between cloud and self-hosted versions → Keep the same core capabilities when deployment requirements change.
- Limited initial rollout budget → Free plan for up to 30 seats → Let a small team evaluate the platform before expanding its use.
Application Scenarios
A software team moving away from Jira can recreate familiar sprint workflows in ONES Project while retaining issue tracking, sprint management, custom fields, automation, and reporting. This can reduce retraining when the team already understands Scrum practices.
A regulated engineering group may need self-hosted deployment because project activity must remain inside a controlled network. ONES.com supports cloud, on-premise, private cloud, and air-gapped deployment options.
A product organization can connect delivery work with internal guidance through ONES Wiki. A sprint issue might link to release procedures, testing instructions, or a product decision page without forcing the team to search across disconnected systems.
Common Challenges When Creating Jira Sprints
Challenge: You Cannot Find the Sprint Button
Solution: Confirm that you are using a Scrum board and viewing its backlog. If the button remains unavailable, ask an administrator to verify your permission to manage sprints.
Also check whether the board belongs to the expected project. Similar board names can make this mistake surprisingly common in larger organizations.
Challenge: The Sprint Contains Too Much Work
Solution: Compare the proposed scope with team availability and recent delivery patterns. Remove low-priority issues before the sprint starts.
Split oversized work into smaller outcomes when possible. Smaller issues reveal progress earlier and make blocked work easier to isolate.
Challenge: The Sprint Goal Is Vague
Solution: Describe the customer or business result the team wants to achieve. Replace “complete backend tasks” with “reduce checkout failures for guest customers.”
A clear goal helps the team evaluate new requests and decide what can move when circumstances change.
Challenge: Work Enters Without Discussion
Solution: Set a simple scope-change rule. Require a product owner, delivery lead, or agreed team representative to approve urgent additions.
Record what entered, why it mattered, and what moved out. That history improves future planning conversations.
Challenge: Unfinished Work Keeps Rolling Forward
Solution: Review incomplete issues during the sprint closeout. Re-estimate or split work when its original shape no longer reflects reality.
Use repeated rollover as a signal to investigate refinement quality, dependencies, testing delays, or excessive sprint scope.
FAQs About Creating Sprints in Jira
Can I create a sprint in a Kanban board?
Jira sprints are designed for Scrum boards, so the sprint creation control may not appear on a Kanban board. If your team needs fixed planning cycles, create or select a Scrum board with an appropriate board filter. If the board is already Scrum and the control is missing, check your sprint management permissions with a Jira administrator.
Can I create several future sprints?
Yes, teams can usually create future sprints for upcoming planning cycles. This can help with roadmap visibility, especially when the team follows a predictable cadence. Keep future sprint scope flexible, though. Adding detailed commitments too early may create rework when priorities or capacity change.
Can I change the sprint dates after creating it?
You can usually edit the planned dates before starting the sprint. After activation, date changes may affect reporting and should be handled carefully. Check the sprint settings available in your Jira version, then communicate any adjustment clearly so the team understands the new timeline.
What happens to incomplete issues when a sprint ends?
Jira generally gives you options to move incomplete issues into another sprint or return them to the backlog. Review each issue before choosing. A defect that still matters may enter the next sprint, while an outdated request may need reprioritization or closure.
Can I start a new sprint while another sprint is active?
Jira may allow multiple active sprints when parallel sprint settings are enabled, although many teams use one active sprint per board. Check your board configuration and team process before doing this. Parallel sprints can help separate workstreams, but they may complicate reporting and ownership.
Why are some backlog issues unavailable for my sprint?
The board filter may exclude those issues because of project, issue type, status, or other conditions. An issue may also belong to another board or have a workflow state that the board does not display. Review the issue details and board filter to identify the mismatch.
Conclusion
Creating a Jira sprint is straightforward: open the correct Scrum board, enter the backlog, create the sprint, add suitable issues, set the dates, define the goal, and start it after a scope review.
The harder part is choosing work the team can realistically finish. Clear preparation, visible dependencies, sensible capacity planning, and deliberate scope control turn a sprint container into a useful delivery cycle.
But here's the truth: a sprint will not solve unclear priorities by itself. If your team keeps fighting scattered planning, excessive plugins, or disconnected knowledge, a unified platform such as ONES.com may offer a practical alternative for managing delivery and team information.