A well-structured PMO is the engine behind every successful programme. Vetrexa steers complex multi-vendor projects in banking, insurance, automotive and industry – disciplined delivery, transparent reporting and reliable budget control. Whether agile (Scrum, Kanban), scaled (SAFe 6.0, LeSS) or classic (PRINCE2, PMBOK), we bring your initiatives safely into steady-state operations. As an external Project Management Office we take on portfolio steering, Program Increment planning, stakeholder management and the consolidation of your resource and budget reporting across every delivery stream. Our PMO leads chair Steering Boards, orchestrate provider contract chains with rigorous SLA cascading and make sure that regulatory requirements – from MaRisk and BAIT to DORA – are translated into verifiable delivery artefacts. Programmes therefore not only close on time but also deliver measurable business value and a clean handover into steady-state operations.
Overview
Why PMO?
Projects rarely fail because of technology – they fail because of unclear roles, weak steering and insufficient transparency.
A professionally established Project Management Office consolidates governance, resource and budget steering in one place. It creates clear decision paths, consistent delivery standards and reliable reporting to C-level. In regulated industries such as banking, insurance and automotive, a capable PMO is a precondition for meeting audit readiness, MaRisk obligations and milestone commitments consistently.
Vetrexa acts as your external PMO lead and takes on individual programme and project management assignments. We structure complex multi-vendor programmes, coordinate internal and external delivery teams and make sure that strategic direction is translated into actionable sprints, releases and deliverables – without overloading your line organisation.
Not every PMO is the same. In practice – drawing on the P3M3 maturity model (Portfolio, Programme & Project Management Maturity Model) – we differentiate five maturity levels from "awareness" through to "optimised" and calibrate governance model, tooling depth and reporting cadence accordingly. Three archetypes have established themselves in terms of PMO orientation: the Delivery PMO (sometimes called project PMO) steers a single programme tightly along scope, schedule and cost and is typical of transformation or migration initiatives with a clear end state. The Enterprise PMO (EPMO), by contrast, owns the organisation's entire project portfolio, evolves standards, skills and tool landscape and provides C-level with consolidated portfolio views. As a third type, the Value Delivery Office has emerged, integrating SAFe portfolios, OKR cycles and product governance. In reality Vetrexa PMOs almost always operate as a hybrid model: a lean, dedicated Delivery PMO per major programme, connected to an EPMO cockpit that consolidates cross-programme KPIs, resource utilisation and risk aggregation – producing portfolio transparency without bureaucratic overhead.
What we deliver for you
Services at a glance.
Six core building blocks with which we make your PMO operational and bring your programmes safely to their objectives.
01
PMO Setup & Project Structuring
Setting up the PMO including governance model, RACI matrix, delivery standards, templates and approval processes – seamlessly integrated with your existing project and line organisation. Together we define role profiles, escalation paths and decision-making bodies and anchor them in a living PMO handbook. The result is an operational setup that delivers reliable steering data from day one.
RAID log (Risks, Assumptions, Issues, Dependencies) with owner tracking
Change Board process, baseline management and scope guardrails
02
Agile Coaching & Events
Coaching Scrum, SAFe and Kanban teams. We facilitate dailies, refinements, reviews and retros and establish a delivery cadence that produces measurable results. For scaled environments we lead Program Increment planning, Scrum of Scrums and the build-up of Communities of Practice across several Agile Release Trains. The maturity of your teams is made transparent through predictability KPIs and PI Objectives achievement.
Burn-up and burn-down charts and velocity trending per team
PI planning preparation, ART sync and Inspect & Adapt workshops
03
Budget Controlling & Resource Planning
Forecast, actuals tracking, change and risk buffers, resource utilisation and skill planning – prepared transparently for steering committees and C-level. We rely on robust Earned Value Management metrics (SPI, CPI, EAC) and provide early warning signals well before budget or schedule reserves are exhausted. For investment decisions we prepare scenario-based business cases and break-even analyses.
Earned Value Management with SPI/CPI trending and Estimate-at-Completion
Rolling forecast, capacity simulation and multi-project resource heatmap
04
Stakeholder & Provider Management
Structured stakeholder mapping, communication plan, steering formats and operational steering of internal departments and external providers with clear escalation paths. We establish vendor scorecards, contract KPIs and regular business reviews so that performance, quality and contractual compliance of every provider become quantifiable. Conflicts are decided early, factually and on a solid data base.
RACI matrix, stakeholder heatmap and tailored communication cascade
Vendor governance with Monthly Business Review and contract-KPI cockpit
05
Documentation & Reporting
A consolidated programme view across Confluence, Jira and SharePoint. Traffic-light reports, KPI dashboards in Power BI, milestone tracking and audit-proof archiving of every decision document. We build reporting so that it is generated once, automatically, and then reused at different levels of aggregation – from team level through to board level. Auditors and regulators receive reproducible evidence chains without manual rework.
Automated reporting via Jira queries, Confluence reporting macros and Power BI
Audit trails, versioning and BAIT / MaRisk-compliant document archives
06
Programme Management for Large Infrastructure Projects
Steering of multi-year infrastructure and transformation programmes with hundreds of contributors – data centre migrations, cloud transitions, legacy replacement, SAFe programmes. We structure the initiative into clearly scoped value streams and Solution Trains, orchestrate dependencies and represent the programme in Steering Boards and meetings with regulators. Transition to operations is treated as a dedicated workstream from the outset.
Program Increment planning, ART synchronisation and Solution-Level coordination
Cutover planning, hypercare concept and knowledge transfer to the line organisation
Our Approach
Four steps into delivery.
A proven sequence – from PMO setup to a clean transition into steady-state operations of your organisation.
Step 01
Setup
Establish governance model, tooling, templates and PMO roles. Define the baseline for scope, budget, resources and risk.
Step 02
Delivery
Steer teams operationally: backlog, sprints, releases, multi-vendor coordination. Impediments are resolved without delay.
Step 03
Reporting
Consolidated status, KPI and financial reporting to steering committee and C-level. Early warning indicators for scope and budget deviations.
Step 04
Handover
Clean transition into steady-state operations: documentation, knowledge transfer and handover of responsibility to line and operations teams.
Methods in detail
Frameworks we command with confidence.
No framework purism – deliberate selection. Depending on the context we deliver agile, scaled or classic delivery, and combine them in hybrid models.
A
Scrum & Kanban (scaling)
For single teams we establish clean Scrum with defined sprint goals, Definition of Ready / Done and a well-groomed backlog. Kanban is used where interruptions and ticket volumes dominate – typically in operations or compliance contexts. For scaling we introduce Scrum of Scrums, Nexus or LeSS and synchronise several teams around shared sprint objectives. Steering instruments include WIP limits, cumulative flow diagrams and team velocity trends.
B
SAFe 6.0 (portfolio level, value streams)
We apply SAFe 6.0 wherever several Agile Release Trains contribute to a shared target picture in parallel. We chair Program Increment planning for more than one hundred participants, facilitate PO sync and ART sync and work with Lean Portfolio Management based on value streams and epic hypotheses. The connection to OKR cycles and investment decisions is made through a portfolio Kanban and Weighted-Shortest-Job-First prioritisation. Continuous Delivery Pipeline and System Demo round out the picture.
C
PRINCE2 & PMBOK (waterfall / hybrid)
In heavily regulated or contractually fixed initiatives, classic project management along PRINCE2 or PMBOK remains the method of choice. We structure the project by processes and themes (business case, risk, quality, change), establish a milestone plan with clear tollgates and engage the steering committee on a pre-defined cadence. In hybrid setups we combine a classic milestone and contract layer with agile delivery teams at work package level – so that regulatory evidence and delivery speed are both maintained.
Project Experience
Selected reference projects.
A selection of programmes we have led or steered as PMO – presented in anonymised form.
PMO lead for the replacement of Papyrus/DOPiX with Quadient Inspire. Steering of agile delivery teams, budget control and reporting to the steering committee through to go-live and hypercare.
Quadient Inspire · Jira/XRay · Confluence · Scrum · Kanban · Power BI
Automotive
Data Centre Migration – Programme Management
Programme lead for the migration of critical IT infrastructure. Coordination of internal departments and external providers, risk and integration test management, classic milestone planning.
Leadership of a multi-train SAFe programme for IAM transformation. PI planning, Scrum of Scrums, multi-vendor coordination and audit-proof reporting in a MaRisk context.
SAFe · SailPoint IIQ · Jira/XRay · Confluence · Power BI · MaRisk
Insurance
DORA Programme PMO
Set-up and leadership of a regulatory DORA programme PMO with 17 parallel workstreams across group and subsidiary entities. Responsibility for the Steering Board, consolidated ICT third-party contract review, RAID log and delivery cadence up to BaFin evidence submission. Consolidated reporting to Board and Supervisory Board with per-stream traffic-light logic and an aggregated risk view.
DORA · MaRisk · BAIT · Jira · Confluence · Power BI · MS Project
Public Sector
Digitalisation Programme PMO
PMO lead for a multi-year digitalisation programme of a public-sector organisation with four specialist procedures and three external systems integrators. Set-up of governance, procurement alignment (EVB-IT) and a robust delivery structure along V-Model XT with agile sprint cells. Political stakeholders are engaged through a dedicated Steering Committee cadence and regular progress reports to ministries.
Programme management for the migration of a heterogeneous SAP landscape to S/4HANA in a large retail group. Steering of fit-gap analysis, data migration, cutover planning, hypercare and integration of Finance, Logistics and POS connectivity. Multi-vendor coordination (systems integrator, hyperscaler, test provider) under a single programme board with clear contract-KPI structure.
SAP S/4HANA · SAP Activate · MS Project · Jira · Confluence · Power BI
Toolset & Frameworks
What we work with.
Proven tools and frameworks for reliable delivery, transparent steering and regulatory fit.
Jira / Jira XRay
Confluence
MS Project
SharePoint
Power BI
Scrum
SAFe
Kanban
PMI / PRINCE2
ITIL
MaRisk
Related Competences
Natural complements.
Topics that clients regularly combine with our PMO offering.
Multi-vendor programme management — best practices
Large programmes are almost always delivered by several providers. The difference between chaos and delivery comes down to the rigour of governance and the quality of contract KPIs.
Vendor governance. The foundation of every multi-vendor programme is robust vendor governance: clearly cut responsibilities between customer, prime vendor and sub-contractors, a shared RACI matrix at work-package level and documented decision rights. Vetrexa sets up a central Vendor Management Office with monthly business reviews, vendor scorecards and a structured onboarding / offboarding process. This makes deliverables comparable, surfaces conflicts between providers early and produces auditable evidence of any breach of contract.
Integration testing. When several providers deliver components, integration testing decides go-live versus no-go-live. We take ownership of an end-to-end test plan with a shared test environment, clear entry and exit criteria per phase and a consolidated defect backlog in Jira / XRay across every provider. The central steering mechanism is an Integration Control Board that decides on daily test releases, blockers and cross-vendor defects – with clear owner and time-box rules per ticket.
Contract KPIs. Contracts must be operationalisable. We work with a contract-KPI cockpit that translates providers' contractual obligations (velocity, reliability, defect density, response times) into monthly measurable target values. Malus and bonus clauses are not only fixed in contracts but measured, documented and discussed regularly in business reviews. Negotiations become factual and contract decisions data-driven – not political.
SLA cascading. A frequently underestimated success factor is clean SLA cascading. End-user SLAs must be translated consistently into OLAs between internal operations units and back-to-back SLAs with sub-providers. Vetrexa models this cascade explicitly, reviews recourse claims and ensures that regulatory requirements (BAIT, DORA, ICT third-party risk) are anchored contractually end-to-end. The result is a vendor landscape that not only delivers but delivers in an auditable way.
FAQ
Frequently asked questions.
The questions we hear most often in our first conversations.
Do you work agile or classic?+
Both. Our project managers are equally comfortable with classic waterfall approaches (PMI, PRINCE2) and with agile frameworks (Scrum, SAFe, Kanban). The chosen method is tailored to the project objective, the maturity of the organisation and the regulatory context – frequently as a hybrid model that combines a classic milestone plan with agile delivery teams.
How do you manage multi-vendor programmes?+
We establish a central PMO structure with clearly defined roles, a RACI matrix, shared delivery governance and consolidated reporting across every provider involved. Our steering instruments include cross-vendor Jira programme boards, vendor scorecards, escalation paths and a weekly sync cadence with the lead architects of all providers.
Which certifications do your PMs hold?+
Our project managers hold, amongst others, PSM I (Professional Scrum Master), PSPO I (Product Owner), SAFe certifications, PRINCE2, PMI foundations and ITIL Foundation. Many colleagues also bring specialist certifications on Quadient Inspire, SailPoint IIQ or COBIT / NIST frameworks.
How is C-level reporting structured?+
C-level reporting is condensed, decision-oriented and KPI-driven. We provide monthly steering committee packs with traffic-light indicators for scope, budget, resources and risk, complemented by live dashboards in Power BI. For regulated environments we integrate MaRisk-compliant evidence, audit trails and milestone tracking.
When Scrum, when SAFe, when waterfall?+
The choice depends on scope, team count, regulatory context and requirements stability. Scrum suits single, product-oriented teams with high change dynamics. SAFe is deployed when 50 to 125 or more people work across several Agile Release Trains and portfolio alignment, Program Increment planning and value streams demand a synchronised approach. Waterfall or PRINCE2 / PMBOK remains the method of choice where scope, compliance and milestone commitments are fixed – for instance in data centre migrations or regulatory delivery programmes with BaFin or EBA context. In practice we frequently combine all three approaches in a hybrid delivery model.
How do you measure PMO effectiveness?+
PMO effectiveness is measured through hard and soft KPIs: the Schedule Performance Index (SPI), Cost Performance Index (CPI) and Earned Value show delivery progress against baseline. We complement these with forecast accuracy, risk burn-down, change request ratio, defect escape rate and time-to-decision at steering level. For agile trains we add predictability measures, PI Objectives achievement and team happiness. As an external reference we use P3M3 (Portfolio, Programme & Project Management Maturity Model) to prove maturity progress over 12 to 18 months in quantifiable terms.
How do you handle failed sprints?+
A missed sprint goal is not an exception; it is part of the craft. We work through the failure in an extended retrospective, classify root causes (scope creep, technical debt, dependencies, unclear acceptance criteria) and derive concrete impediment actions. Incomplete stories return to refinement, are re-sliced or planned as a spike. At programme level the velocity dip is captured in the RAID log and – if the miss repeats – team composition, WIP limits or the Definition of Ready are reviewed.
Your programme. Steered with precision.
Talk to us about PMO setup, programme management or an agile delivery that produces measurable results.