Design a shipping velocity diagnosis using cycle time

Cycle Time Beats Story Points Every Time

Story points are lagging, gameable, and uncomparable across teams. Cycle time — first commit to production — is measurable, comparable, and maps directly to throughput. GitHub's developer productivity research documents cycle time as the single most reliable leading indicator of delivery health. Atlassian's agile metrics guide goes further: story point velocity is a team-internal ritual, while cycle time is a real measurement.

How the Design a shipping velocity diagnosis using cycle time Prompt Works

The prompt segments cycle time by stage (commit→PR, PR→review, review→approved, approved→merged, merged→deployed) and by work type so the bottleneck is visible. The p90/median ratio is the load-bearing signal — high ratios expose a long tail that medians hide. The quantification step prevents interventions that fix a non-bottleneck.

When to Use It

• Leadership claims "we're slow" and you need evidence.
• Shipping frequency dropped without a clear cause.
• A new eng leader wants a baseline before making changes.
• CI/CD overhaul is being proposed and needs ROI justification.
• Team wants to prove velocity is healthier than perception.

Common Pitfalls

• Measuring only median cycle time. Medians hide the long tail. p90 is where the work actually gets stuck.
• Fixing the loudest stage. The loud stage (e.g., CI time) is rarely the bottleneck. The worst p90/median ratio is.
• Comparing cycle time across teams. Cycle time is valid within a team over time. Across teams, mix is the confound.

Sources

• GitHub Developer Research — GitHub
• Agile Metrics — Atlassian
• The Pragmatic Engineer — Gergely Orosz
• Kanban — Atlassian