Bootminds PMO & Programme Governance Packbootminds.pmo v1.0.0
Programme governance scaffolding for transformation programmes (GCC, ERP, M&A, etc.). Covers programme charter, Steerco design, RACI baselines, reporting cadence, and programme-level gate definitions. Pack-wide maturity rubric covering programme-governance maturity across five canonical levels. Ships ~30 question templates, ~10 decision templates, 6 gate templates governing Discovery exit through Stabilisation exit, and 5 AI interpretation specs for Steerco draft, programme health, gate readiness, RACI completeness, and risk synthesis.
Counts
- Workstreams
- 5
- Questions
- 30
- Decisions
- 10
- Gates
- 6
Required runtime capabilities
Provenance
- Registry hash
69cac88368a9…- Raw pack
- /api/packs/bootminds.pmo
Workstreams
P0 Programme Charter
Programme scope, objectives, success criteria, sponsor, and governance forum. The foundational decisions about what this transformation is and is not.
View workstream detail →P0 Governance Forums
Steerco design (members, cadence, decision authority, escalation paths) and Working Group structure. Where decisions get made.
View workstream detail →P1 Programme RACI Baselines
Programme-level RACI: who decides what at the programme level (resourcing, scope changes, risk acceptance). Distinct from object-level RACI on individual decisions.
View workstream detail →P1 Reporting Cadence
Steerco pack format, weekly status, monthly board update, KPI definitions. How the programme communicates progress upward and outward.
View workstream detail →P0 Gate Management
Programme gate definitions (Discovery exit, Design exit, Build entry, Cutover ready, Go-live, Stabilisation exit), exit criteria, and approval chains. Governs phase progression of the transformation as a whole.
View workstream detail →Pack-wide decisions
10 decision templates ship with this pack.
| id | title | scope | priority | options | evidence questions |
|---|---|---|---|---|---|
| pmo.dec.charter_approval | Approve programme charter (objectives, scope, sponsor, budget envelope) | GCC | P0 | 3 | 7 |
| pmo.dec.steerco_constitution | Constitute the Steering Committee (members, cadence, decision authority) | GCC | P0 | 3 | 6 |
| pmo.dec.raci_baseline_lock | Lock programme-level RACI baseline (resourcing, scope, risk, vendors) | GCC | P0 | 2 | 4 |
| pmo.dec.reporting_cadence_lock | Lock reporting cadence (weekly status, Steerco pack, board update, KPI definitions) | GCC | P1 | 3 | 5 |
| pmo.dec.gate_definitions_lock | Lock programme gate definitions (which gates, in what order, with what criteria) | GCC | P0 | 3 | 4 |
| pmo.dec.escalation_path_lock | Lock escalation path above Steerco | GCC | P1 | 2 | 1 |
| pmo.dec.decision_logging_practice_lock | Lock decision-logging practice (where, by whom, format) | GCC | P1 | 2 | 1 |
| pmo.dec.raid_owner_assignment | Assign programme RAID register owner | GCC | P2 | 2 | 1 |
| pmo.dec.stakeholder_engagement_plan_lock | Lock stakeholder engagement plan | GCC | P2 | 2 | 1 |
| pmo.dec.benefits_realisation_lock | Lock benefits realisation model | GCC | P1 | 2 | 2 |
Gates
| id | name | description |
|---|---|---|
| pmo.gate.discovery_exit | Discovery exit gate | End-of-discovery gate. The programme exits Discovery with a populated decision graph, a maturity baseline, and a written charter. Failure to pass means Discovery continues; the cost of a soft Discovery exit is paid in Design. |
| pmo.gate.design_exit | Design exit gate | End-of-Design gate. The programme exits Design with design-level decisions locked for every workstream the build will deliver. Failure to pass means Build is at risk of restarts. |
| pmo.gate.build_entry | Build entry gate | Entry-to-Build gate. The programme enters Build with team, funding, and vendors in place. Failure to pass means Build does not start; deferring is preferable to entering Build with a known gap. |
| pmo.gate.cutover_ready | Cutover ready gate | Pre-cutover Go/No-Go. The programme certifies that the cutover for a wave is ready to execute: dual-run successful, runbooks signed off, comms sent, rollback plan tested. Failure to pass means cutover is deferred. |
| pmo.gate.go_live | Go-live gate | The actual cutover Go/No-Go. Last formal moment to abort. Failure to pass means rollback or defer. Decision-maker is the gate chair (Programme Lead); approver is the sponsor; reviewers are workstream leads who certify their own areas. |
| pmo.gate.stabilisation_exit | Stabilisation exit gate | End-of-stabilisation gate. The programme exits stabilisation with the new state operating at defined baselines and the transition team standing down. Failure to pass means stabilisation continues. |