Product · Sprints
Cycles, properly.
Two-week iterations by default. Unfinished issues roll forward with a required reason. Post-cycle reports surface slippage without anyone arguing about a spreadsheet.
Required rollover reasons
When a cycle ends, any open issue gets tagged with a rollover reason: dependency, scope, sickness, re-prioritised. Reasons aggregate in the next cycle report.
Velocity trend across 6 cycles
Not the point-in-time velocity; the trend. Great retro material. Great board material. Great let's-not-overcommit-again material.
Slippage detection
If an issue's estimate grew 2x or more during the cycle, it's flagged with the diff inline. No more post-hoc mystery about where the week went.
Exportable reports
Every cycle report can be exported as PDF or shared as a read-only link. Good for status updates to leadership or board reviews.
Sample cycle report
Platform · Cycle 23 · 2026-03-24 → 2026-04-04
Planned
34pt
Shipped
31pt
Rolled over
3pt↓
Velocity trend
+4%↑
Rollover reasons
- · 2pt — waiting on design (PLAT-325)
- · 1pt — external API blocker (PLAT-347)
Slippage
PLAT-342 grew from 2pt → 5pt mid-cycle (webhook retry redesign expanded scope). Flag: re-estimate at sprint-plan.