What is the TPM in RACE Programming?

Beside the Pit Walls, not inside them

A RACE team is a Pit Wall and a Pit Crew working for one Team Principal. The TPM sits above several such teams, next to their Pit Walls. The teams can be related, as parts of one program, or independent, including teams from different engagements.

The name is the one the industry already uses. The metaphor comes from Formula 1, where the Sporting Director runs race operations for the whole team, not for one car, and on race day sits on the pit wall, while each race engineer works from the garage. 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 how the work of several teams converges on a result.

Who owns what above and inside the team

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 across teams;
• 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 are cross-team. They do not add ceremonies inside a Pit Crew, where the retrospective remains the one ceremony RACE kept, and they do not change the team's Kanban limits or the release cadence, which stay with AI Product.

The TPM escalates:

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 together the plans and dependencies of several Pit Walls, but does not decide for AI Product and the Forward Deployed Engineer what to build or how.
• RACE Engineer. The neighboring role above engagements. It owns the machinery and comes in on request.
• Leadership. Forms the project team and decides whether the project needs a TPM, and how much of one.
• Line managers. Manage people outside the project work. This sits outside the RACE role model, and the TPM does not manage people.

Measured in teams

The seniority of the role is measured by how many teams one person coordinates at the same time. As that number grows, so does the level of the specialist.

There is no fixed number of teams 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, not on request. Part-time means one person carries several teams. On a given engagement the TPM can be part-time or not needed at all, and that is decided by leadership, not by the team. The TPM is overhead of the delivering company, not a separate line in the engagement.

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 teams a TPM coordinates exist for their own reasons: separate products, separate engagements, neighboring teams on the client side. The TPM is not a way to grow one engagement by splitting its backlog across more teams. RACE scales through the machinery, not through headcount.

What the agent does

The agent assembles the cross-team picture: each team's Executable Product Roadmap and Executable Product Backlog, real-time status, and risks. The roadmaps and backlogs themselves are authored by each team's AI Product with its Team Principal. The TPM works from the assembled picture: the sequence, the trade-offs between teams, the call on when to escalate.

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 looks from outside and across teams.
• Not a project manager inside a project. That role is folded into AI Product.
• 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.