Public sector
State government — 0 to 100+ developers, weekly production deploys.
Three KPIs at a glance, then the structured story below.
Headline
State government — 0 to 100+ developers, weekly production deploys.
A state government digital transformation was attempting to scale a small in-house engineering team into a multi-team capability that could ship public-facing services at the rate the policy environment required. Most of the existing playbook came from waterfall procurement and quarterly releases. COVID-19 arrived mid-engagement and required digital responses to be delivered in days, not quarters.
- Developers across multiple teams
- 0 → 100+
- Production deployments
- Weekly
- COVID-19 digital response delivered
- Pace
Challenge
A state government digital transformation was attempting to scale a small in-house engineering team into a multi-team capability that could ship public-facing services at the rate the policy environment required. Most of the existing playbook came from waterfall procurement and quarterly releases. COVID-19 arrived mid-engagement and required digital responses to be delivered in days, not quarters.
Approach
Built the engineering practice from the ground up. XP discipline, CI/CD, pair programming, and code-as-craft as default. Hired and onboarded engineers into outcome-aligned squads rather than functional silos. Established the deploy pipeline that made weekly production releases the norm rather than the exception.
Outcome
Engineering scaled from a handful to over 100 developers across multiple teams. Weekly production deployments became the rhythm. The COVID-19 digital response — citizen-facing services that previously would have taken months — shipped in days. The capability stayed with the public service after the engagement ended.