The Program Core Team: Cross-Functional Coordination at Scale

Definition

The program core team is a deliberately composed group that includes the program manager, software and hardware program managers (if needed), the program product owner, and representatives from all organizational functions whose work affects the final product: marketing communications, sales, deployment, legal, finance, human resources, and any others critical to delivery. This team meets regularly to identify and solve problems that no single feature team can address alone, and to make strategic decisions about resource allocation and program direction that affect the whole.

In the Book

Rothman distinguishes between the core team (responsible for business value and organizational coordination) and feature teams (responsible for delivering working software). A core team might number 8–12 people, selected for their standing and decision authority within their functions, not just their titles. The software program team is separate — its members solve technical problems across feature teams. The core team's responsibility is to remove obstacles that require cross-organizational negotiation: if deployment cannot meet a release frequency the software teams can sustain, the core team negotiates that conflict. If marketing needs performance data from the teams to finish collateral, the core team ensures that need is visible and prioritized.

The book emphasizes: "You can manage one program team." If you try to manage both a core team and a software program team yourself, you will not create the necessary collaboration. Larger programs (20+ teams) need a core program manager and a software program manager, each with their own meeting rhythm and focus.

Why It Matters

A program-level coordination structure solves the problem of organizational silos. In a single team, engineers talk to one another. In a program, feature teams can deliver working code while leaving the organization unable to release because marketing, sales, or deployment cannot complete their work. Without a designated core team meeting focused on cross-functional dependencies, these problems remain invisible until they block release. The core team creates a forum where strategic constraints bubble up and get resolved before they become crises.