A Practical Guide to Scheduling Delivery Capability: How Long Does PMO Setup Take?

Paul Thomas • July 16, 2026

Share this article

This is a subtitle for your new post

"How long will this take?" is usually the second question after "how much." It deserves the same specificity. This guide walks through the realistic 3–6 month timeline for PMO Setup & Maturity, phase by phase, so you know what to expect before you commit.


Step 1 (Weeks 1–2): Assessment


This is the free part. Two weeks of senior practitioner time spent understanding what's actually happening across your projects today. No PMO gets designed before we know what it's replacing or reinforcing.


Step 2 (Weeks 3–6): Design


A right-sized PMO for a 50-person engineering org looks nothing like one for a 400-person operations business. This phase builds the governance model, reporting cadence, and escalation paths specific to your organisation, not a template pulled from the last client.


Step 3 (Months 2–4): Pilot and calibration


The PMO runs live on a subset of your portfolio before it's rolled out fully. This is where most off-the-shelf PMOs fail, they skip the pilot and discover the gaps after full rollout, when they're expensive to fix. We calibrate here instead.


Step 4 (Months 4–6): Embed and hand over


Full rollout across your portfolio, with the PMO run by your own people before we step back. We build a delivery capability that lasts; the goal was never to make you dependent on us.


Step 5: Check what could slow you down


Three things reliably stretch a PMO build past its estimate. Run this check before you start:

  • Stakeholder alignment speed. If department heads can't agree on what "on track" means within the first two weeks, design stalls waiting for consensus.
  • Data availability. A PMO's reporting is only as good as the project data feeding it. If that data doesn't exist yet, week three becomes an unbudgeted data-cleanup exercise.
  • Existing tooling debt. Migrating years of scattered spreadsheets and disconnected trackers into one reporting model takes longer than building the model itself.


None of these are reasons to delay starting. There are reasons to know about them at week one instead of month four.


Step 6: Know where the profession is heading


This shift toward more rigorous PMO design is happening industry-wide, not just at AgileMinds. APM's 2025 survey found uptake of its Project Management Qualification has risen 50% in two years, and its entry-level Project Fundamentals Qualification has risen 38%, per the APM Salary Survey 2025 — UK organisations are visibly investing in more credentialed project capability. A PMO built on a template from five years ago is already behind where the profession itself has moved. Your design phase should reflect that shift, not just your organisation's own history.

Want the real number for your organisation, not the range? 


Where to start


The honest range is three to six months, and the honest way to find your own number inside that range is a proper assessment, not a guess dressed up as a quote.


Agileminds builds PMOs designed around the organisation they serve, not a template. If you want the real number for yours, we should talk.


Recent Posts

By Paul Thomas July 15, 2026
Most consultancies won't answer the cost question directly. Ask, and you'll typically get "it depends" and a form to fill in. It does depend, but that's not an excuse to be vague about what it depends on. If you're a COO trying to build a business case for the board, three variables actually set the price, and none of them are secret. What actually drives the number Programme size is the first. A single at-risk workstream costs less to stabilise than a portfolio of twelve, scope drives everything downstream. A workstream with one team, one sponsor, and one clear deliverable is a contained diagnostic exercise. A twelve-workstream portfolio with overlapping dependencies and multiple sponsors is a different order of problem entirely, because stabilising one workstream in isolation without understanding its dependencies on the other eleven risks solving the visible symptom while the underlying cause resurfaces somewhere else three months later. Embed duration is the second: recovery engagements typically run three to six weeks, and a straightforward stabilisation, credible plan, honest reporting, a functioning team, costs less than a six-week turnaround with practitioners embedded across multiple workstreams. The difference between the two isn't really about calendar time so much as coverage, how many people need to be physically present, in the room, for how many of those weeks, before the organisation can run the plan on its own. Seniority is the third, and the one most likely to be quietly reduced to save money. We only deploy practitioners with 15+ years of experience, never graduates running a template, and that's a deliberate cost floor, it's also why the fix tends to hold. It's worth being honest about why seniority costs more and is still worth it: a junior consultant working from a template can produce a plan that looks credible on paper. A senior practitioner who has seen a dozen versions of this specific failure pattern before knows which parts of that plan won't survive contact with the actual organisation, and can say so in week one rather than week five. What that seniority actually costs, in public numbers You don't have to take a consultancy's word for what senior delivery talent costs in the UK market. The Association for Project Management's 2025 Salary and Market Trends Survey, the UK's largest annual study of the profession, puts the average project management salary at £52,500, up 10% on 2023, with practitioners in consultancy and energy/utilities sectors averaging £62,500, per the APM Salary Survey 2025 . Embedded recovery work commands more than that average because it's compressed: fifteen-plus years of pattern recognition delivered on a timeline measured in weeks, not spread across a year. There's a useful way to think about what's actually being purchased here. A permanent hire's salary buys a year of their time, spread across whatever the organisation needs that year. A recovery engagement's cost buys weeks of concentrated attention on one specific problem, from someone whose entire value is having seen that problem before. The hourly economics look expensive next to a permanent salary until the comparison is corrected for what's actually being delivered in that window. The cost that never makes it onto an invoice Every cost conversation focuses on what recovery costs. The number that's harder to see, and usually larger, is the cost of inaction. A project drifting for another quarter doesn't just slip its date, it compounds in several distinct ways. The team burns out chasing an unrealistic plan, because nobody has told them the plan is unrealistic, so they keep trying to hit dates that were never achievable in the first place. The best people quietly start looking elsewhere, because skilled practitioners can generally tell when a programme has lost its way faster than the sponsors funding it can, and they don't wait around to find out how it ends. Stakeholder trust erodes in a way that outlasts the project itself, a sponsor burned once by an over-promised, under-delivered programme brings that scepticism into the next funding conversation, and the next, long after the specific project is closed. And the eventual fix costs more because the drift has to be unwound before recovery can even begin, every extra week of a bad plan being followed is a week of decisions made on false assumptions that now need to be found and corrected. By the time a board asks how much it will cost to fix, the more useful question is how much it has already cost to wait. Why nobody publishes a rate card A three-week reporting fix and a six-week multi-team turnaround are different projects with different costs, and any headline number would be wrong for most people who read it. That's not evasion. It's the same reason a surgeon doesn't quote a price before the scan — not because the price is a secret, but because quoting it before the diagnosis would mean quoting the wrong number to almost everyone who asked. Where to start Cost climbs with the number of embedded practitioners, the complexity of stakeholder alignment, and how far a programme has already drifted before anyone calls for help. It does not climb because of methodology, tooling, or brand name. Agile Minds gives every prospective client a free, two-week assessment before any number gets discussed. If you need a figure you can actually take to the board, we should talk .
Blue infographic chart with numbered hexagons and a pencil on a desk
By Paul Thomas July 14, 2026
Not every project needs the same delivery model. This step-by-step guide shows you how to build the right one for yours, then offers a free assessment.
Jaguar and Land Rover logos on a gray building facade
By Paul Thomas June 1, 2026
How AgileMinds built JLR a working agile framework through a real product, not a workshop. A 16-week app and guilds that kept it alive after we left.
Halfords storefront with glass entrance, orange logo, and parked bicycles outside
By Paul Thomas June 1, 2026
How AgileMinds delivered Halfords' unified ecommerce platform on Salesforce Commerce Cloud. Two brands, one basket, over 100 integrations, nine months.
Three people in red helmets and jackets stand outdoors at dusk, looking serious.
By Bernadine Dela Cruz May 29, 2026
How AgileMinds helped E.ON take a virtual power station from proof of concept to commercialised, award-winning solution in six months.
Stressed person at desk with laptop, head in hand, reviewing charts in a bright office
May 24, 2026
Uncover the hidden costs of project team burnout, like knowledge loss & attrition. Contact us for strategies to mitigate these issues.
Team collaborating around a laptop with papers, notebooks, coffee, and a smartphone on a desk.
By Paul Thomas May 4, 2026
Most failing projects send warning signs months before the board notices. Here’s how to spot them, and how to recover before it’s too late. Free assessment.
Hands holding a tablet with a to-do checklist and red markings on a desk, lit by blue and warm light
By Paul Thomas May 4, 2026
More than half of PMOs are shut down within two years. Here are the five reasons mid-market PMOs fail, and what to do differently. Free PMO assessment.
Colleagues in a meeting, leaning over documents and pointing at a chart on a conference table.
By Paul Thomas May 4, 2026
Explore why 70% of digital transformations fail due to middle management issues. Contact us for tailored solutions today!