RACE Programming vs Shape Up
Shape Up fixes a six-week appetite, shapes work before betting on it, and keeps teams small. RACE Programming shares those instincts (fixed time, variable scope, small autonomous teams) but shrinks the batch to one Executable User Story because the team is AI-augmented, and turns "shaping" into the Executable User Story.
Shared instincts, compressed batch
| Dimension | RACE Programming | Shape Up |
|---|---|---|
| Fixed vs variable | Fix any two of scope, time, budget; quality never a lever | Fixed time (appetite), variable scope |
| Designed for | AI-augmented teams (engineer-led, agent-executed) | Small human product teams |
| Cycle | Continuous Kanban flow; each Executable User Story production-ready in 2-3 days at the floor; Pit Stops on the client's release cadence | Six-week cycle + two-week cooldown |
| Defining the work | Executable User Story: precise, testable, Gherkin acceptance | Shaping: bounded, at the right abstraction, before betting |
| Who decides what to build | Team Principal (client-side; budget, product direction) | Betting table (leadership picks bets each cycle) |
| Scope control | Story ships when its four DoD gates pass | Circuit breaker: no automatic extension past the cycle |
Six weeks was the human batch size
Shape Up gets a lot right, and RACE Programming agrees with it more than it disagrees: define work before committing, fix the time and flex the scope, keep the team small and autonomous, and refuse to let projects drift. Those are durable ideas.
The six-week cycle, though, is calibrated to human throughput, it is roughly how long a small human team needs to ship something meaningful end to end. When AI shifts engineering economics by an order of magnitude, meaningful work ships in days, so the natural batch shrinks. RACE Programming keeps the shaping discipline and the fixed-time instinct but reruns them on a single story, production-ready in two to three days, and makes the shaped work an Executable User Story that can be delegated to and validated against the AI agent.
How Shape Up roles map across
| Shape Up role | RACE Programming role |
|---|---|
| Betting table (leadership) | Team Principal: client-side; budget, product direction, UAT |
| Shapers (senior) | AI Product + Forward Deployed Engineer: shape work into an Executable User Story on the Pit Wall |
| Builders (programmers) | Pit Crew Software Engineer: AI-augmented execution, Inner Cycle 2×/day |
| Builders (designer / QA duties) | Pit Crew Quality Engineer: validates AI output against EUS Gherkin |
| (no equivalent) | Silicon Software Engineer: the AI agent, present in Pit Wall and Pit Crew; not human headcount |
The triangle moves
Scope, time, and budget are the three sides of every project; quality is the area inside, fixed, never a lever. You set two sides, and RACE Programming moves the third. A senior-only RACE team delivers a Scrum team's output about 2× faster at roughly 0.75× the cost, about 3× the work per dollar. One efficiency, three doors:
- ~3× the finished software for the same budget and deadline
- ~⅓ the cost for the same scope on the same clock
- 2-5× faster time-to-business-result, since each Executable User Story is production-ready the moment its gates pass, not gated to a cycle
What we see now: the three figures above, worked out from two team shapes on the framework page. Measured: in the agent-to-agent data imports case, against our estimate for a team that already works with AI tools, all three sides moved at once: the cost of production came to about a third, the same scope took 7.1 times less human effort, and end-to-end speed stayed about the same, four months against an estimated 4.5, because that team had itself moved to Kanban in production and kept sprints only as a release cadence. Shape Up already keeps teams small; RACE Programming keeps that shape and moves the economics.
Using Shape Up? Shaping and fixed appetites carry over almost directly. The framework page shows how they become the Executable User Story and the release cadence.