Where do you start?
Four paths into RACE Programming, each matched to your current context. Pick the one that describes where your team is today.
From Scrum
Your team uses Scrum. Sprints, velocity, story points, a Scrum Master. You want to adopt RACE Programming without discarding what works.
Read the Scrum transition guide →Greenfield
Starting from scratch. No legacy constraints, no existing team rituals. Build the RACE Programming system right from day one.
Read the greenfield guide →Brownfield
An existing product, existing codebase. Adopting RACE Programming while maintaining live production without a hard cutover.
Read the brownfield guide →Staffing to client speed
Staff up when the client accelerates. Staff down when they slow. The accordion model maps EUS/week throughput to Pit Wall and Pit Crew allocations across Discovery mode and Realization mode.
Read the staffing guide →What all four guides share
Every guide follows the same structure: Why (what breaks without RACE Programming in your context), What (what you're adopting), Who (which roles change and how), How (step-by-step, 90 days), and How to measure success (the metrics that confirm it's working).
If you're new to RACE Programming, read the Framework overview first. If you're coming from Agile and want the conceptual bridge, read Agentic Agile.