How to Create a Sprint in Jira: A Step-by-Step Guide [2026]

Need to create a sprint in Jira? This 2026 guide covers jira create sprint steps, goals, dates, and backlog planning. Read now!

Creating a sprint in Jira sounds simple until the button is missing, the dates are unclear, or unfinished work gets added without a plan. A rushed setup can leave your team with overlapping sprints, confusing reports, and tickets that do not match the sprint goal.

That frustration grows when your backlog is large. You may spend more time fixing sprint settings than preparing the work itself. A small configuration mistake can also affect velocity, burndown charts, and stakeholder expectations.

Here’s the solution: create the sprint from the backlog, give it a clear goal, set realistic dates, and move only ready work into it. This guide walks you through the process step by step, including permissions, planning tips, common problems, and practical alternatives.

How to Create a Sprint in Jira

To create a sprint in Jira, open your Scrum project’s Backlog, select Create sprint, add prepared issues, set the sprint details, and start it when planning is complete. You usually need permission to plan or manage sprints in the project.

Jira product screenshot

Step 1: Open the Scrum project backlog

Sign in to Jira and open the Scrum project where you want to plan the sprint. From the project navigation, select Backlog.

You should see your backlog along with any future sprints. Jira shows different options depending on your project type, board configuration, and permissions.

Make sure you are working with a Scrum board. Kanban boards generally do not use sprints in the same way.

Step 2: Select “Create sprint”

Look above the backlog for the Create sprint button. Jira typically adds a new future sprint near the top of the backlog.

If you cannot see the button, check whether:

You have permission to manage sprints.
The board is connected to the project you opened.
You are viewing a Scrum board rather than a Kanban board.
Another sprint is already active and your Jira setup limits parallel sprints.

The new sprint may receive an automatic name, such as “Sprint 1.” Rename it before planning if your team uses a consistent naming convention.

Step 3: Give the sprint a clear name

Choose a name that helps your team identify the sprint quickly. You might use a sequence, date range, or short objective.

Sprint 24 for a simple sequential approach.
Checkout stability — March 4 when the sprint has a strong theme.
2026-W10 for teams that plan by calendar week.

Avoid names such as “New Sprint” or “Next Sprint.” They provide little context when someone reviews reports months later.

Step 4: Review the backlog before adding work

Before moving issues into the sprint, review their readiness. Each issue should have enough detail for the team to understand the expected result, acceptance criteria, and dependencies.

For example, “Improve checkout” is usually too broad for one sprint. “Show an inline error when a card payment fails” gives the team a clearer outcome.

Check the issue status, priority, estimate, owner, and linked work. Remove blocked or unclear issues from consideration until the team can act on them.

Step 5: Add issues to the sprint

Drag prepared issues from the backlog into the new sprint. You can also use Jira’s issue actions to move several issues at once, depending on your interface.

Keep the sprint focused. A team might select ten small improvements, three medium features, and one technical task. The right mix depends on capacity and complexity, rather than issue count alone.

Be careful with items that have unresolved dependencies. If a payment service update must happen before your team can test checkout, link the work and confirm the sequence first.

Step 6: Set the sprint goal

Select the sprint’s details and write a short goal. The goal should describe the result the team wants to achieve, not merely list tickets.

For example:

“Reduce checkout payment failures and improve recovery messaging.”
“Prepare the mobile release for internal testing.”
“Complete the first version of role-based access controls.”

A useful goal helps the team make trade-offs. If a new request appears during the sprint, you can ask whether it supports the goal before adding it.

Step 7: Set start and end dates

Choose a start date and end date that match your team’s working rhythm. A two-week sprint should usually cover ten working days, excluding holidays and planned closures.

Confirm the time zone and calendar assumptions for distributed teams. A sprint ending at midnight in one region may end at a different local time elsewhere.

Do not extend the sprint automatically when work remains unfinished. Review the incomplete issues and decide whether to return them to the backlog or move them into the next sprint.

Step 8: Start the sprint

When planning is complete, select Start sprint. Jira may ask you to confirm the sprint name, dates, and goal before activating it.

Starting the sprint changes how Jira displays the work. Active sprint reports, burndown charts, and sprint boards now use the selected sprint as a reporting period.

Take one final look before confirming. Make sure the team understands the goal, planned work, dependencies, and definition of done.

Step 9: Monitor the sprint after launch

Creating the sprint is only the beginning. During execution, review progress on the active sprint board and watch for blocked work or major scope changes.

Use the burndown chart to compare remaining work with time left. A flat line may indicate that issues are not being updated. A sharp increase may signal scope being added after the sprint started.

At the end, hold a review and retrospective. Compare the intended goal with the actual result, then use those findings when planning the next sprint.

What You Need Before Planning a Sprint

Good sprint setup begins before you click the creation button. Jira can organize work, but it cannot decide whether an issue is understandable, achievable, or valuable.

Confirm the project and board type

Jira has multiple project experiences, configurations, and board types. The exact labels may vary across Jira editions and customized environments.

Open the board you use for Scrum planning. If the backlog does not show sprint controls, ask a Jira administrator to check the board filter and project permissions.

Check sprint permissions

Jira commonly separates the ability to create or edit issues from the ability to manage sprints. You may be able to add a ticket while still lacking permission to create or start a sprint.

Ask for the relevant project permission if the control is unavailable. An administrator should also verify that your account belongs to the correct project role.

Prepare a refined backlog

A refined backlog gives planning a practical starting point. Each candidate issue should have a clear outcome, reasonable size, and enough context for estimation.

Consider this example:

Weak candidate: “Fix reporting problems.”
Stronger candidate: “Keep weekly revenue totals consistent when an order is refunded.”

The second issue gives the team a more specific result to discuss and test.

Backlog product screenshot

Estimate capacity realistically

Capacity includes more than scheduled development time. Meetings, support requests, leave, reviews, testing, and release work all reduce available hours.

If four engineers each have 60 productive hours during a sprint, the team does not necessarily have 240 hours for planned tickets. A practical buffer may be necessary for interruptions and unexpected defects.

How to Plan Sprint Scope Without Overloading the Team

The safest approach is to plan around a meaningful goal and the team’s demonstrated capacity. A sprint becomes less useful when every available issue is pushed into it.

Here’s why: overloaded sprints make progress difficult to interpret. A team may finish six issues but leave four large items partially complete, creating more uncertainty than the issue count suggests.

Use historical delivery as a guide

Review several completed sprints and compare planned work with finished work. Look for a general range rather than treating one unusually strong sprint as a permanent capacity level.

For example, if a team usually completes between 28 and 34 story points, planning 32 points may be reasonable. Planning 48 points because one sprint reached that number creates unnecessary risk.

Velocity is a planning signal, not a performance score. It should help the team make better commitments rather than encourage artificial point inflation.

Separate essential work from optional work

Put the most important work near the top of the sprint plan. Keep lower-priority items available only if the team finishes early and the work does not distract from the goal.

This approach gives the team flexibility without pretending that every selected issue has equal importance.

Account for dependencies

Dependencies can delay a sprint even when every issue is well estimated. A frontend task may depend on an API change, which may depend on an infrastructure update.

Map those relationships during planning. If the dependency is outside your team, confirm its timing before making the dependent issue a central sprint commitment.

Protect the sprint goal

New work will appear. A production defect may need immediate attention, or a stakeholder may request a time-sensitive change.

When that happens, discuss the effect openly. Add the work only when its priority justifies changing the plan, and remove or defer another item when capacity is limited.

How to Change or Manage an Active Sprint

Jira lets you adjust sprint work after the sprint begins, but every change affects reporting and team focus. Make changes deliberately and record the reason during your team conversation.

Adding an issue after the sprint starts

You can move an issue into an active sprint when new work is genuinely necessary. For example, a critical production defect may deserve immediate attention.

However, frequent additions make the original commitment harder to evaluate. If new scope becomes regular, discuss whether the team needs a different intake process or a separate urgent-work policy.

Moving incomplete work forward

When the sprint ends, Jira may prompt you to move unfinished issues to the backlog or another sprint. Review each item instead of moving everything automatically.

Ask three questions:

Is the issue still important?
Is the issue small enough for the next sprint?
Did a dependency or unclear requirement cause the delay?

An issue that remains blocked may need clarification or a dependency task before it returns to active planning.

Editing sprint dates

Changing dates during an active sprint can affect burndown charts and comparisons. Use date changes only when the team’s working period genuinely changed.

For instance, a company-wide closure may justify adjusting the end date. Extending a sprint simply to make unfinished work appear complete creates misleading history.

Closing the sprint

At the end of the timebox, review completed and incomplete work. Jira will preserve sprint history, which helps your team inspect delivery patterns over time.

Use the review to discuss outcomes. A finished ticket count matters less than whether the sprint goal created a useful result.

Common Jira Sprint Mistakes to Avoid

Most sprint problems come from planning habits rather than the creation screen itself. A few small improvements can make your board easier to manage.

Creating a sprint without a goal

A sprint name tells you when the work happened. A sprint goal tells you why the work mattered.

Without a goal, the team may optimize for closing individual issues while losing sight of the larger outcome. Add one sentence that describes the customer, product, or operational result.

Adding unrefined issues

Unclear issues create delays during execution. Developers ask questions, testers discover missing conditions, and priorities change midway through the timebox.

Keep large or vague issues in the backlog until they are ready. If the work needs discovery, plan a discovery task with a clear result rather than hiding uncertainty inside a feature ticket.

Using issue count as the capacity measure

Ten one-hour fixes do not represent the same workload as ten multi-day features. Count alone can make an overloaded sprint look reasonable.

Use estimates, historical delivery, complexity, and available working time together.

Running several unrelated goals

A sprint containing security work, a major redesign, reporting changes, and unrelated cleanup may keep everyone busy while producing no coherent outcome.

Group work around a primary objective whenever possible. If several initiatives must run together, identify the highest-priority result and protect it.

Ignoring the retrospective

Jira preserves activity, but your team still needs a conversation about what happened. Review blocked issues, scope changes, waiting time, and quality problems.

Choose one or two improvements for the next sprint. Small experiments are easier to test than a long list of process promises.

Natural Jira Sprint Planning Solution: ONES.com

ONES.com product screenshot

Value Proposition

ONES.com combines project management and knowledge management in one platform, with ONES Project serving as a Jira alternative for teams that want structured sprint planning and built-in collaboration. ONES Project and ONES Wiki are sold separately, so you can choose the capability that fits your workflow.

It supports cloud, on-premise, private cloud, and air-gapped deployments. The free plan supports up to 30 seats, while the self-hosted version maintains feature parity with the cloud version.

Core Capabilities

Scattered sprint planning: ONES Project brings backlog planning, sprint management, and issue tracking into one workspace. Result: your team can plan and monitor work without relying on several connected plugins.
Inconsistent Jira-style workflows: Jira-compatible workflows help teams preserve familiar delivery patterns. Result: switching platforms requires less process disruption.
Limited reporting visibility: Built-in reporting helps you inspect progress, delivery trends, and sprint outcomes. Result: you can discuss evidence during reviews instead of relying on memory.
Rigid issue customization: Custom workflows and fields let you reflect approvals, risk levels, ownership, or release stages. Result: the board can match your operating process more closely.
Manual repetitive updates: Automation can handle routine transitions and notifications. Result: the team spends less time repeating administrative actions.
Difficulty managing iterative delivery: Sprint management supports timeboxed planning, active execution, and review cycles. Result: Scrum teams can keep their work organized across multiple iterations.
Separate project and knowledge spaces: ONES Wiki provides a knowledge base that can sit alongside project work. Result: planning guidance, release notes, and team practices remain easier to find.
Deployment restrictions: Cloud, on-premise, private cloud, and air-gapped options support different security requirements. Result: teams in restricted networks can evaluate a deployment model suited to their environment.

Application Scenarios

Software team replacing Jira: A product team can recreate familiar workflows, define custom fields for risk and release status, and use built-in reporting during sprint reviews. This helps reduce dependence on third-party extensions.

Regulated organization with restricted infrastructure: An organization that cannot place project information in a public cloud can consider an on-premise, private cloud, or air-gapped deployment. The team can keep sprint planning within its required environment.

Growing team connecting delivery and knowledge: A team can manage sprint work in ONES Project while maintaining engineering guidance and release practices in ONES Wiki. Keeping those functions within the ONES.com platform can reduce context switching.

Common Challenges When Creating a Sprint

The “Create sprint” button is missing

Problem: You open the backlog but cannot find the sprint control.

Solution: Confirm that you are using a Scrum board and have sprint management permission. Ask an administrator to review the board filter, project role, and permission scheme.

The sprint contains too much work

Problem: The team selects every high-priority issue and enters the timebox already overloaded.

Solution: Estimate team capacity first. Choose work that supports the goal, then keep optional items outside the commitment.

Issues remain unfinished every sprint

Problem: Incomplete work repeatedly rolls into the next sprint.

Solution: Check whether issues are too large, dependencies are unresolved, or unplanned work is consuming capacity. Split oversized issues and reserve space for predictable interruptions.

The sprint goal does not match the work

Problem: The goal says “prepare the release,” but most selected issues concern unrelated maintenance.

Solution: Rewrite the goal or change the scope. The goal, selected work, and expected result should tell the same story.

Reports become difficult to interpret

Problem: Dates change often, issues enter late, and the team cannot explain burndown patterns.

Solution: Keep the timebox stable, record scope changes, and discuss reporting effects during the retrospective. Consistent practices make trends more useful.

FAQs About Jira Sprint Creation

Can I create a sprint without being a Jira administrator?

Usually, yes. You typically need the project permission that allows sprint management, but you do not necessarily need full Jira administrator access. If the creation control is missing, ask a project or Jira administrator to review your role and the board’s permission scheme.

Can I create several future sprints in Jira?

Yes. Scrum teams often create future sprints during release planning, especially when they use a regular cadence. Keep future sprint scope flexible, because priorities and capacity may change. Add only sufficiently refined work, and avoid treating every future selection as a firm commitment.

What should I do if I start a sprint by mistake?

Review the sprint immediately and correct the dates, goal, or selected issues if Jira permits the change. Tell the team what happened so reporting remains understandable. If the sprint has already collected significant activity, avoid repeatedly rewriting its history. Instead, record the correction and continue with a clear operating plan.

How many issues should a sprint contain?

There is no universal issue count. Ten small fixes may require less effort than two complex features. Use team capacity, estimates, dependencies, and historical delivery to decide. A better question is whether the selected work supports one goal and fits comfortably within the available time.

Should I add unfinished issues to the next sprint?

Review each unfinished issue before moving it. Confirm that it remains valuable, understand why it missed completion, and check whether it is ready for another timebox. Some issues need splitting, clarification, dependency work, or removal from the plan rather than automatic rollover.

Can a Kanban team use Jira sprints?

Jira sprints are primarily associated with Scrum boards. A Kanban team can use time-based planning practices, but its board and reports may not expose the same sprint controls. If your team wants formal sprints, configure or create a Scrum board that uses the appropriate project work.

Conclusion

To create a sprint in Jira, open the Scrum backlog, select Create sprint, add ready issues, define the goal, set realistic dates, and start the sprint after the team agrees on the plan.

But here’s the truth: the button is the easy part. A useful sprint depends on refined work, realistic capacity, visible dependencies, and a goal that connects individual tickets to a meaningful result.

When sprint planning becomes difficult because your team needs different workflows, deployment options, or fewer connected extensions, evaluate a Jira alternative such as ONES Project within ONES.com. The right platform should make disciplined planning easier without obscuring the work your team needs to complete.