How to Create a New Sprint in Jira: A 6-Step Guide for Teams
Need to create a new sprint in Jira without messy planning? Follow this 6-step guide to set goals, prioritize work, and launch confidently. Read now.
To create a new sprint in Jira, open your Scrum board’s backlog and select Create sprint. Then add work, agree on a goal, and start the sprint when your team is ready.
It sounds simple, yet sprint setup can become frustrating when the backlog is messy, priorities are unclear, or the team starts without a realistic commitment. A sprint with too much work can leave important tasks unfinished. One with no clear goal can turn daily planning into a string of unrelated updates.
But here's the truth: Jira handles the basic setup in a few steps. The harder part is preparing work your team can actually complete. Here’s how to create the sprint, plan it with care, and keep progress visible after kickoff.
How to create a new sprint in Jira: 6 steps
You can create a sprint from the backlog of a Scrum board. Jira’s labels and controls can vary slightly by project type or interface, but the workflow follows the same basic pattern.
Open your Scrum board’s backlog. In Jira, go to the project and select the relevant Scrum board. Open its backlog view. If you cannot see the backlog or sprint controls, check that you have access to the board and the required permissions.
Select “Create sprint.” Look near the top of the backlog for the Create sprint control. Jira adds a new sprint section to the backlog. You can create a sprint before deciding which work to include.
Name the sprint and set a goal. Use a name your team can recognize, such as “Checkout improvements — May 6.” Add a specific goal, like “Reduce checkout errors and complete payment validation.” A clear goal helps the team make trade-offs when plans change.
Choose work for the sprint. Drag prioritized backlog items into the new sprint, or use the available issue controls. Review each item’s estimate, dependencies, and acceptance criteria. For example, a payment feature may need a validation task before the team can test it.
Check the team’s capacity. Compare the planned work with the people available during the sprint. Account for holidays, support shifts, and other commitments. If someone will be away for two days, reduce the planned workload before kickoff.
Start the sprint. Select “Start sprint,” review the sprint name, duration, start date, end date, and goal, then confirm. Jira moves the sprint into progress. Your team can then track its work from the board.
The key distinction is that creating a sprint prepares a container for planned work. Starting it begins the time period and makes the commitment visible to the team.

Prepare your Jira board before sprint planning
A sprint is only as useful as the work your team can understand and deliver. Before planning, review the backlog for clear priorities, current estimates, and enough detail to discuss each item.
For example, “Improve search” is too broad for a team to estimate confidently. “Show matching products when a shopper enters a partial product name” gives the team a more concrete outcome to discuss.
Check access and board settings
Make sure you are working in a Scrum board that supports a backlog. Jira Kanban boards use a different flow, so you may not see sprint creation controls there.
If the Create sprint option is missing, ask a Jira administrator or project lead to check your board access and sprint permissions. Also confirm that you have opened the intended board, especially when a project has several boards.
Review the backlog for planning readiness
Move the most important work near the top of the backlog. Check that each planned item has a clear description, acceptance criteria, and any estimate your team uses.
Keep large or uncertain work visible during planning. A team might split “Build account settings” into smaller outcomes, such as editing a profile name and changing notification preferences.

Choose a realistic sprint scope
Start with the sprint goal, then select backlog items that support it. This gives your team a reason for choosing the work and a practical guide when new requests appear.
Compare the planned workload with the team’s recent pace and availability. If the team usually completes about 20 story points, planning 35 points during a week with two people away raises the risk of unfinished work.
Include dependencies and uncertainty
Check whether planned items depend on another team, a design decision, or an external service. A task that cannot begin until an approval arrives may need a different sequence or a smaller commitment.
Suppose your team plans a new payment option. The interface, payment service integration, and error handling may be separate tasks, but the team should understand how they fit together before starting.
Keep the commitment understandable
Teams sometimes fill every available hour with planned work. That leaves little room for code reviews, testing, support requests, or unexpected defects.
Leave a reasonable buffer when your work is unpredictable. A smaller sprint commitment with a clear goal is often easier to manage than a packed sprint with several unrelated priorities.
Start the sprint and confirm the details
Before confirming the start, review the sprint name, dates, duration, goal, and planned issues. Jira displays these details in the start dialog, though the exact controls can vary between project configurations.
Pick dates that match your team’s working calendar. A two-week sprint that begins before a public holiday may have fewer working days than the label suggests, so check availability before finalizing the plan.
Use a goal that guides decisions
A useful sprint goal describes the outcome the team wants to achieve. “Complete five tickets” tracks activity, while “Let customers update their delivery address before placing an order” explains the value of the work.
When priorities shift, return to the goal. If a new request does not support it, the team can discuss whether it belongs in the current sprint or a later one.
Track work throughout the sprint
After kickoff, use the Jira board to see which items are in progress, blocked, or complete. Update work as it changes so the board reflects the team’s current understanding.
For example, if a task depends on a delayed design review, mark the blocker and raise it during the team’s daily check-in. That gives the team a chance to find a solution before the delay affects more work.
Review progress without losing the goal
Look at remaining work and blockers regularly. A burndown chart or other built-in report can help your team spot a pattern, such as work staying unfinished until the final days.
Use those signals to ask practical questions. Is a task larger than expected? Is review taking longer? Does the team need help from another group? The goal is to respond early, not to assign blame.
Handle scope changes deliberately
New requests can arrive after a sprint starts. Discuss their urgency, impact on the sprint goal, and the work that would need to move if the team accepts them.
For instance, a high-priority defect may justify changing the plan. If the team adds it, agree on which planned item will move out and communicate the decision clearly.
ONES.com is a unified project management and knowledge management platform powered by ONES Assistant. ONES Project provides project management and is a Jira alternative; ONES Wiki provides knowledge management and is a Confluence alternative. They are sold separately.

For teams that want sprint planning alongside configurable workflows and reporting, ONES Project offers Jira-compatible workflows, sprint management, automation, and custom fields. It is available in cloud and self-hosted deployments, with full feature parity between those versions.
Core capabilities
Backlog planning: When a team needs a clear place to prioritize and prepare work, ONES Project’s project management features help organize items for sprint planning. The result is a more visible path from backlog to sprint.
Sprint management: When teams need to plan and follow work over a timeboxed cycle, sprint management supports organizing work and tracking its progress. Teams can keep the sprint plan connected to daily execution.
Jira-compatible workflows: When a team is familiar with Jira workflows, compatible workflow support can make it easier to represent familiar work stages. The team can structure its process without starting with an unfamiliar model.
Custom workflows and fields: When different teams need different review stages or issue details, custom workflows and fields let administrators adapt the setup. Teams can capture relevant information without relying on a collection of add-ons.
Built-in reporting: When a team needs to review progress or spot delivery patterns, built-in reporting provides a way to examine project work. This can reduce the need to assemble routine updates manually.
Automation: When repetitive project actions take time, automation can handle configured workflow tasks. Teams can reduce manual steps and keep common transitions consistent.
Cloud and self-hosted deployment: When an organization has specific hosting or network needs, ONES.com offers Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Full feature parity between cloud and self-hosted versions gives teams deployment flexibility.
Free plan for up to 30 seats: When a smaller team wants to evaluate the platform, the free plan supports up to 30 seats. This gives the team a way to explore the workflow before deciding whether it fits.
Application scenarios
A team moving from Jira: A software team that already plans work in Jira can consider ONES Project when it wants Jira-compatible workflows, sprint management, and reporting in another project management platform. The team can review its workflow needs and hosting preferences during evaluation.
A team with restricted network requirements: An organization that needs an air-gapped or on-premise deployment can assess ONES Project’s self-hosted options. This lets the team plan sprint work within a deployment model suited to its environment.
Common challenges when creating a Jira sprint
The Create sprint control is missing. Confirm that you opened a Scrum board with a backlog and have the necessary board access and permissions. If the control remains unavailable, ask the Jira administrator to review the board configuration.
The sprint contains too much work. Compare the planned items with team availability, recent delivery pace, and known absences. Remove or defer lower-priority work until the commitment feels achievable.
Work items are too vague to estimate. Clarify the expected outcome and acceptance criteria. Split broad items into smaller pieces, such as separating account profile editing from notification preferences.
Dependencies are discovered after kickoff. Review related work and external approvals during planning. If a dependency becomes blocked, make it visible on the board and discuss its effect on the sprint goal.
New requests disrupt the plan. Assess urgency and impact with the team. If you accept the request, agree on which planned work will move so the sprint commitment stays understandable.
FAQs about creating Jira sprints
Can I create a sprint in a Jira Kanban project?
Jira sprints are associated with Scrum boards, so you generally need a Scrum board with a backlog to create one. A Kanban board focuses on continuous flow and may not show sprint controls. If your team needs timeboxed planning, check whether a Scrum board is available for the project and whether you have access to it.
Can I create a sprint before adding work to it?
Yes. You can create a sprint in the backlog before choosing which issues belong in it. This can help your team prepare a planning area ahead of a meeting. Add prioritized work later, then review estimates, dependencies, and team capacity before starting the sprint.
Can I change sprint dates or the goal after starting?
Jira’s available sprint actions can vary with permissions and project configuration. If the team needs to correct a detail, open the sprint controls and check which fields can be edited. Agree on changes with the team, especially when dates or the goal affect expectations beyond the immediate project group.
What should I do if the sprint is already underway and priorities change?
Discuss the request with the team and compare its urgency with the sprint goal. If it needs to be added, decide what planned work should move out and update the board. This makes the trade-off visible and helps the team understand how the change affects its commitment.
Conclusion
Creating a sprint in Jira means opening a Scrum board’s backlog, selecting Create sprint, choosing focused work, and confirming the plan when you start. The six steps are quick; thoughtful preparation makes them useful.
Keep the sprint goal clear, account for team capacity, and surface dependencies early. If planning feels overloaded or unfinished work keeps rolling forward, revisit the backlog and scope before the next kickoff.
That small change can help your team move from a crowded list of tasks to a manageable sprint with a shared purpose. When your team is evaluating its project management workflow, ONES Project is another option to consider for sprint planning and Jira-compatible workflows.