Hemut Co. · Engineering
Linear Sprint Planning
§1Team KPIs
0%
Team Completion
0
Total Issues (90d)
0
Completed
100% Completion
None
Overdue Issues
None
§2Completion Rate by Engineersorted by rate desc · green ≥80% · yellow ≥50% · red <50%
Sumedh
0%
0/0
Ashish
0%
0/0
A2Z2
0%
—
Not in Linear system
Avetis
0%
0/0
Aaryan
0%
0/0
Federico
0%
0/0
Pranav
0%
0/0
Harshiv
0%
0/0
Kalpan
0%
0/0
Andrew
0%
0/0
Darius
0%
0/0
Gabriele
0%
0/0
Tarun
0%
0/0
Alex
0%
0/0
Len
0%
—
Not tracked in Linear
Aidan
0%
0/0
Loki
0%
0/0
§3Backlog by Engineersorted by overdue desc then backlog desc
| Engineer | Backlog | Overdue | Blocked |
|---|---|---|---|
| No backlog data available — run collect_linear.py | |||
§4Backlog by Projecttop 10 modules
| Project | Backlog Count |
|---|---|
| No project backlog data available | |
§5Ticket-to-PR Coveragewho links PRs to tickets vs flying blind · target: 80%+
§6Overdue Issuessorted by count desc · action required
✓ No overdue issues detected across all engineers.
§7Velocity Trendcompletion rate vs team avg (0%) · in-flight as leading indicator
Engineer
Completion
Rate
vs Team Avg
In Progress
Week-by-week velocity data not available in current pipeline. Showing 90-day completion rate vs team average as a proxy.
"In flight" = active In Progress issues — high numbers may indicate WIP buildup.
§8Linear Flags & Notes
No flags available — run collect_linear.py to populate