Audio brief · 2 min

Where Did the PM and the Scrum Master Go in RACE?

Inside a RACE project the Scrum Master did not survive as a separate role: that care folded into AI Product, and agents now assemble the status and tracking. Project management did not disappear with AI agents. In RACE it belongs to one role, the TPM (Technical Program Manager): TPM is accountable for the project/contract goal(s) achievement. It owns the clock and leaves every answer with its owner.

Inside one project, meaning and requirements went to AI Product

The framework collapses five functions into one AI-native role. The AI Product card absorbs the Product Owner, Business Analyst, UX, Test Lead, and Scrum Master, and keeps operational coordination inside the project. The Project Manager’s project management goes to the TPM. Coordination overhead built to synchronize a seven-to-nine person team is removed. A small AI-augmented team needs no ceremony owners to stay aligned.

The Pit Wall has no separate ceremony owner. As the guide for Scrum teams notes, the Scrum Master evolves into AI Product, the specification half of the Pit Wall.

The distinction between project and product management remains strict. AI Product owns meaning and requirements, including operational coordination inside the project; the TPM owns that everything comes together and gets delivered. The Product Manager maps client-side to the Team Principal. The Pit Wall mediates all feedback, and the Team Principal never communicates directly with the Pit Crew.

The bookkeeping went to agents

Status aggregation and tracking are the first tasks automation clears. Jason Flynn of Scaled Agile observed in September 2026 that AI can automate status updates, summarizes sprint progress, flags risks, and streamlines cross-team communication. The most exposed roles rely on information relay, meeting facilitation, and status aggregation.

Flynn notes that durable coordination focuses on judgment, conflict resolution, and capability development. In RACE, an agent assembles the project picture: the Executable Product Roadmap and Executable Product Backlog, real-time status, and risks. The TPM works from that picture: sequencing, trade-offs, when to escalate. So inside one project the work still has owners: AI Product for meaning and requirements, the TPM for the project goals, agents for the bookkeeping.

Who answers for the goals

Scaling exposes an unaddressed boundary. The comparison with SAFe notes that a program once requiring an Agile Release Train of 50 to 125 people can often be delivered by a handful of micro-teams. The framework did not say who answers for the goals of that work.

The RACE Engineer does not fill this void. As the scaling essay describes, the RACE Engineer develops delivery machinery, including agents, workflows, guardrails, and evals. That role sits above projects, part-time and on request, the way DevOps does today. Answering for the goals of a project is a different job.

The role is TPM

The industry already has a name for this discipline: Technical Program Manager. Amazon describes the role at Annapurna Labs directly: “This is not a status-reporting role.” Amazon expects the TPM to connect engineering workstreams into a single coherent schedule, identify the real critical path week to week, and drive cross-functional decisions.

Mario Gerard marks the boundary: “TPMs don’t decide how to build, and they don’t manage engineers.” A TPM aligns teams and drives the plan, but does not make deep technical decisions or execute directly through engineers.

RACE gives the TPM the decision rights that keep it from sliding into a status collector. The TPM alone decides the sequencing of work, the critical path, the rhythm of forums and the risk register. It also sets a deadline for every dispute, and a dispute still open at its deadline escalates with a decision date.

The TPM also understands RACE and puts it in place on the project: 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.

Everything else the TPM escalates to its owner. Product priorities go to the Team Principal and AI Product, architecture to the Forward Deployed Engineer. People go to line managers and leadership. The TPM manages the project budget and keeps the work inside it; raising the budget or changing scope is the Team Principal’s decision, which the TPM brings as a change request.

The Sporting Director metaphor

The Formula 1 metaphor clarifies the division of labor. In F1, a race engineer works one car from the garage. The Sporting Director sits on the pit wall and answers for the team’s race results within the sporting regulations. The Team Principal operates in a wider zone: budget, sponsors, and long-term strategy.

In RACE, AI Product and the Forward Deployed Engineer decide what to build and how for their own Pit Wall, as a race engineer works one car. The TPM answers for the project goals, aligns the plan and dependencies, and overrides none of their decisions. The contract plays the part of the regulations. It keeps the Team Principal’s stakeholders, neighboring teams, outside resources and sponsor informed. Product work still goes through the Pit Wall.

TPM is the title; Sporting Director is only the metaphor. A project with goals to reach needs that seat, and in RACE the TPM takes it.

What the role is not

A common objection claims that RACE removed the coordinator only to restore it one level up. If that were true, the overhead built to synchronize a seven-to-nine person team would come back, now over a program that once took an Agile Release Train of 50 to 125 people. The coordinator inside the team is gone and stays gone.

The TPM owns no backlog and manages no people, and agents handle the bookkeeping. Leadership decides how much of a TPM a project needs when it forms the team. On a given project the TPM may work part-time. RACE scales through machinery, so one TPM can own delivery of more than one project from inside each.

The TPM is distinct from every legacy post. A Scrum Master optimizes one team from within, and that care folded into AI Product. Project management stays, with the TPM. A line manager evaluates people and a RACE Engineer builds machinery; the TPM does neither. So the overhead stays gone: the TPM is one seat, often part-time, that leadership sizes for each project.

Inside one Pit Wall AI Product decides and agents keep the record. The TPM keeps the clock and answers for the project goals. It holds decision rights over the schedule and none over the answer, and leadership sizes its share for each project.

Comments and ideas

If these problems sound familiar from your own work, write to me directly on LinkedIn or at paul@raceprogramming.com to share what you have found.

Help putting it in place

If you want help putting in place what this essay describes, First Line Software offers that as a service.


Written by Pavel Khodalev, author of RACE Programming and CTO of First Line Software. Follow new essays via RSS.