A project office designed for projects in a predictive life cycle works on variances: a date met or not, a budget consumed against the budget approved, a scope delivered against the scope signed. Agile teams no longer provide it with this material, because their detailed content is decided iteration after iteration and no detailed end-to-end plan serves as a baseline. Common usage calls an agile PMO the project office that has drawn the consequences of this observation.
Its stance changes, in our reading, on several points. It plans a cadence and a capacity, and leaves the detail of the work to the teams. It measures what is delivered. It prepares priority arbitrations where it used to investigate change requests. It stops asking for percentages complete and reports that the teams’ tools already contain. Its mandate remains the same: informing those who decide on comparable bases, and preparing their decisions.
Project PMO and agile PMO, line by line
In the predictive life cycle, of which the V-model is one form, scope, date and budget are set at launch, then the project is measured against that plan. In the agile regime, stable teams deliver in short iterations a product whose content is adjusted along the way.
| Project PMO in a predictive life cycle | PMO serving agile teams | |
|---|---|---|
| Object tracked | Projects, each with an end date | Lasting products or work streams, carried by stable teams |
| Planning | Milestones, critical path, workload plan for each project | Common calendar of iterations, team capacity, dependencies between teams |
| Measurement | Variances in date, cost and scope against a baseline | Items delivered and usable, lead time between a request and its release, objectives achieved over the period |
| Arbitrations prepared | Change requests, reinforcements, rescheduling | Order of priorities between products, allocation of capacity, unresolved dependencies |
| Budget framework | One budget per project, committed to a scope | Capacity funded for a period, whose use is reviewed |
The SAFe framework has given this shift a name. The public part of the “Value Management Office” page on its website (framework.scaledagile.com, read on 12 November 2026) calls Value Management Office (VMO) the function that facilitates lean portfolio management. It states that VMOs often emerge from the existing PMO; the rest of the page requires an account and is not described here. This vocabulary belongs to a framework: a project office can change its stance without adopting it.
Planning concerns cadence and capacity
In a predictive life cycle, the PMO consolidates schedules: it checks sequences, follows the critical path and flags threatened milestones. With agile teams, the detail of the work is not its concern. The Scrum Guide (scrumguides.org, November 2020) describes self-managing teams, which “internally decide who does what, when, and how”.
The office then plans what the teams have in common. It maintains the calendar of iterations and joint planning events, of which the SAFe framework’s PI planning is one form. It maintains the view of capacity: how many teams, on which products, for what period. It also records the dependencies these planning events bring to light, in particular those that fall outside the agile scope: a supplier, an infrastructure team, a regulatory deadline.
The long horizon does not disappear. To senior management asking what will be available in several months, the office answers with period objectives, each with a degree of certainty, according to the convention described in our article on the roadmap of an IT project.
Measures taken on what is delivered
In Scrum, an item is either done or not: the Scrum Guide states that work that does not meet the conditions of the Definition of Done cannot be considered an Increment. The first measure of the agile PMO is therefore an observation: what has been delivered and meets the agreed definition.
Flow measures can be added: the lead time between a request and its release, the frequency of releases, the share of a period’s objectives actually achieved. Each rests on a convention to be written down, like the traditional measures covered in our article on PMO KPIs.
Velocity calls for a precaution. In practice, a team that tracks it expresses it in a unit it has chosen, to forecast its own workload; adding it up or comparing it from one team to another may then bring together different units.
None of these measures shows whether what is delivered is useful. That observation is made after release, with the business owner or the product owner, and the PMO keeps the schedule for it.
Arbitrations of priority and capacity
In a predictive life cycle, the office investigates change requests: a modification of the signed scope, with its effect on date and cost. In a Scrum team, the order of work is settled in the Product Backlog, for which the product owner is accountable: it does not need to go up to a committee.
What goes up is of a different nature. Two products claim the same team. A dependency cannot be resolved by any of the teams concerned. Capacity must move from one subject to another during the year. The agile PMO prepares these files like the previous ones, in the form of options expressed in capacity and lead time, and presents them at the dates when priorities are reviewed. The body that decides and its rules fall under project portfolio management.
The practices the agile PMO drops, and those it keeps
Changing stance begins with requests that the office stops sending to the teams:
- the declared percentage complete, replaced by the observation of what is done;
- the detailed end-to-end schedule, demanded of teams whose content is decided at each iteration;
- the report re-entered in a format specific to the office, when the team’s tool already carries the information;
- the change request for each change in content, as long as the period’s objective and capacity are not affected;
- comparing teams with one another on their internal measures.
The rest remains. The office has a principal and a written mandate, the subjects of our articles on the role and responsibilities of the PMO and on the types of PMO. It continues to track spending, whether the budget is approved by project or by capacity. It holds risks, dependencies on what is not run in agile mode and commitments made to third parties: contracts, regulatory deadlines. It maintains common definitions and follows up the application of decisions taken.
An organisation can run projects with an imposed date and product teams at the same time. Its office then runs two regimes and states, for each object, which one applies. This split is written into the mandate, a document of the charter described on our page on setting up a PMO; the organisation of the teams falls under our page on agile at scale.
The first step is an inventory. For each heading of the report it asks for today, the office checks whether the information already appears in the tools of an agile team within its scope. The headings found there no longer need to be requested. Those that are missing (spending, external dependencies, risks) designate what the office continues to hold itself.