Engineering metrics have a bad reputation. Used wrong, they become surveillance tools that demoralize teams. Used right, they give you early warnings before problems become crises.
The key is picking the right metrics. Here are the 5 that matter most for teams using Linear, and how to actually track them.
1. Velocity (per person, per cycle)
Velocity is the amount of work your team ships per sprint. It's the foundational metric because everything else is measured against it.
To track it properly, you need:
- A consistent way of estimating work (story points or t-shirt sizes)
- Data across multiple cycles, not just the current one
- A breakdown by team member, not just aggregate
Linear gives you cycle-level data. It doesn't give you an easy view of velocity trends across 10 cycles with a per-person breakdown. You'll need to export and build this manually, or use a tool built on top of Linear.
What to do with it: Velocity isn't about pushing people to ship more. It's about making realistic commitments. If your team ships 20 points per sprint, don't plan 35.
2. Cycle time
Cycle time measures how long it takes a ticket to go from "In Progress" to "Done." It's a measure of execution speed.
Linear tracks this natively in its Insights tab. You can see average cycle time per team member and filter by time period.
What to look for: A cycle time of 2 to 3 days for small tickets is healthy. If you're seeing 7+ days regularly, something is slowing things down: unclear requirements, large ticket sizes, too much context switching, or too many review rounds.
What to do with it: When cycle time spikes, dig into the specific tickets causing it. The pattern usually reveals the real problem.
3. Blocker rate
Blocker rate is the percentage of tickets in a given sprint that get blocked at some point. A ticket doesn't have to be marked "Blocked" in Linear. Any ticket that sits In Progress for 48+ hours without movement is effectively blocked.
Linear doesn't surface this automatically. You have to check manually or use a tool that monitors ticket activity.
What to look for: A blocker rate above 20% in a sprint usually signals a systemic issue: unclear dependencies, external blockers, or a lack of async communication.
What to do with it: High blocker rate is a retro conversation starter. Ask the team what types of blockers are recurring, and fix the root cause.
4. Carryover rate
Carryover rate is the percentage of tickets planned in a sprint that carry over to the next one. If you consistently carry over 30% of your tickets, your sprint planning is broken.
Linear shows you carried-over issues at the end of each cycle. You can see which issues rolled over and why.
What to look for: A carryover rate above 15% to 20% consistently means you're systematically over-committing. Either your velocity estimates are off, or scope creep is hitting you mid-sprint.
What to do with it: Use carryover data in planning. If you carried over 5 issues last sprint, factor that into your next sprint's scope.
5. Estimate accuracy
Estimate accuracy measures whether your 3-point tickets actually take 3 points of effort. This is the least-tracked metric on this list, and one of the most useful.
If your 5-point tickets consistently take 10 points of real effort, your velocity numbers are meaningless. You think you're shipping 25 points per sprint, but you're actually shipping 25 points of planned scope with 50 points of actual effort.
Linear doesn't track this natively. It records your estimates and your completions, but it doesn't compute the gap.
What to look for: Individual engineers who consistently under-estimate may be taking on ambiguous work. Those who consistently over-estimate may be sandbagging. Both are useful signals for coaching.
How to track these in practice
You have two options:
Option 1: Manual tracking. Export from Linear each sprint, build a spreadsheet, update it weekly. This works but takes 2 to 3 hours per sprint to maintain. Most teams start here and abandon it within a month.
Option 2: Use a dedicated analytics layer. A tool that connects to Linear and computes these metrics automatically across all your historical data.
SprintIQ: metrics built for Linear teams
SprintIQ connects to your Linear workspace in 30 seconds via OAuth (read-only access) and automatically tracks:
- Velocity per team member across all past cycles, with trend lines
- Blocker detection: tickets stuck for 48+ hours, surfaced automatically before standup
- Sprint forecast: will you hit your cycle goal based on current pace?
- Carryover tracking across cycles
No CSV exports. No spreadsheets. The data is already in Linear. SprintIQ just makes it visible.
Free to start. No credit card required.