When teams go agile, the project management office (PMO) is often the first group to feel the chill. Templates, weekly status reports, and compliance checks suddenly look like friction to people who want to ship. Some PMOs respond by tightening the rules. We think the better response is to change what the PMO is for.
Why the old model feels wrong
A traditional PMO works by standardizing. It asks every project for the same plan, the same report, and the same sign-offs, so leadership can compare them. That served a purpose when projects looked alike. An agile team shows progress through working software every few weeks, so a weekly document describing percent complete adds little. Teams see the report as extra work, and the PMO sees teams as undisciplined. Both are partly right.
From policing to enabling
Consider a PMO at a mid-sized insurer, with 15 teams moving to Scrum. Instead of enforcing the old templates, it could take on four jobs.
Lighter reporting. Replace long status reports with information teams already produce: the release plan, the sprint results, and a short list of risks and impediments. Leaders can read a team board or attend a sprint review. The PMO’s job is to combine this into one view, not to ask teams to write it twice.
Coaching. PMO staff often know the organization’s politics, vendors, and budgets better than anyone. Pair that knowledge with agile training, and they become coaches who help new teams get started and help managers understand what they’re seeing.
Removing impediments. Teams regularly hit obstacles that they can’t fix alone: a server request stuck in a queue, a vendor contract, a policy that blocks a release. A PMO with organizational reach can clear these. Track how long impediments stay open and report that to leadership.
Managing cross-team dependencies. When 15 teams build parts of the same product, someone has to see the connections. The PMO can host regular planning sessions among teams, keep a visible dependency map, and flag conflicts early.
What to keep
Don’t throw out everything. Compliance requirements, budget tracking, and risk reporting still matter, and teams shouldn’t have to carry them alone. The goal is to meet those needs with less paperwork, not to abandon them.
A way to begin
Ask the teams. Hold a short session and have them list which PMO requirements help them and which only cost them time. You’ll likely find that a few items are the source of most complaints. Fix those first, and tell teams what you changed.
If your PMO is facing this shift, talk to us about how we’ve seen others approach it.