2× sprint throughput
Engineering velocity turnaround: 2× sprint throughput
Fractional CTO / Coach•SaaS / Enterprise (150-person eng org)•Sep 2022 — Mar 2023•Published 5 November 2022
Restructured rituals, review standards, and Definition of Done for a mid-market SaaS team — doubling velocity while cutting rework.
Technology Stack
ADR templatesJiraGitHubConfluence
Key Outcomes
- •2× sprint throughput within one quarter
- •Rework dropped ~35% via design clinics and blameless postmortems
- •Engineering handbook and review checklists adopted org-wide
Outcome: 2× sprint throughput with ~35% less rework.
Context
A 150-person engineering org had grown fast through acquisition. Rituals were inconsistent; VP Engineering needed an external coach to reset standards without a reorg.
Problem
- Stories closed but not truly “done” — prod bugs spiked.
- Design decisions lived in Slack threads.
- Review fatigue; nitpicks without architectural feedback.
Approach
- Definition of Ready/Done — workshop + enforcement in Jira.
- Design clinics — 45-min slots before build starts.
- ADR discipline — one-page decisions for anything cross-team.
- Blameless postmortems — template and executive sponsorship.
Deliverables
Engineering handbook, review checklists, and quarterly velocity dashboard.
Results
Throughput doubled in one quarter; rework estimates from team leads fell ~35%.
CTA
Need a fractional CTO who coaches teams, not just code? Book a 30-min call.