Sprint planning is the meeting that decides whether your next two weeks go smoothly or fall apart. Linear gives you solid tools for it. Most teams use about 30% of what's available.
Here's how to do it properly.
Set up your cycles first
In Linear, sprints are called Cycles. Before your planning meeting, make sure cycles are configured in your workspace settings. Go to Settings > Cycles and define your sprint length (usually 1 or 2 weeks).
A few things to configure:
- Cooldown period: gives the team a buffer at the end of each cycle before the next one starts
- Auto-close: automatically closes incomplete issues or rolls them over
- Start day: align it with your team's actual rhythm (Monday is common)
If you haven't set these up yet, do it before your next sprint starts.
Backlog grooming before the meeting
The planning meeting fails when the backlog is a mess. Before you sit down together, spend 20 minutes doing a grooming pass:
Go to your Issues view, filter by "No Cycle" and "Backlog" status. Look at each item and ask:
- Is this still relevant?
- Does it have a clear description?
- Is it assigned to someone?
- Does it have an estimate (if your team uses points)?
Issues without estimates or clear owners slow down planning. Clean these up before the meeting.
The planning meeting itself
Once your backlog is groomed, the meeting has a simple structure:
Step 1: Review last cycle. Open the previous cycle and walk through what shipped, what got carried over, and why. This takes 10 minutes max.
Step 2: Set a goal. Before pulling issues in, write down one sentence describing what success looks like for this sprint. Linear lets you add a cycle description. Use it.
Step 3: Pull issues into the cycle. Drag issues from the backlog into the current cycle. If you use points, watch your total. A common mistake is pulling in 40 points when your team historically ships 25.
Step 4: Assign ownership. Every issue in the cycle should have an owner before the meeting ends. "Team" is not an owner.
The problem with planning blind
Here's what most teams skip: planning based on actual data.
When you drag issues into a cycle, you're making a prediction. You're saying "we'll ship this much work in 2 weeks." But if you don't know what your team actually shipped in the last 8 cycles, you're guessing.
Linear shows you one cycle at a time. It doesn't show you:
- Your average velocity across the last 10 sprints
- Who on your team is consistently over- or under-committed
- Whether your estimates are accurate over time
- Whether velocity is trending up or down
Without this data, every planning session is a guess dressed up as a plan.
Using data to plan better
Good sprint planning uses historical patterns to make realistic commitments.
If your team shipped 22 points last sprint, 19 the sprint before, and 24 the one before that, your realistic target is around 21 to 23. Not 35.
If one engineer is consistently completing 120% of their estimated work, they might be under-estimating. If another is consistently at 60%, they might be blocked or over-committed elsewhere.
This kind of pattern only shows up when you look at multiple cycles side by side. Linear doesn't surface this natively.
SprintIQ: the analytics layer for Linear planning
SprintIQ connects to your Linear workspace and automatically builds the velocity history your planning sessions are missing.
Before your next sprint planning meeting, you can open SprintIQ and see:
- Velocity per person across the last 8 to 12 weeks
- How accurate your estimates have been historically
- A sprint forecast showing whether your planned scope is realistic
- Any tickets currently stuck that should be resolved before they go into the next cycle
It takes 30 seconds to connect via Linear OAuth (read-only, we never touch your data). No setup, no CSV exports, no spreadsheets.
Free to start.