Sprint Planning Template for Linear
A sprint planning template designed for Linear cycles. Covers cycle setup, issue prioritization, project grouping, capacity planning with velocity data, dependency tracking, and retrospective workflows.
Why teams use Linear for sprint planning
Linear is built for speed. Issue creation, status updates, and backlog management are significantly faster than in traditional project management tools. This speed advantage matters most during sprint planning, where the team needs to review, estimate, and prioritize dozens of items in a single session.
Linear\'s cycle feature provides automated velocity tracking, progress visualization, and issue carry-over between cycles. Combined with projects for strategic grouping and sub-issues for task breakdown, Linear gives teams everything they need for structured sprint planning without plugin sprawl.
The complete Linear sprint planning template
Seven sections optimized for Linear cycles, projects, and team workflows.
Cycle Setup in Linear
Linear uses "Cycles" instead of sprints. Create a cycle with a name, start date, end date, and description. The description field is where you write your sprint goal. Linear automatically tracks the number of issues and total points in each cycle, giving you a built-in velocity view.
Example: Cycle name: "Cycle 14 — Search Improvements." Duration: Aug 11 – Aug 22 (2 weeks). Description: "By end of cycle, users can search workspace content by full text and receive results within 2 seconds." Issues: 8 issues, 23 points total.
Linear Tips
- Use consistent naming conventions for cycles (e.g., "Cycle 14 — Theme Name")
- Set the cycle duration in Team Settings > Cycles for automatic cycle creation
- Write the sprint goal in the cycle description so it is visible on the cycle page
- Enable "Auto-archive completed cycles" to keep your workspace clean
Issue Prioritization with Linear Priority Levels
Linear has built-in priority levels: Urgent, High, Medium, Low, and No Priority. Use these consistently during planning. Urgent and High items must be completed this cycle. Medium items should be completed. Low items are stretch goals. Filter the cycle view by priority to focus standup discussions on blocked high-priority items.
Example cycle breakdown: Urgent (0 issues) — reserved for production incidents. High (3 issues, 11 points): Search API, Search UI, Analytics tracking. Medium (3 issues, 8 points): Search filters, Error states, Loading indicators. Low (2 issues, 4 points): Search suggestions, Search history.
Linear Tips
- Reserve "Urgent" for production incidents and unplanned work only
- Plan High items to fill about 60% of cycle capacity, Medium for 30%, Low for 10%
- Use Linear filters to create saved views like "High priority in current cycle"
- Review priority distribution during planning to avoid over-committing to high-priority items
Project Grouping
Linear Projects group related issues across multiple cycles. During sprint planning, check which projects have issues in the current cycle and ensure they align with the cycle goal. Projects provide the strategic context (why) while cycles provide the execution cadence (when).
Example: Project "Search Improvements" contains 12 issues total. 8 are assigned to Cycle 14, 4 are in the backlog for future cycles. The project page shows overall progress (67% in current cycle), target date, and project lead. Issues in the cycle are linked to their parent project for traceability.
Linear Tips
- Create one Linear Project per major initiative or epic
- Check the project progress bar during planning to see how much work remains
- Use project milestones to mark key checkpoints within the initiative
- Link the project description to the PRD or product brief for full context
Estimate and Capacity
Linear supports point estimates on issues. During planning, ensure every issue in the cycle has an estimate. Compare total planned points against the team's historical cycle velocity. Linear shows velocity on the Team Insights page — use the 3-cycle rolling average as your capacity target.
Example: Team Insights shows — Cycle 11: 20 points. Cycle 12: 18 points. Cycle 13: 22 points. Average: 20 points. Current cycle planned: 23 points. Team: 5 engineers. Adjustment: James on PTO for 2 days. Recommended capacity: 20 points. Decision: Move 2 Low items (3 points) to backlog. Adjusted plan: 20 points.
Linear Tips
- Use Linear's Team Insights page for velocity data across cycles
- Ensure every issue has a point estimate before the cycle starts
- Plan at or below your 3-cycle average velocity
- Use Linear's "Estimate" feature (Fibonacci or linear scale) consistently across the team
Sub-issues and Dependencies
Linear supports sub-issues for breaking down large items. Use sub-issues when a single issue has multiple distinct deliverables. For dependencies, use Linear's relation feature ("blocked by" and "blocking") to map which issues depend on each other. Blocked issues appear with a visual indicator on the board.
Example: Issue "Search API" has 3 sub-issues: "Implement search endpoint," "Add full-text indexing," "Write API tests." Dependency: "Search UI" is "blocked by" "Search API." When Search API moves to Done, the blocking indicator on Search UI clears automatically.
Linear Tips
- Use sub-issues for task breakdown, not for separate features
- Set "blocked by" relations during planning so the team knows the execution order
- Use Linear's board view to visually identify issues with blocking indicators
- Review blocked issues during standup — if the blocker is not progressing, escalate
Cycle Progress and Daily Tracking
Linear's cycle view shows a progress bar, completed vs. remaining issues, and a burndown-style chart. Use this during daily standups to assess whether the team is on track. Filter by assignee to check individual workloads. Filter by status to identify items stuck in review or testing.
Example daily check: Day 5 of 10. Cycle progress: 45% complete (10 of 23 points). On track: Yes (expected 50% by Day 5). Blocked items: 1 (Search filters — waiting on design). Action: Follow up with designer by EOD. At-risk items: 0.
Linear Tips
- Check the cycle progress chart at the start of each standup
- Use Linear's "Active" filter to focus on issues currently being worked on
- Flag issues that have been "In Progress" for more than 2 days without movement
- Use Linear's SLA feature to set time-in-status alerts for bottleneck detection
Cycle Review and Retrospective
At the end of the cycle, review completed vs. planned work using Linear's cycle report. Carry incomplete issues to the next cycle or move them back to the backlog. For the retrospective, create a Linear document or use a separate tool. Record what went well, what to improve, and action items. Create action item issues and assign them to the next cycle.
Example: Cycle 14 completed: 20 of 23 points (87%). Carried over: Search suggestions (2 points), Search history (1 point). Retro notes: What went well — API delivered on Day 3 as planned, unblocking UI work. What to improve — UI estimation was off (5 points actual vs. 3 estimated). Action: Create a design review step issue for next cycle.
Linear Tips
- Use Linear's cycle close dialog to move incomplete issues to the next cycle or backlog
- Record retrospective action items as Linear issues assigned to specific team members
- Review the cycle velocity trend over time using Team Insights
- Link retrospective documents to the cycle for future reference
How Vantage enhances Linear sprint planning
Linear handles issue tracking. Vantage adds the product intelligence layer.
Native Linear sync
Vantage connects to Linear with two-way sync. Issues, statuses, and priorities stay in sync. Changes in either tool reflect in the other.
AI sprint plan generation
Describe your cycle goal and Vantage recommends issues from your backlog based on priority, dependencies, and team capacity.
Cross-team visibility
When cycle items depend on work in other Linear teams or projects, Vantage surfaces the conflict so you can resolve it during planning.
Velocity-based recommendations
Vantage tracks your cycle velocity over time and recommends a realistic point target based on your rolling average and team availability.
Related templates
Sprint Planning Template for Jira
Sprint planning optimized for Jira Scrum boards with JQL and burndown charts.
View template →Sprint Planning Template
A tool-agnostic sprint planning template with goals, capacity, velocity, and retrospective sections.
View template →User Story Template
Write clear user stories with acceptance criteria using the standard format.
View template →Frequently asked questions
Plan better cycles with Vantage + Linear
Connect Linear 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.