What is the TPM in RACE Programming?
TPM is accountable for the project/contract goal(s) achievement. The TPM (Technical Program Manager) is the RACE Programming role that holds project management. The product, the architecture and the people stay with their owners. The agent assembles status and risks; the TPM works from that picture. One TPM can carry more than one project, part-time on each.
Project management stays, and the TPM holds it
Project management does not disappear with AI agents; in RACE it belongs to the TPM. Agents take the bookkeeping: status, tracking, the risk picture. Someone still answers for whether the project reaches its goals, and that is the TPM. It owns:
- risks;
- dependencies;
- the critical path;
- deadlines;
- people load;
- the scope of each phase;
- client expectations.
The TPM manages the project budget: it keeps the plan and staffing inside it and raises a flag before it runs short. When the budget, a goal, the scope or a deadline has to move, the TPM brings a change request to the Team Principal, who decides. The contract is one of the TPM's constraints: the TPM delivers the goals inside it and says early when they no longer fit.
The TPM knows RACE and puts it in place
The TPM is expected to understand RACE well: how it works, where its nuances are, what it does well and where it falls short. Staffing a RACE project takes more than counting people against a plan, so the TPM sets RACE up on each project they carry:
- The right staffing. The roles the project needs, with no surplus.
- The right sequence. The Pit Wall first, the Quality Engineer after the MVP, the Pit Crew Software Engineers as the backlog requires, a RACE Engineer when the Forward Deployed Engineer asks for one.
- The right moment. Each person arrives when the work needs them.
- The red flag. Raised early, when the project is going to need something it does not have.
Leadership and line managers assign the people. The Forward Deployed Engineer decides when to build machinery and how much.
With the project, next to the Pit Wall
A RACE team is a Pit Wall and a Pit Crew working for one Team Principal. The TPM works with that team on its project, next to the Pit Wall, and answers for the project's goals. One TPM can carry more than one project, part-time on each. The projects can be related, as parts of one program, or independent, including different engagements.
The name is the one the industry already uses. The metaphor comes from Formula 1, where the Sporting Director answers for the team's race results within the sporting regulations and on race day sits on the pit wall, while each race engineer works one car from the garage. For the TPM, the contract plays the part of the regulations. The Team Principal's zone is wider: budget, sponsors, long-term strategy.
The TPM is separate from the RACE Engineer. The RACE Engineer owns how software gets built. The TPM owns that the project reaches its goals.
Meaning and requirements, delivery of the whole
| Role | Owns |
|---|---|
| AI Product | Meaning and requirements, including the long analytical documents and operational coordination inside the project |
| TPM | That everything comes together and gets delivered: the end-to-end view of the seams between components and the end-to-end acceptance |
Who owns what in a project
| Role | Span | Owns | Does not touch |
|---|---|---|---|
| AI Product | One Pit Wall | Meaning and requirements: the flow and its Kanban limits, the Executable User Story, the team's roadmap and backlog, acceptance with the Team Principal | Other Pit Walls |
| Forward Deployed Engineer | One Pit Wall | Prototypes, architecture (ADR), the engagement's delivery machinery | The project plan and deadlines |
| TPM | The project or contract; one TPM can carry more than one, part-time on each | Achievement of the project goals: putting RACE in place, the plan and critical path, risks, dependencies, deadlines, people load, phase scope, client expectations, end-to-end acceptance | What and how to build, the machinery, managing people, commercial decisions |
| RACE Engineer | All engagements, on request | The machinery: agents, workflows, guardrails, evals, telemetry | Project schedules and dependencies |
The container, not the contents
The TPM owns the container, not what goes in it: the clock, not the answer. A role like this needs decision rights of its own, or it turns into a collector of status reports. The rights below match those of a mid-level TPM at a large technology company.
The TPM decides:
- the plan and sequence of work in the project;
- the critical path;
- the format and rhythm of status and forums;
- the risk and dependency register;
- when to escalate, and to whom;
- the deadline for a dispute: a dispute not settled by its deadline goes up with a date for the decision.
The forums sit at project level. They add no ceremonies inside a Pit Crew, where the retrospective remains the one ceremony RACE kept, and they leave the team's Kanban limits and the release cadence with AI Product.
The TPM escalates:
| Question | Who decides |
|---|---|
| What to build, priorities | Team Principal, AI Product |
| How to build it, architecture | Forward Deployed Engineer |
| People, team composition (the TPM brings the sequence and raises the red flag) | Line managers, leadership |
| Raising the budget, changing scope (the TPM manages spend inside the budget and raises a change request) | The Team Principal |
Who the TPM works with
- Team Principal. The TPM coordinates work with the Team Principal where that is needed. The larger part of the job is around the Team Principal: the expectations, information and alignment of their stakeholders, the neighboring teams, the resources outside the teams, and their sponsor. Work on the product follows the canon: all contact is via the Pit Wall. The Pit Wall keeps ideation and acceptance throughput with the Team Principal.
- Pit Wall. The TPM brings the Pit Wall's plan, dependencies and risks together with everything else the project needs, and leaves what to build and how with AI Product and the Forward Deployed Engineer.
- Team Principal. Decides on raising the budget and moving goals, scope or a deadline. The TPM manages spend inside the budget and brings the change requests.
- RACE Engineer. The neighboring role across engagements. It owns the machinery and comes in on request.
- Leadership. Forms the project team and decides how much of a TPM the project needs.
- Line managers. Manage people outside the project work. This sits outside the RACE role model, and the TPM does not manage people.
Measured by the goals carried
The seniority of the role grows with the size and complexity of the goals one person is accountable for, and with how many projects they carry at the same time.
There is no fixed number of projects per TPM. It depends on the complexity of the work, the number of stakeholders, the Team Principal's habits, and the skills of the Pit Walls and Pit Crews. Leadership weighs this when it forms the team.
The role is permanent, and it is often part-time: one person carries more than one project, a share of the week on each. Leadership decides that share for a given project.
A transition to RACE always has one. Moving teams off their old process is cross-team work even when one team converts first: the converting team, the teams still on the old process, the sponsor and the Team Principal's stakeholders all have to move on one plan. Leadership assigns a TPM to organize the transition, part-time when the scope is small. The practice guides show what the TPM does at each step.
The projects a TPM carries exist for their own reasons: separate products, separate engagements. Splitting one backlog across more teams does not grow an engagement. RACE scales through the machinery, not through headcount.
What the agent does
The agent assembles the project picture: the team's Executable Product Roadmap and Executable Product Backlog, real-time status, and risks. The roadmap and backlog themselves are authored by AI Product with the Team Principal. The TPM works from the assembled picture: the sequence, the trade-offs, the call on when to escalate or raise a change request.
What the TPM is not
- Not a Scrum Master. A Scrum Master looks after the effectiveness of one team from the inside, and in RACE that care is already part of AI Product. The TPM answers for the project's goals.
- Not the budget owner. The TPM manages spend inside the project budget; raising it is the Team Principal's decision, the TPM brings the change request.
- Not a line manager. The TPM does not hire, evaluate or grow people.
- Not a RACE Engineer. The TPM does not own the machinery and does not come in on request.
The TPM answers for the goals of RACE Programming projects. See how the Team Principal, Pit Wall and Pit Crew work inside one team.
Read the framework → · What is the Pit Wall? → · The RACE Engineer →