RACE Programming on an existing product
Live production. Existing team. No hard cutover required. Two transition paths: choose by your organization's change tolerance.
Why brownfield is harder, and still worth it
Brownfield and greenfield differ by the starting point. Here a lot is already in place, including processes that do not fit the new reality; greenfield starts from nothing. This guide lays out the path from this start and the options along it.
Brownfield adoption faces two constraints greenfield doesn't: an existing team with established habits, and a live product that can't stop delivering. The temptation is to "add AI tools" without changing the delivery model, which produces the 46% AI pilot failure rate (Scrum.org): faster code generation poured into the coordination overhead it was supposed to remove. We measured the effect on one long-running client platform: a developer with agents got 8.3 times faster at coding, and the ten-person team around him delivered 1.65 times as much (The Ceiling of AI Tools).
RACE Programming's value in brownfield is structural change: replace coordination overhead with a spec-first, prototype-gated delivery model. What we see now on the project triangle: ~3× the scope, ~⅓ the cost, or 2-5× faster, worked out from two team shapes. Measured in the agent-to-agent data imports case, against our estimate for a team that already works with AI tools: about a third of the cost of production, 7.1 times less human effort for the same scope, about the same end-to-end speed.
Where the full economics hold: new feature work on the existing product, greenfield features in a brownfield codebase, any work where AI can take a well-formed spec. Where it takes longer: legacy-heavy refactoring with no test coverage, absent or unavailable Team Principal.
Two transition paths
Choose based on leadership's change tolerance and available qualified talent.
Either path has one organizer: the TPM, assigned by leadership. The TPM owns the transition plan and its critical path, the order in which teams move, the dependencies between converted and unconverted teams, the risk register and escalation, and the alignment of the sponsor and the Team Principal's stakeholders. The TPM also understands RACE and puts it in place: the right staffing in the right sequence, each person arriving when the work needs them, and a red flag raised early when the project needs something more. The steps below say where the decisions themselves sit.
Path A: Clean break
- Map who can transition. Survey the existing team for AI Fluency or clear intent to develop it. Non-engineering leads (Product Owner, Scrum Master, BA, UX Lead, Test Lead) → AI Product candidates; the Project Manager → TPM candidate; the Product Manager or business customer → Team Principal, client-side. Tech leads, senior and mid engineers → Pit Wall and Pit Crew candidates. Build the roster before forming teams. No qualification = no RACE Programming role.
- Form teams, release others. Qualified roster in hand → form one Pit Wall per separate product immediately, with its Pit Crew Quality Engineer from the first story, because a live product is already past its MVP; the Pit Crew Software Engineers follow as the backlog requires. Each product is its own engagement, coordinated by the TPM. Release or reassign those who didn't qualify; that call belongs to line managers and leadership, and the TPM schedules it into the plan. The number of teams follows the number of separate products, not the number of qualified candidates. Start the first story as soon as the first EUS is specified and priced.
- Clean break. Faster ROI, cleaner metrics, no cultural bleed from legacy process. Requires leadership support to make the transition non-negotiable. The TPM secures that support from the sponsor before day one and holds it through the cutover.
Path B: Incremental blend
- Convert one Scrum team into one Pit Crew. From qualified candidates, in the same order: the Pit Wall, the Quality Engineer, then the Pit Crew Software Engineers as the backlog requires. The other teams continue as Scrum teams on the existing backlog.
- Build the machinery, then move work onto the Pit Crew. The Forward Deployed Engineer builds the machinery that lets this one Pit Crew take over the work of the remaining Scrum teams, one stream at a time; a stream moves when the machinery can clear it. The TPM sets the order and puts the dependencies between the Scrum teams and the Pit Crew on the critical path, inside the project budget. People whose stream has moved are reassigned by line managers and leadership.
- Full transition when the last Scrum team's work has moved to the Pit Crew. Slower ROI, lower organizational risk, and it works where a hard cutover is politically impossible.
Role mapping for existing team members
Context mapping before the first story
Brownfield codebases require context work that greenfield doesn't. Before the first story:
- AI context audit. What can AI read in your codebase without misinterpreting it? Identify: well-tested modules (AI can execute reliably), legacy modules with no tests (AI needs supervision), undocumented business logic (requires human extraction before delegation).
- Technical debt strategy. Do not attempt to pay down technical debt and adopt RACE Programming simultaneously. RACE Programming's 4-gate DoD prevents new debt. Existing debt is addressed through dedicated EUS items, prioritized by Team Principal as deliberate investment, not a background task.
- Machinery after the frame. The Forward Deployed Engineer decides when to start building machinery and how much; nobody has to build it before solving the client's problem and setting the frame.
- Prototype scope. For brownfield features, the EUS prototype may need to integrate with existing APIs or data models. Pit Wall identifies integration constraints in the ADR component of each EUS before prototyping starts.
The first 30 days
Brownfield-specific metrics
See the Framework overview for full role and artifact specifications. If your team currently uses Scrum, the From Scrum guide covers role and ceremony translation in depth.