Jira Sprint Setup: How to Create a First Sprint in 6 Steps
Need to know how to create new sprint in Jira? Use these 6 steps to set goals, scope work, and launch confidently. Read now to get started.
A sprint can look simple until you’re staring at Jira’s backlog, unsure where to begin. Create it too late, and planning gets rushed; start it without clear work, and the team may spend its first day sorting out confusion. Even a small setup mistake can make progress harder to track.
Here’s the truth: creating a sprint takes only a few steps, but a useful sprint needs a clear goal, a realistic scope, and the right issues. I’ll walk you through creating your first sprint in Jira, adding work, setting dates, and starting it with confidence. You’ll also see how to troubleshoot common snags and keep the sprint focused once work begins.
How to create a new sprint in Jira in six steps
Quick answer: Open a Scrum board’s backlog, create a sprint, add and prioritize issues, set the sprint goal and dates, check the scope, then start the sprint.
Jira’s labels and layout can vary slightly between versions, but the basic workflow is similar. You’ll need access to a Scrum board and permission to manage sprints.
-
Open the correct Scrum board. In Jira, go to the project or board where your team plans work. Open its backlog and confirm the board is a Scrum board. A Kanban board does not use the same sprint-planning workflow.
-
Create a sprint. In the backlog, select the option to create a sprint. Jira adds a new sprint area to the board, usually near the top of the backlog. You can create a sprint before adding issues, so don’t worry if it appears empty.
-
Add the right issues. Drag backlog issues into the sprint, or use the available controls to move them. Choose work that supports one outcome, such as completing a checkout improvement, rather than adding every high-priority request.
-
Prioritize and estimate the work. Put the most important issues near the top and review their estimates, if your team uses them. Check dependencies and team availability. For example, an issue that needs design approval may not be ready for the first day.
-
Set the sprint details. Select the sprint’s start option or edit its details, depending on your Jira layout. Add a concise goal, choose a duration, and confirm the start and end dates. A useful goal describes an outcome, such as “Let shoppers complete checkout with saved addresses.”
-
Review the scope and start the sprint. Confirm the team understands the goal, the selected issues are ready, and the dates fit the team’s calendar. Select Start sprint when you’re ready. Jira moves the sprint into active work, where the team can track progress on its board.
Creating a sprint and starting one are separate actions. You can prepare a future sprint in the backlog, refine its scope, and start it when the team is ready.

What to prepare before sprint planning
A little preparation makes the six steps easier. Before creating a sprint, check that the backlog contains issues your team understands and can complete. Each issue should have a clear description, acceptance criteria where useful, and an owner or team responsible for clarifying it.
Here’s why: unclear work creates delays after the sprint begins. Imagine a team selects “Improve account page,” but nobody knows whether that means changing the layout, adding a feature, or fixing an error. A short conversation before planning can turn that vague request into work the team can assess.
Also check team availability. Holidays, support coverage, and planned leave affect how much work is realistic. If one developer will be away for three days, planning the sprint as if the whole team were available can set an unrealistic expectation.
How to choose a realistic sprint scope
Start with the sprint goal, then select issues that contribute to it. This keeps planning focused on an outcome instead of becoming a contest to fit in as many tasks as possible. A team improving onboarding might select an account setup issue, a welcome email task, and a small usability fix.
Compare the proposed scope with the team’s recent capacity and current commitments. If your team typically finishes about 20 story points, a 35-point plan deserves a second look. That number is a reference, not a promise; complexity, interruptions, and team availability can all change what is achievable.
The best part? You can leave lower-priority work in the backlog. A focused sprint is easier to discuss and adjust than a crowded one where unrelated requests compete for attention.
Set a sprint goal and dates your team can use
A sprint goal should help the team make decisions during the sprint. “Finish 12 issues” describes a quantity, while “Help new customers complete account setup without support” describes an outcome. The second version gives the team a shared reason for its selected work.
Choose dates that reflect how your team actually works. A two-week sprint may suit a team that plans, builds, and reviews work on a regular cadence. A shorter sprint may fit work that changes quickly, while a longer one may require more coordination to keep priorities clear.
Let me explain: dates help organize the work, but they do not make an oversized scope achievable. If the sprint ends on Friday and several issues are still uncertain, revisit the scope before starting rather than relying on the calendar to solve the problem.
Check sprint progress without losing focus
Once the sprint is active, use the board to review work in progress and spot issues that are stalled. A task sitting in the same status for several days may need a decision, help from another teammate, or a smaller next step.
For example, if testing is blocked because an interface change is unfinished, the team can discuss whether to pair on the change or adjust the order of work. The sprint board makes that conversation easier when issues have clear owners and statuses.
When priorities change, discuss the impact with the team before adding work. A new urgent request may be important, but adding it without removing or renegotiating other work can make the sprint goal less realistic.
ONES.com solution for connected project and knowledge management

Value proposition
ONES.com brings project management and knowledge management together through separately sold products: ONES Project for project work and ONES Wiki for team knowledge. If you’re evaluating a Jira alternative, ONES Project offers Jira-compatible workflows, sprint management, custom fields, automation, and reporting, with cloud and self-hosted deployment options.
Core capabilities
Issue tracking is scattered across tools: ONES Project provides project and issue management in one workspace, helping teams keep sprint work organized.
Sprint planning is hard to follow: Sprint management supports planning and tracking iterations, helping teams review work against an agreed goal.
Existing workflows are difficult to adapt: Jira-compatible workflows and custom workflows let teams shape processes around their needs.
Teams need fields that match their work: Custom fields capture relevant issue details, making work easier to assess and coordinate.
Progress reporting takes extra effort: Built-in reporting gives teams a way to review project progress without relying on a separate reporting add-on.
Repeated manual tasks slow work down: Automation can handle routine workflow actions, reducing the steps people need to complete by hand.
Project decisions are hard to find later: ONES Wiki offers knowledge management as a separate product, helping teams organize working practices and guidance alongside their project activity.
Deployment requirements limit options: ONES.com supports Cloud, On-Premise, Private Cloud, and Air-gapped deployments. Its cloud and self-hosted versions have full feature parity.
ONES Project is positioned as a Jira alternative, while ONES Wiki is a Confluence alternative. The products are sold separately, so teams can choose the project or knowledge capabilities they need. ONES.com offers a free plan for up to 30 seats.
Native capabilities for workflows, fields, reporting, and automation can reduce reliance on plugins for teams whose needs fit those features. Self-hosted deployment may also suit organizations that need to run their project environment on-premise or in a restricted network.
Application scenarios
A software team moving from Jira: The team can map its Jira-compatible workflows, configure custom fields, and plan sprints in ONES Project. It can evaluate reporting and automation needs as part of the transition.
An organization with deployment requirements: A team that cannot use a standard cloud setup can assess On-Premise, Private Cloud, or Air-gapped deployment options while retaining feature parity with the cloud version.
A team connecting project work with guidance: A group can manage tasks in ONES Project and keep working practices in ONES Wiki, using the two products together if both are needed.
Common challenges when setting up a Jira sprint
The sprint option is missing
Problem: You can open a board but cannot find the sprint creation control. The board may be Kanban, you may be looking outside its backlog, or your account may lack sprint-management permission.
Solution: Confirm that you’re using a Scrum board and open its backlog. If the option is still unavailable, ask a Jira administrator to review your permissions and board configuration.
The sprint contains too much work
Problem: Every issue seems urgent, so the team adds more work than it can finish. This can leave the goal unclear and make progress difficult to interpret.
Solution: Prioritize issues that support the sprint goal, then leave the rest in the backlog. Compare the planned scope with team availability and recent delivery patterns before starting.
The team cannot agree on what an issue means
Problem: Team members interpret an issue differently, or key details are missing. Work may stall while the team decides what “done” means.
Solution: Clarify the expected outcome and acceptance criteria during refinement. Split an issue if it combines several independent outcomes or cannot be estimated with confidence.
The sprint dates do not match team availability
Problem: The sprint overlaps with holidays or leave, but the planned scope assumes everyone is available. The team may discover the mismatch only after work begins.
Solution: Check the team calendar before setting dates and selecting issues. Reduce the scope when availability is lower, and make the sprint goal achievable within the actual working time.
FAQs about creating a sprint in Jira
Can I create a Jira sprint before adding any issues?
Yes. You can create a sprint in the backlog before moving issues into it. This can be useful when you’re preparing future sprints or organizing a planning session. Add and prioritize work later, then check that the sprint has a clear goal and realistic scope before starting it.
Can I create a sprint in a Kanban board?
Jira sprints are part of Scrum planning, so you need a Scrum board to use the standard sprint workflow. A Kanban board focuses on continuous flow rather than fixed sprint cycles. If your team needs sprint planning, check whether a Scrum board is available or appropriate for your project.
What is the difference between creating and starting a sprint?
Creating a sprint adds it to the backlog so you can prepare its work. Starting a sprint makes it active and begins the sprint period. Before you start, review the selected issues, goal, dates, and team availability. Keeping these actions separate lets you plan ahead without starting work prematurely.
Can I change a sprint after it starts?
Jira lets teams make some changes to active sprint work, but the best response depends on what changed and how your team manages commitments. Discuss additions or removals with the team, consider their effect on the sprint goal, and make the decision visible. Avoid quietly adding work without reassessing the scope.
Conclusion
To create your first Jira sprint, open a Scrum board’s backlog, create the sprint, add focused work, set a useful goal and dates, and check the scope before starting. A clear goal and realistic workload make it easier for your team to plan, track progress, and respond when priorities shift.
But here's the truth: sprint setup is only the beginning. If planning feels rushed or issues remain unclear, pause to refine the work before the sprint starts. That small step can prevent avoidable confusion and help your team make the sprint count.