
How to Use Jira for Sprint Planning in 2026: Backlog, Capacity, Velocity and Sprint Goals
To plan a sprint in Jira, open your Scrum space’s Backlog, select Create sprint, drag ranked and estimated work items into it, set a sprint goal and dates, then select Start sprint. Use your average completed velocity from the last few sprints to decide how much to pull in. The hard part is not the button. It is having a backlog that is ready before the meeting starts.
Jira now calls projects spaces and issues work items. The screens are the same; only the names changed. This guide follows Atlassian’s docs on the Scrum backlog, estimating work, the velocity chart, the sprint report and completing a sprint, checked on October 16, 2026.
The rules Jira applies to sprints
| Rule | What it means for planning |
|---|---|
| Who can start a sprint | Space admin for every space in the board’s filter (or Manage Sprints) |
| One active sprint at a time | Unless you turn on parallel sprints |
| Velocity = average completed estimate | Over recent sprints; subtask estimates are not counted |
| Commitment is frozen at start | Items added later don’t change the gray “commitment” bar |
| “Done” = right-most board column | Wrong column mapping breaks every report |
| Closing a sprint | All subtasks must be Done first |

Step 1: Make the backlog sprint-ready first
Sprint planning length tracks backlog quality. A clean backlog gives you a 30 to 60 minute meeting. A messy one gives you three hours of arguing about scope.
A work item is ready when it has:
- A clear title and description a new teammate could follow.
- Acceptance criteria in the description, not in comments. The “Given, When, Then” format works well. For example: Given a signed-in user, when they click Export, then a CSV downloads.
- An estimate in Story points or Original estimate, set on the Backlog.
- A size that fits well inside one sprint. If not, use Split work item on the Backlog.
Run a short refinement session mid-sprint to get the next sprint’s top items ready. Do not leave it to the planning meeting.
Step 2: Agree what a story point means
Jira lets you estimate in story points, time, work item count or any number field. Atlassian’s own Jira team uses story points. Most teams should too.
The common mistake is treating 1 point as 1 hour. Then points inflate, and velocity stops meaning anything. Treat points as relative size: a 2 is about twice the effort and risk of a 1. Pick one small, well-known item as your “1” and compare everything to it.
Estimate the parent items, not subtasks. The velocity chart and the sprint report ignore subtask estimates.
Step 3: Read velocity the right way
Open Reports, then Velocity Chart (Scrum spaces only).
- The gray bar is the commitment: the total estimate when the sprint started.
- The green bar is what was completed by sprint end.
- The black line is the average.
Velocity is the average of completed estimates over recent sprints. Atlassian’s example: (17.5 + 13.5 + 38.5 + 18 + 33 + 28) / 6 = 24.75 points. That team should plan about 25 points next sprint.
Two cautions. First, the chart is board-specific and depends on column mapping. An item counts as done only in the right-most column. Second, one odd sprint skews a short history. Look at the last three to six sprints and drop clear outliers, like a holiday sprint.

Step 4: Adjust for real capacity
Velocity assumes a normal sprint. Adjust when people are out. A simple method: if one of five people is away for half the sprint, plan about 10% less.
On Jira Premium and Enterprise, Plans (advanced planning) can track capacity per team and sprint. Defaults are 30 story points or 200 hours per iteration. Change them when the team shrinks. To count against capacity, a work item needs a Team, a Sprint and an estimate. Plans spreads estimates across the team’s members, so still check each person’s load with the avatars on the Backlog.
| Jira plan | Price (per user/month, 300-user monthly quote) | Sprint planning tools |
|---|---|---|
| Free | $0 (up to 10 users) | Backlog, sprints, velocity, sprint report |
| Standard | $8.48 | Same, plus user roles and permissions |
| Premium | $15.56 | Adds Plans capacity and cross-team planning |
| Enterprise | Annual quote | Premium features at larger scale |
Prices are from the Jira pricing page on October 16, 2026. They change with team size. See our Jira pricing guide for more.
Step 5: Run the planning meeting
- Open Backlog and select Create sprint.
- Write the sprint goal first. One sentence on the outcome, like “Customers can export invoices to CSV.” A goal lets the team trade scope mid-sprint without losing the point.
- Drag the top ranked items into the sprint until you reach your planned points. You can drag the horizontal divider to move several at once.
- Check the assignee avatars at the top of the sprint. Select them to see the workload per person.
- Select Start sprint, set the duration (one, two or four weeks are common), and confirm.
While a sprint is active, you can plan the next one but cannot start it. If you truly run two at once, turn on parallel sprints.
Step 6: Keep the board honest during the sprint
Board design causes more sprint pain than people do. Keep the workflow to about four to six statuses: To Do, In Progress, In Review, Done. Show “blocked” or “waiting on client” with a flag or a label, not a new status. A status should show who owns the work now. A blocker is a condition, not an owner.
Watch the sprint report mid-sprint. Items added after the start show an asterisk. Lots of asterisks mean the commitment was never real. A JQL filter like sprint in openSprints() AND flagged is not EMPTY lists every blocked item in one place.
Step 7: Close the sprint cleanly
- Open Active sprints and select Complete sprint.
- All subtasks must be Done first. Open parents move on.
- Choose where unfinished items go: the backlog, a future sprint, or a new sprint.
You need Jira admin rights or the Manage Sprints permission. If a sprint is shared across boards, only the closing board’s items carry forward. Items from other boards go to the backlog.
Then run the retro with the sprint report open. Ask three things: Did we meet the goal? What got added? Was anything carried over twice? Carry-over twice usually means the item was too big.
Scrum or Kanban?
Use a Scrum space when the team ships in planned batches and stakeholders want dates. Use Kanban when work arrives all the time, like support or ops, and a sprint commitment would be fiction. Do not force sprints on a team that gets interrupted daily. Track cycle time on a Kanban board instead. For longer-range plans, pair either with a Jira timeline or roadmap.
Common questions
Who can start a sprint in Jira?
You must be a space admin for every space that matches the board’s filter, or have the Manage Sprints permission.
How does Jira calculate velocity?
It averages the completed estimates of recent sprints. Atlassian’s example averages six sprints to get 24.75 points.
Why don’t my subtask estimates show in the velocity chart?
The velocity chart and sprint report only count estimates on parent work items, not subtasks.
Can I run two sprints at the same time?
Yes, if you enable parallel sprints. Otherwise you can plan future sprints but start only one at a time.
What happens to unfinished work when I close a sprint?
You choose: move it to the backlog, a future sprint, or a new sprint. Subtasks must be Done before you can close.
Checked against support.atlassian.com (Jira Cloud sprint, estimation, velocity and sprint report docs) and atlassian.com/software/jira/pricing on October 16, 2026. Includes still-accurate advice folded in from our retired guide “How to Use Jira for Agile Teams.”



