How long does the transition from Scrum to R ACE P rogramming take?

The structured transition takes 90 days across three phases: Pilot Pit Wall (weeks 1–2), First Stint (weeks 3–6), Full Transition (weeks 7–12). Similar Agile-to-continuous-flow transitions typically take 5–12 weeks for the core mechanics; the 90-day plan accounts for cultural adoption and metric migration.

What happens to the Scrum Master role in R ACE P rogramming?

The Scrum Master role evolves into Pit Wall (ACE TL). It is not eliminated — it upgrades. Instead of facilitating ceremonies, the Pit Wall co-authors Executable User Stories, builds prototypes on synthetic data, translates client intent into AI-executable specs, and owns the delivery contract between client and Pit Crew.

What replaces velocity in R ACE P rogramming?

Velocity is replaced by Executable User Stories per Stint plus delivery cost per item. This metric is client-visible, comparable across teams, and AI-compatible. Story points encode human effort — they break when AI writes the code. EUS/Stint measures actual delivery regardless of who or what built it.

Can we run R ACE P rogramming and Scrum in parallel during transition?

Yes. The recommended approach for weeks 1–2 is to pilot the Pit Wall pair without changing the dev team's Scrum process. The first full Stint (weeks 3–6) runs alongside the existing Scrum structure. Full transition (weeks 7–12) retires the Scrum ceremonies once the R ACE P rogramming cadence is proven.

Practice Guide · Scrum Transition

From Scrum to RACE Programming

A practitioner's transition guide. Every Scrum role, artifact, and ceremony mapped to its RACE Programming equivalent — with a 90-day plan and the metrics to validate it worked.

Contents

Why Scrum breaks under AI
What Scrum got right
Role translation
Artifact translation
Ceremony translation
The 90-day transition
Objections
What to measure

Why

Why Scrum breaks under AI

The ceremony tax

22.5% of team capacity goes to Scrum events — constant across sprint lengths. Sprint Planning, Daily Scrum, Sprint Review, Retrospective, Refinement: ~18 hours per developer per two-week sprint, ~9 hours per developer per week. 47% of teams report feeling constrained by mandatory events. 33% name overhead as the #1 problem.

Velocity is broken

Velocity was designed to measure human coding capacity. When AI makes developers 55.8% faster (arXiv controlled trial, Copilot), story-point estimates are off by 2×. Velocity is not comparable across teams, not comparable to AI-augmented baselines, and not visible to clients. 61% of teams track it anyway.

The spec problem Scrum never solved

The Definition of Ready is optional in the Scrum Guide. Most teams start sprints with stories that require mid-sprint clarification. "As a user, I want to see my dashboard" is a wish, not a spec. An AI reads it literally — builds something — and it is wrong. 63% of teams report declining software quality (18th State of Agile, 2025).

AI and Scrum: speed mismatch

46% of AI pilots fail because the delivery model doesn't match AI's throughput. Scrum assumes human effort is the bottleneck. AI moves the bottleneck to specification (upstream) and human validation (downstream). Sprint boundaries create review pile-ups: a week of AI-generated code lands for review at sprint end, with no scaled review capacity.

What carries forward

What Scrum got right

RACE Programming builds on these — it does not discard them:

Iterative delivery. Ship working software at a defined cadence. RACE Programming keeps this as the Stint.
Cross-functional teams. One team owns delivery end-to-end. RACE keeps this: Pit Wall + Pit Crew is a single accountable unit.
Visible backlog. Work is explicit and prioritized. RACE extends this: nothing enters the Executable Product Backlog without all six AI-facing spec components.

Who

Role translation

Scrum Role	RACE Programming	What changes
Product Owner	Team Principal	Business owner / client decision-maker. Stays client-side. Holds budget and product direction. Approves Executable Product Roadmap and prototypes before coding starts.
Scrum Master Proxy PO · BA · UX Lead · Test Lead · PM	AI Product	Six delivery roles absorb into one AI-native position. Authors Executable User Stories, Gherkin acceptance scenarios, NFR specs. Context Manager in Pit Crew. Eliminates coordination overhead.
AI Fluent Senior Developer (Scrum Developers)	ACE Software Engineer	AI Fluency at senior level required. Pit Wall mode: prototype build + ADR + CI/CD. Pit Crew mode: codes alongside AI tools as engineer.
AI Fluent Technical Lead (Scrum Developers)	ACE Technical Lead	Serves 2–5 Pit Crews simultaneously at 20% allocation each. Triggered when Team Principal absorption exceeds one ACE Software Engineer's Pit Wall capacity.
AI Fluent Senior / Middle Developer (Scrum Developers)	Pit Crew	AI Product + 1–2 AI Fluent Senior or Middle Developers. AI-augmented execution. Inner cycle 2×/day. No ceremonies.

What

Artifact translation

Scrum Artifact	RACE Programming	Key difference
Product Backlog	Executable Product Backlog	Every item = fully-specified Executable User Story. Nothing enters Pit Crew without all six AI-facing components.
Product Goal	Executable Product Roadmap	Quarterly, Stint-projected, with delivery cost per item. Client approves before budget commits.
User Story	Executable User Story (6 components)	Adds: Prototype · EARS NFR · Architecture Decision Record · Gherkin scenarios · Test Data. Estimate added for client visibility — not an AI-facing spec component.
Sprint (2 weeks)	Stint (adaptive: 3 days – quarterly)	Prototype-first before any coding. Adaptive cycle — matches client's release cadence.
Velocity (story points)	EUS / Stint + delivery cost	Client-visible. Comparable across teams. AI-compatible — story points break when AI writes the code.
Definition of Done (improvised)	4-gate Definition of Done	Unit tests ≥80% coverage · Integration tests · End-to-end tests · Acceptance tests — all automated.

How

Ceremony translation

Scrum Ceremony	Status	RACE Programming equivalent
Sprint Planning	Gone	Replaced by per-story estimation at Handover. Pit Crew receives each EUS individually and gives cost estimate before coding starts.
Daily Standup	Evolved	2×/day sync with AI Product. Asynchronous, no ceremony.
Sprint Review	Evolved	Pit Stop Demo — client acceptance testing in staging at Stint end. Shorter, outcome-driven.
Sprint Retrospective	Gone	Pit Wall continuous improvement — embedded, not scheduled. No ceremony.
Backlog Refinement	Evolved	Pit Wall authors EUS + builds prototype. Client validates concept before development starts — no coding until approved.

~20%+ of developer capacity recovered from eliminated ceremonies. That's 9 hours per developer per week redirected to delivery.

How

The 90-day transition

Weeks 1–2

Pilot Pit Wall

Identify the Pit Wall pair (Scrum Master + senior dev). Run the first EUS authoring session. Build a prototype for the highest-priority story on synthetic test data.

Do not change the dev team's process yet.

Weeks 3–6

First Stint

Run the first full Stint. Pit Wall authors EUS on Monday. Pit Crew executes. Pit Stop Demo on Friday.

Measure: hours saved vs. sprint ceremonies. Compare throughput to previous sprint.

Weeks 7–12

Full Transition

Executable Product Roadmap replaces the sprint roadmap. Executable Product Backlog replaces the backlog. All stories converted to EUS. Velocity metric retired.

Produce the first quarterly EPR with the client.

What practitioners resist

"My role disappears."

Scrum Masters become Pit Wall. The role upgrades — from facilitating ceremonies to co-authoring delivery contracts and building prototypes. More impact, fewer meetings.

"Our release cadence doesn't fit."

Stint adapts to the client's release cadence — 3 days to once per quarter. RACE Programming doesn't dictate when you ship. It matches your rhythm with less overhead.

"We lose our velocity metric."

Replaced by EUS / Stint + delivery cost. A metric the client understands and approves before work starts. Velocity was never comparable across teams anyway.

"More spec burden upfront."

EUS is more detailed than a user story. It eliminates mid-sprint clarifications, rework, and acceptance disputes. Front-loaded spec = zero back-end chaos.

Objections

What you'll hear. What to say.

Scrum Master objections

"We've invested years in Scrum culture."

74% of organizations now use hybrid or homegrown approaches. Scrum Master job postings dropped 49% between 2020 and 2024. The market moved first.

"Sprint commitments give the team safety."

Sprint commitments protect the process, not delivery. 47% of teams feel constrained by rigid events. EUS sign-off before coding = real safety — the spec is approved, not the calendar.

"Our velocity is improving."

Velocity that isn't comparable to other teams or to AI output isn't a signal — it's a local story. EUS/Stint is observable, client-verified, and AI-compatible.

Product Owner objections

"I lose control without sprint planning."

You gain control where it matters: you approve the EPR (quarterly roadmap with costs) and each EUS prototype before a line of code is written. More control, not less.

Engineering objections

"Story points help us estimate."

Story points encode human effort. Copilot makes developers 55.8% faster — estimates are now off by 2×. EUS estimates are in hours and dollars: what the client sees and approves.

"We can't prototype every story in 1–2 days."

Pit Wall prototypes on synthetic data using AI tools. A mid-sized feature prototype: 4–8 hours. That's the point of the Pit Wall role — it's not the full team prototyping.

How to measure success

What to measure in the first 90 days

Metric	How to measure	Success looks like
Ceremony hours recovered	Hours/week per developer before vs. after	≥ 8 hours / developer / week recovered
EUS acceptance rate	% of EUS accepted without revision after prototype review	> 80% first pass by month 2
Pit Stop pass rate	% where staging UAT passes on demo day	> 70% in first 3 Stints
Rework rate	Stories returned to Pit Crew after delivery	< 10% after month 2
Client feedback cycle time	Days from build-start to client validation	≤ one Stint duration by week 6

The first step

Identify your highest-priority story. Build a prototype. Show the client before writing a line of code. That's the first EUS prototype. That's how RACE Programming starts.

Ready to start? The Framework overview covers all roles, artifacts, and ceremonies in depth. To talk through the transition for your specific team, reach out directly.