What is the difference between RACE Programming and Kanban?

Kanban is an evolutionary flow-management method: you visualize the workflow, limit work in progress, manage flow, and improve gradually, without prescribing roles, iterations, or how the work is actually done. It sits on top of whatever process you already run. RACE Programming is a prescriptive Agentic SDLC framework: it specifies roles, mandatory artifacts, ceremonies, and AI-native execution for delivering software with the Silicon Software Engineer (the AI agent). Kanban tells you to manage your flow; RACE Programming tells you how to build, and runs a kanban flow inside its own delivery cycle.

Is RACE Programming a replacement for Kanban?

It operates at a different layer, and it keeps the part of Kanban that works. Kanban is method-agnostic: it optimizes the flow of an existing process but does not define the engineering model, roles, or practices. RACE Programming defines all of those, and inside the Stint the Pit Crew runs its Inner Cycle on a kanban flow with explicit work-in-progress limits. So RACE Programming does not reject Kanban; it absorbs Kanban's flow mechanics into a complete, prescribed delivery model built for AI-augmented teams.

Does RACE Programming use work-in-progress limits and pull?

Yes. The Pit Crew's Inner Cycle (Spec, Build, Align) runs twice per day as a pull-based kanban flow with limited work in progress, which is exactly the Kanban discipline. The difference is scope: Kanban stops at flow policy, while RACE Programming also prescribes who is on the team, what an Executable User Story is, how AI output is validated, and how a Stint ends in a Pit Stop (a production deployment).

Kanban has almost no prescribed roles. What does RACE Programming prescribe instead?

Kanban deliberately prescribes no engineering roles (its optional roles, Service Delivery Manager and Service Request Manager, are about flow, not building software). RACE Programming prescribes a full role set: a client-side Team Principal; an AI Product and an Forward Deployed Engineer on the Pit Wall; Pit Crew Software Engineers and a Pit Crew Quality Engineer in delivery; and the Silicon Software Engineer, the AI agent, present across both and adding no human headcount.

How much more efficient is RACE Programming than a Kanban team?

Quality is held fixed, so locking any two of scope, time, and budget moves the third. A senior-only RACE team delivers a Scrum team's output about 2x faster at roughly 0.75x the cost, about 3x the work per dollar. Kanban improves the throughput of an existing team but does not change the underlying engineering economics; RACE Programming changes the economics by making the team AI-augmented and senior-only. Conservative figures, measured on delivered projects.

By Pavel Khodalev, CTO at First Line Software · July 9, 2026

Compare

RACE Programming vs Kanban

Kanban is a flow-management method that sits on top of whatever process you already run. RACE Programming is a prescriptive Agentic SDLC framework that defines the whole delivery model, and runs a kanban flow inside its own cycle. They are not rivals so much as different layers, and RACE Programming keeps the part of Kanban that works.

At a glance

Two layers, not two rivals

Dimension	RACE Programming	Kanban
What it defines	The whole delivery model: roles, artifacts, ceremonies, AI-native execution	Flow policy over an existing process; not the work itself
Designed for	AI-augmented teams (engineer-led, agent-executed)	Any team wanting smoother flow, evolutionary change
Flow mechanics	Kanban flow inside the Inner Cycle, WIP-limited, twice daily	Visualize flow, limit WIP, manage flow, explicit policies
Roles	Team Principal · Forward Deployed Engineer · AI Product · Pit Crew Quality Engineer · Pit Crew Software Engineer · Silicon Software Engineer (AI)	None prescribed (optional: Service Delivery / Request Manager)
Cadence	Stint at the client's pace, ending in a Pit Stop (production deploy)	Continuous flow; optional cadences for replenishment and review
Metrics	Four Definition-of-Done gates per Stint; idea-to-production time	Lead time, cycle time, throughput, WIP, cumulative flow

Why it changed

Managing the flow is not the same as changing the work

Kanban is a genuinely good idea, and RACE Programming uses it. Visualizing work, limiting work in progress, and managing flow make almost any process smoother. But Kanban is deliberately method-agnostic: it improves the flow of whatever you already do without saying who should be on the team, how software should be built, or what "done" means.

When AI shifts engineering economics by an order of magnitude, the flow is not the constraint, the delivery model is. A smoother flow of the old way of working still leaves you with the old roles, the old headcount, and the old handoffs. RACE Programming prescribes the new model, senior micro-teams delegating to and validating the AI agent, and then runs a WIP-limited kanban flow inside it. You keep Kanban's discipline; you change the thing the discipline is applied to.

What each layer owns

Where Kanban stops and RACE Programming continues

Concern	Kanban	RACE Programming
Flow and WIP	Core discipline	Adopted, inside the Inner Cycle
Who is on the team	Not defined	Prescribed role set, senior-only micro-team
How software is built	Not defined	Spec-driven, delegated to and validated with AI
What "done" means	Left to the team	Four Definition-of-Done gates per Stint

Economics

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 ships the moment it is ready, not gated to a batch

Conservative figures, measured on delivered projects, not projections. Kanban improves how smoothly a team moves; it does not change the underlying engineering economics the way an AI-augmented, senior-only team does.

Already running Kanban? Its flow discipline carries straight into the Inner Cycle. The framework page shows where it fits inside the full delivery model.

Read the framework → · More comparisons →

FAQ

Frequently asked questions

What is the difference between RACE Programming and Kanban?: Kanban is an evolutionary flow-management method: you visualize the workflow, limit work in progress, manage flow, and improve gradually, without prescribing roles, iterations, or how the work is actually done. It sits on top of whatever process you already run. RACE Programming is a prescriptive Agentic SDLC framework: it specifies roles, mandatory artifacts, ceremonies, and AI-native execution for delivering software with the Silicon Software Engineer (the AI agent). Kanban tells you to manage your flow; RACE Programming tells you how to build, and runs a kanban flow inside its own delivery cycle.
Is RACE Programming a replacement for Kanban?: It operates at a different layer, and it keeps the part of Kanban that works. Kanban is method-agnostic: it optimizes the flow of an existing process but does not define the engineering model, roles, or practices. RACE Programming defines all of those, and inside the Stint the Pit Crew runs its Inner Cycle on a kanban flow with explicit work-in-progress limits. So RACE Programming does not reject Kanban; it absorbs Kanban's flow mechanics into a complete, prescribed delivery model built for AI-augmented teams.
Does RACE Programming use work-in-progress limits and pull?: Yes. The Pit Crew's Inner Cycle (Spec, Build, Align) runs twice per day as a pull-based kanban flow with limited work in progress, which is exactly the Kanban discipline. The difference is scope: Kanban stops at flow policy, while RACE Programming also prescribes who is on the team, what an Executable User Story is, how AI output is validated, and how a Stint ends in a Pit Stop (a production deployment).
Kanban has almost no prescribed roles. What does RACE Programming prescribe instead?: Kanban deliberately prescribes no engineering roles (its optional roles, Service Delivery Manager and Service Request Manager, are about flow, not building software). RACE Programming prescribes a full role set: a client-side Team Principal; an AI Product and an Forward Deployed Engineer on the Pit Wall; Pit Crew Software Engineers and a Pit Crew Quality Engineer in delivery; and the Silicon Software Engineer, the AI agent, present across both and adding no human headcount.
How much more efficient is RACE Programming than a Kanban team?: Quality is held fixed, so locking any two of scope, time, and budget moves the third. A senior-only RACE team delivers a Scrum team's output about 2x faster at roughly 0.75x the cost, about 3x the work per dollar. Kanban improves the throughput of an existing team but does not change the underlying engineering economics; RACE Programming changes the economics by making the team AI-augmented and senior-only. Conservative figures, measured on delivered projects.