Starting a Jira sprint should take minutes, yet small setup mistakes can create confusion for your entire team. Work may sit in the wrong sprint, dates can fail to match your release plan, and teammates might not know what the team committed to deliver.
That uncertainty becomes expensive once development begins. Reports lose accuracy, unfinished work gets carried forward without discussion, and daily stand-ups turn into status investigations.
But here's the truth: starting a sprint in Jira is simple when you prepare the backlog first. You need a clear sprint goal, a realistic group of issues, correct dates, and the right permissions. This guide walks you through the complete process, explains what happens after you click Start sprint, and shows how to handle common problems without disrupting your team.
How to Start a Sprint in Jira
To start a sprint in Jira, open your team-managed or company-managed Scrum board, go to the Backlog, move the selected issues into a sprint, set the sprint goal and dates, then select Start sprint. Jira will move the sprint into the active state and make it available for tracking on the board.
1. Confirm that you are using a Scrum board
Sprints belong to Scrum boards. If your project uses a Kanban board, you will usually manage work through continuous flow rather than fixed sprint cycles.
Open the relevant project and choose Board or Backlog from the project menu. Look for a sprint panel near the top of the backlog. If you cannot see one, check the board type and ask a Jira administrator to review your permissions.
2. Review and prepare the backlog
Before creating a sprint, review the highest-priority issues. Each issue should have enough detail for the team to understand the expected result, acceptance criteria, and dependencies.
For example, “Improve checkout” is too broad for a focused sprint. “Add address validation to the checkout form and show an error message for invalid postal codes” gives the team a clearer piece of work.
Remove outdated tasks, clarify blocked items, and confirm that estimates are available when your team uses story points or another estimation method. This preparation helps you avoid filling the sprint with work the team cannot complete.
3. Create a sprint
In the backlog view, select Create sprint. Jira will add a new sprint area, often above the backlog or below another planned sprint.
Give the sprint a useful name if your team follows a naming convention. “Sprint 24” works, while “Sprint 24 — Checkout reliability” gives people more context at a glance.
4. Add issues to the sprint
Drag selected issues from the backlog into the new sprint. You can also use Jira’s bulk actions when you need to move several issues at once.
Keep the sprint focused on work that supports one short-term outcome. If the team has a two-week capacity of 40 story points, adding 70 points creates pressure before the sprint begins.
Check each issue’s priority, assignee, estimate, and dependency status. A task that depends on an unfinished design or an external approval may need a later sprint.
5. Open the sprint setup window
Select Start sprint. Jira will open a setup window where you can enter or confirm key sprint details.
Review the sprint name, start date, end date, and goal. The exact fields can vary between Jira configurations, so your screen may look slightly different from another team’s setup.
6. Set realistic start and end dates
Choose dates that reflect your team’s actual working cycle. A two-week sprint might run from Monday morning through Friday afternoon of the following week.
Check holidays, planned absences, release deadlines, and company-wide events. A sprint that overlaps with a three-day holiday may need a smaller workload.
Dates also affect reporting. If the sprint starts late or ends early, velocity charts and completion trends may become harder to interpret.
7. Write a clear sprint goal
A sprint goal describes the outcome the team wants to achieve. It should explain the purpose of the work rather than repeat a list of issue titles.
For example, “Allow customers to update saved payment details securely” gives direction to several related tasks. “Complete tickets PAY-101, PAY-102, and PAY-103” only identifies the work items.
A strong goal helps the team make trade-offs. If a new request appears during the sprint, the team can ask whether it supports the agreed outcome.
8. Check the final issue list
Before confirming, scan the sprint for duplicate tasks, missing acceptance criteria, unrealistic estimates, and work that belongs to another team.
Look for unfinished work carried over from an earlier sprint. Discuss whether each item still matters, then adjust the plan before starting.
9. Select “Start sprint”
When the details look correct, select Start sprint. Jira will mark the sprint as active and display its issues on the Scrum board.
From this point, the team can track progress, update statuses, log work, and review remaining work through the active sprint view.
What Happens After You Start a Sprint?
Once a sprint becomes active, Jira treats it as the team’s current delivery cycle. Issues assigned to that sprint appear on the board according to their workflow status.
For example, a task in To Do may move to In Progress, then to Code Review, and finally to Done. Your workflow may use different status names, but the principle remains the same.
The board becomes the team’s daily control center
During daily stand-ups, team members can use the active board to discuss progress, blockers, and next actions. A quick glance should show whether work is moving or accumulating in one status.
If five issues remain in code review while development tasks continue growing, the board reveals a flow problem. The team can then pair reviewers with developers or reduce new work temporarily.
Reports begin tracking sprint performance
Jira can calculate sprint progress through reports such as the burndown chart, sprint report, and velocity chart. These reports become more useful when the team updates issue statuses consistently.
A burndown chart that stays flat may indicate that work has not moved, estimates are missing, or completed issues are not being marked correctly. Treat the chart as a conversation starter rather than a scorecard.
Changes require deliberate communication
Teams often discover new information after a sprint begins. A product requirement may change, or a critical production issue may appear.
You can add or remove issues, but every change affects the original commitment. Discuss the trade-off openly and record the reason in the issue or team channel.
How to Choose the Right Sprint Scope
The best sprint scope fits the team’s capacity and supports one meaningful objective. Capacity includes available working time, technical complexity, support duties, meetings, and planned leave.
Suppose a four-person team has 160 total working hours over two weeks. After support work, planning, reviews, and meetings, the team may have only 105 hours for planned delivery.
| Planning factor | Practical question |
|---|---|
| Team capacity | How much focused time is actually available? |
| Issue size | Can each item reach a useful completion state within the sprint? |
| Dependencies | Does another person, team, or approval need to act first? |
| Priority | Which work creates the greatest customer or business value? |
| Risk | Are unknown technical details likely to delay delivery? |
Use historical performance carefully
Past velocity can help you plan, but it should not become a rigid quota. A team that completed 35 points last sprint may have fewer available hours this time.
Consider recent results alongside holidays, staffing changes, support requests, and the type of work involved. Ten small maintenance issues may behave very differently from three complex integration tasks.
Split oversized issues
Large issues hide uncertainty. Break them into slices that each produce a testable result.
For a reporting feature, one slice might create the report layout, another might connect the required calculations, and a third might add export behavior. The team gains feedback earlier and sees progress more clearly.
How to Run the Sprint After Launch
Starting the sprint is only the beginning. The team must keep Jira current so the board reflects reality.
Update statuses promptly
Move an issue when its work state changes. If a task remains marked In Progress after it enters review, the board will exaggerate active development and hide the review queue.
Encourage short, useful updates. “Waiting for API credentials from the security team” tells people more than “Blocked.”
Watch for scope expansion
New work can enter a sprint quietly through comments, urgent messages, or informal requests. Capture the request in Jira and discuss its effect on the sprint goal.
If an urgent bug must enter, consider removing work of similar size or lower priority. This keeps the workload visible and protects the team from uncontrolled growth.
Use the daily stand-up to inspect progress
Ask three practical questions: What changed since the last check-in? What needs attention today? What could prevent the sprint goal?
For example, if a testing environment is unavailable, the team can escalate that issue immediately. Waiting until the final day turns a manageable blocker into a missed commitment.
Review remaining work near the midpoint
A midpoint check gives you time to adjust responsibly. Look at unfinished issues, blocked tasks, and newly discovered complexity.
If the sprint goal is at risk, discuss options early. You might reduce scope, pair team members, or schedule a focused technical investigation.
How ONES.com Can Support Sprint Planning
ONES.com provides a project management environment for teams that want planning, execution, collaboration, and reporting in one place. It can be useful when your team needs a broader delivery workspace around sprint activities.
Capabilities that support Scrum-style work
- Backlog organization: Arrange tasks, priorities, and upcoming work before a sprint begins.
- Sprint planning: Group selected work into defined delivery cycles with goals and time limits.
- Task tracking: Follow work through stages such as planned, active, under review, and completed.
- Issue detail: Keep descriptions, acceptance criteria, owners, comments, and activity history together.
- Agile reporting: Review progress, workload, completion patterns, and delivery trends.
- Team collaboration: Give teammates a shared place to discuss blockers and decisions.
- Custom workflows: Adapt statuses and transitions to match the way your team delivers work.
- Permission controls: Manage access so different roles can view or update appropriate areas.
- Cross-project visibility: Connect related work when several initiatives depend on one another.
Imagine a team coordinating product development, quality assurance, and customer feedback. A connected workspace can reduce the need to reconstruct progress across separate tools.
Jira remains a strong choice for teams already invested in its Scrum boards and reporting. ONES.com may suit teams looking for an alternative project environment with planning and collaboration capabilities in one platform.
Common Challenges
Jira does not show the “Start sprint” button
Problem: You may lack the required permission, be viewing the wrong board, or have no issues assigned to the sprint.
Solution: Confirm that you have sprint management permission, open the correct Scrum board, and check whether the sprint contains planned work. Ask a Jira administrator to review the board configuration if the control remains unavailable.
The sprint contains too much work
Problem: The team adds every urgent request and carries a heavy backlog into the same cycle.
Solution: Compare the planned workload with real capacity. Remove low-priority issues, split oversized tasks, and keep a small buffer for unexpected work.
Issues appear in the wrong sprint
Problem: An issue may have been dragged into the wrong sprint or assigned through a bulk action.
Solution: Open the issue, review its sprint field, and move it to the correct sprint. Check related subtasks as well, because they may not always follow the parent issue automatically.
The sprint goal is unclear
Problem: The goal simply lists tickets, leaving the team without a shared outcome.
Solution: Rewrite it around the customer or business result. “Reduce failed password resets for mobile customers” gives stronger direction than “Finish authentication tickets.”
Work remains unfinished at the end
Problem: The team reaches the end date with several issues still open.
Solution: Review why the work remained incomplete. Move unfinished issues to the next sprint only after checking their priority and readiness. Use the retrospective to address recurring causes such as unclear requirements or excessive work in progress.
FAQs
Can I start a sprint without adding issues?
Jira may allow you to start an empty sprint, depending on your configuration and permissions. However, an empty sprint usually provides little planning value. Add at least the work connected to your sprint goal, or use the period for a clearly stated planning or technical objective.
Can two sprints run at the same time in Jira?
Some Jira configurations allow parallel active sprints, while others limit a board to one active sprint. Parallel sprints can help teams with separate delivery streams, but they may complicate reporting and ownership. Confirm that your team has a clear reason before enabling this approach.
Can I change the sprint dates after starting it?
In many Jira setups, you can edit the sprint dates after it becomes active. Open the active sprint controls and look for the option to edit sprint details. Make date changes carefully because reports and progress comparisons may reflect the revised period.
What should I do with unfinished issues?
Review each unfinished issue with the team. Move it into the next sprint if it still matters and is ready for work. Return it to the backlog if its priority has changed, or split it when only part of the work remains. Avoid carrying every unfinished task forward automatically.
Can I add new work after the sprint starts?
Yes, Jira generally lets you add issues to an active sprint. First, discuss the impact on the sprint goal and existing commitments. If the new work is urgent, remove or postpone work with a similar effort level when possible.
What is a good sprint goal?
A good sprint goal describes one valuable outcome in plain language. For example, “Enable customers to complete checkout with saved payment details” gives the team a decision-making guide. It also connects several technical tasks to a result that stakeholders can understand.
Conclusion
Starting a sprint in Jira is a short action with a significant planning effect. You select suitable issues, confirm capacity, set dates, write a meaningful goal, and choose Start sprint.
The real value comes from what follows. Keep statuses accurate, watch scope, surface blockers early, and review unfinished work honestly. A clean sprint gives your team a clearer view of progress and makes future planning more reliable.
When sprint setup feels confusing, the problem is usually unclear preparation rather than a difficult Jira control. Prepare the backlog carefully, protect the sprint goal, and use the active board as your team’s shared operating view.
