Sprint Planning Template for Jira
A sprint planning template optimized for Jira Scrum boards. Covers board configuration, JQL filters, capacity planning against velocity data, dependency tracking with issue links, burndown analysis, and retrospective structure.
Sprint planning with Jira Scrum boards
Jira is the most widely used tool for agile sprint management. Its Scrum board provides a visual workflow, built-in velocity tracking, burndown charts, and sprint reports. But Jira alone does not replace a structured sprint planning process. The board shows you where tickets are. The planning template tells you why those tickets were selected and how the team will deliver them.
This template covers the Jira-specific configuration and workflow you need for effective sprint planning: board setup, sprint goal definition, backlog grooming, capacity planning using velocity data, dependency tracking with issue links, and sprint reporting. Each section includes JQL examples and Jira feature references so you can implement it immediately.
The complete Jira sprint planning template
Seven sections covering Jira board configuration, JQL filters, sprint reports, and retrospective workflows.
Jira Board Configuration
Set up a Scrum board in Jira with columns that match your team's workflow. The default columns (To Do, In Progress, Done) work for small teams, but most teams benefit from adding "In Review" and "Blocked" columns. Map each column to a Jira status so tickets flow through the board correctly.
Example board columns: Backlog → To Do → In Progress → In Review → QA → Done. Status mapping: "To Do" maps to the "Selected for Development" status. "In Progress" maps to "In Progress." "In Review" maps to "Code Review." "QA" maps to "Testing." "Done" maps to "Done." Add a WIP limit of 2-3 items per developer on "In Progress" to prevent context switching.
Jira Tips
- Enable the "Estimation" field (Story Points) in board settings under Estimation
- Add swimlanes by assignee or priority to visually group related work
- Set WIP (Work in Progress) limits on columns to prevent bottlenecks
- Use Quick Filters for common views: "My Items," "Blocked," "No Assignee"
Sprint Goal in Jira
When you create a sprint in Jira, use the Sprint Goal field to define the outcome the team is working toward. The sprint goal appears on the board header and in sprint reports, making it visible throughout the sprint. Write it as a single sentence describing user or business value.
Example sprint goal: "Users can search workspace content by full text and receive relevant results within 2 seconds." This goal is visible on the Scrum board, in the Sprint Report, and in the Backlog view. It helps the team make trade-off decisions when time runs out.
Jira Tips
- Write the sprint goal before selecting backlog items — the goal drives item selection
- Reference the sprint goal in daily standups to keep the team focused
- Update the goal only if a significant change occurs (new information, blocked dependency)
- Link the sprint goal to an Epic or Initiative using Jira Advanced Roadmaps
Backlog Grooming and Sprint Selection
Before sprint planning, ensure backlog items are refined: each has a clear description, acceptance criteria, and story point estimate. During planning, drag items from the backlog into the sprint in priority order until you reach the team's capacity. Use the Sprint Planning view in Jira to see the sprint's total points and compare against velocity.
Example JQL for sprint items: project = PLAT AND sprint = "Sprint 14" ORDER BY priority ASC, created ASC. Backlog refinement checklist: (1) Description is clear and specific. (2) Acceptance criteria written in Given-When-Then. (3) Story points estimated by the team. (4) Dependencies identified and linked. (5) Designs attached or linked.
Jira Tips
- Use Jira's drag-and-drop in the Backlog view to move items into the sprint
- The sprint header shows total planned points — compare this to your velocity average
- Use labels or components to group related items (e.g., "search-api," "search-ui")
- Create a "Refinement" status for items that need more detail before they are sprint-ready
Capacity Planning with Jira
Jira does not have a native capacity planning feature, so teams typically track capacity in a companion document or use Jira Advanced Roadmaps (formerly Portfolio). For Scrum boards, compare your planned story points against the team's average velocity. If planned points exceed the 3-sprint velocity average, remove lower-priority items.
Example: Velocity Report (Jira built-in): Sprint 11: 22 points. Sprint 12: 18 points. Sprint 13: 24 points. Average: 21.3 points. This sprint planned: 23 points. Team: 5 engineers. Adjustments: James on PTO for 2 days (reduce 3 points). Adjusted plan: 20 points — within velocity range.
Jira Tips
- Use Jira's built-in Velocity Chart (Board > Reports > Velocity Chart) to see historical data
- Plan at or below your 3-sprint average velocity for realistic commitments
- Account for PTO and on-call in a separate capacity document, then adjust planned points
- If using Jira Advanced Roadmaps, configure team capacity in the Plan settings
Dependency Tracking with Issue Links
Use Jira Issue Links to map dependencies between tickets. Link types include "is blocked by," "depends on," and "relates to." When viewing a ticket, linked issues show their current status, making it easy to spot blocked work. For cross-team dependencies, use labels or a custom field to flag external dependencies.
Example: PLAT-342 (Search API) "is blocked by" PLAT-338 (Elasticsearch cluster setup). PLAT-343 (Search UI) "depends on" PLAT-342 (Search API). PLAT-344 (Analytics tracking) "relates to" PLAT-342. Filter for blocked items: project = PLAT AND sprint = "Sprint 14" AND status = "Blocked" OR issueFunction in linkedIssuesOf("status != Done", "is blocked by")
Jira Tips
- Use "is blocked by" for hard dependencies that prevent work from starting
- Use "relates to" for informational connections that do not block progress
- Create a Quick Filter on your board: "Blocked items" using a JQL filter
- Review linked issues during standup to catch dependency delays early
Sprint Reports and Burndown
Jira provides built-in sprint reports: the Burndown Chart, Sprint Report, and Velocity Chart. The Burndown Chart shows remaining work over time. The Sprint Report shows committed versus completed items. Use these during the sprint review to assess performance and during retrospectives to identify patterns.
Example: Sprint Report shows: Committed: 8 issues (23 points). Completed: 7 issues (20 points). Not Completed: 1 issue (3 points — PLAT-345 carried over due to design change). Added mid-sprint: 1 issue (2 points — urgent bug fix). Burndown Chart: On track for first 5 days, slight plateau on Day 6 (code review bottleneck), recovered by Day 8.
Jira Tips
- Check the Burndown Chart daily to spot trends early — a flat line means work is stuck
- In the Sprint Report, review "Items added" and "Items removed" to track scope changes
- Use the Velocity Chart across sprints to identify whether the team is stabilizing or declining
- Export sprint reports for stakeholder updates and quarterly planning reviews
Retrospective in Jira
Jira does not have a native retrospective feature, but many teams use Confluence pages linked from the sprint or third-party apps like EasyRetro. Structure the retrospective around three questions: What went well? What should we improve? What actions will we take? Record action items as Jira tickets assigned to specific owners.
Example: What went well: Dependency on Elasticsearch resolved on Day 2 as planned. Team completed 87% of committed points. What to improve: Search UI took 5 points instead of estimated 3 — need design review before estimation. Actions: (1) PLAT-400: Add design review step to refinement process (owner: PM, Sprint 15). (2) PLAT-401: Create search performance benchmark test suite (owner: Sarah, Sprint 15).
Jira Tips
- Create retrospective action items as Jira tickets so they get tracked and completed
- Link action item tickets to the next sprint so they appear in the upcoming sprint backlog
- Use Confluence for the full retrospective discussion, linked from the Jira sprint
- Review previous retrospective action items at the start of the next retrospective
How Vantage enhances Jira sprint planning
Jira tracks your tickets. Vantage connects your sprint to the product context that informs it.
Two-way Jira sync
Vantage syncs with Jira bidirectionally. Ticket status, priority, and assignment changes flow both ways. No manual copying between tools.
AI-powered sprint selection
Describe the sprint goal and Vantage recommends backlog items based on priority, dependencies, and team capacity — grounded in your actual Jira data.
Cross-project dependency detection
Vantage maps dependencies across Jira projects and teams. When sprint items conflict with another team's planned work, you see it before the sprint starts.
Sprint plan generation
Vantage generates a complete sprint plan document with capacity analysis, risk assessment, and item justification — all traceable to your Jira backlog and analytics data.
Related templates
Sprint Planning Template for Confluence
Sprint planning formatted for Confluence with Jira integration macros.
View template →Sprint Planning Template for Linear
Sprint planning optimized for Linear cycles with project views.
View template →User Story Template for Jira
Write well-formed user stories with acceptance criteria for Jira tickets.
View template →Frequently asked questions
Plan better sprints with Vantage + Jira
Connect Jira and Vantage generates sprint plans with real velocity data, dependency detection, and two-way sync. Free to start.
Free to start. No credit card required.