Long-running programme exhibiting the oscillation pattern — 23 RAG transitions across 81 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Upstream system / team dependency.

Programme deteriorated to Red status and remained in or near Red without sustained recovery. Detected causes: Governance / approval blockage; Operational readiness review; Testing defect / UAT failure.

Long-running programme exhibiting the oscillation pattern — 17 RAG transitions across 60 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Upstream system / team dependency.

Programme deteriorated to Red status and remained in or near Red without sustained recovery. Detected causes: Cybersecurity review.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Long-running programme exhibiting the oscillation pattern — 25 RAG transitions across 101 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Upstream system / team dependency.

Long-running programme exhibiting the oscillation pattern — 14 RAG transitions across 47 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Upstream system / team dependency.

Long-running programme exhibiting the oscillation pattern — 17 RAG transitions across 47 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Upstream system / team dependency; Operational readiness review.

Long-running programme exhibiting the oscillation pattern — 24 RAG transitions across 91 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Strategic pivot / management redirection; Governance / approval blockage.

Programme deteriorated to Red status and remained in or near Red without sustained recovery. Detected causes: Technical complexity / legacy entanglement.

Programme deteriorated to Red status and remained in or near Red without sustained recovery. Detected causes: Scope expansion / requirements change; Technical complexity / legacy entanglement.

Programme deteriorated to Red status and remained in or near Red without sustained recovery. Detected causes: Governance / approval blockage; Technical complexity / legacy entanglement.

Programme deteriorated to Red status and remained in or near Red without sustained recovery. Detected causes: Vendor dependency / third-party delay; Cybersecurity review.

Programme deteriorated to Red status and remained in or near Red without sustained recovery. Detected causes: Governance / approval blockage; Upstream system / team dependency; Operational readiness review.

Programme deteriorated to Red status and remained in or near Red without sustained recovery. Detected causes: Governance / approval blockage; Upstream system / team dependency.

Substantial programme (16 status cycles) that touched Amber on 1 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Substantial programme (21 status cycles) that touched Amber on 7 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Short-scope programme that touched Amber on 3 occasions but did not reach Red. Limited trajectory data.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Long-running programme exhibiting the oscillation pattern — 13 RAG transitions across 77 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Upstream system / team dependency.

Programme deteriorated to Red status and remained in or near Red without sustained recovery. Detected causes: Scope expansion / requirements change; Operational readiness review.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Long-running programme exhibiting the oscillation pattern — 5 RAG transitions across 27 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Upstream system / team dependency.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Short-scope programme that touched Amber on 2 occasions but did not reach Red. Limited trajectory data.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Long-running programme exhibiting the oscillation pattern — 13 RAG transitions across 50 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Operational readiness review.

Programme deteriorated to Red status and remained in or near Red without sustained recovery. Detected causes: Upstream system / team dependency; Operational readiness review; Data quality / migration defect.

Substantial programme (25 status cycles) that touched Amber on 17 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Short-scope programme that touched Amber on 3 occasions but did not reach Red. Limited trajectory data.

Short-scope programme that touched Amber on 2 occasions but did not reach Red. Limited trajectory data.

Short-scope programme that touched Amber on 1 occasions but did not reach Red. Limited trajectory data.

Long-running programme exhibiting the oscillation pattern — 12 RAG transitions across 38 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Operational readiness review.

Long-running programme exhibiting the oscillation pattern — 20 RAG transitions across 78 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Upstream system / team dependency.

Long-running programme exhibiting the oscillation pattern — 9 RAG transitions across 24 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Upstream system / team dependency.

Long-running programme exhibiting the oscillation pattern — 8 RAG transitions across 38 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Operational readiness review.

Long-running programme exhibiting the oscillation pattern — 11 RAG transitions across 55 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Upstream system / team dependency.

Long-running programme exhibiting the oscillation pattern — 7 RAG transitions across 20 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Upstream system / team dependency; Sponsor / business alignment.

Programme deteriorated to Red status and remained in or near Red without sustained recovery. Detected causes: Governance / approval blockage; Vendor dependency / third-party delay; Cutover / release execution risk.

Substantial programme (19 status cycles) that touched Amber on 5 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Substantial programme (24 status cycles) that touched Amber on 3 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Short-scope programme that touched Amber on 4 occasions but did not reach Red. Limited trajectory data.

Short-scope programme that touched Amber on 2 occasions but did not reach Red. Limited trajectory data.

Short-scope programme that touched Amber on 1 occasions but did not reach Red. Limited trajectory data.

Short-scope programme that touched Amber on 1 occasions but did not reach Red. Limited trajectory data.

Short-scope programme that touched Amber on 1 occasions but did not reach Red. Limited trajectory data.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Long-running programme exhibiting the oscillation pattern — 17 RAG transitions across 71 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Upstream system / team dependency.

Long-running programme exhibiting the oscillation pattern — 5 RAG transitions across 13 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Data quality / migration defect.

Substantial programme (37 status cycles) that touched Amber on 17 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Substantial programme (14 status cycles) that touched Amber on 5 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Short-scope programme that touched Amber on 2 occasions but did not reach Red. Limited trajectory data.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Long-running programme exhibiting the oscillation pattern — 8 RAG transitions across 50 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Strategic pivot / management redirection; Governance / approval blockage.

Programme deteriorated to Red status and remained in or near Red without sustained recovery. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Upstream system / team dependency.

Short-scope programme that touched Amber on 1 occasions but did not reach Red. Limited trajectory data.

Long-running programme exhibiting the oscillation pattern — 4 RAG transitions across 8 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Governance / approval blockage; Operational readiness review.

Substantial programme (48 status cycles) that touched Amber on 8 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Short-scope programme that touched Amber on 3 occasions but did not reach Red. Limited trajectory data.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Long-running programme exhibiting the oscillation pattern — 14 RAG transitions across 70 cycles. Repeated cycles of declared recovery followed by re-deterioration. Detected causes: Scope expansion / requirements change; Upstream system / team dependency; Operational readiness review.

Substantial programme (12 status cycles) that touched Amber on 8 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Substantial programme (52 status cycles) that touched Amber on 29 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Short-scope programme that touched Amber on 1 occasions but did not reach Red. Limited trajectory data.

Short-scope programme that touched Amber on 2 occasions but did not reach Red. Limited trajectory data.

Short-scope programme that touched Amber on 1 occasions but did not reach Red. Limited trajectory data.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Substantial programme (26 status cycles) that touched Amber on 12 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Substantial programme (15 status cycles) that touched Amber on 2 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Short-scope programme that touched Amber on 2 occasions but did not reach Red. Limited trajectory data.

Short-scope programme that touched Amber on 5 occasions but did not reach Red. Limited trajectory data.

Substantial programme (10 status cycles) that touched Amber on 1 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Substantial programme (30 status cycles) that touched Amber on 9 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Programme reported Green status across all cycles, no transitions observed. Empirically consistent with the Sustained-Green pattern — typically short-scope efforts that completed quickly and transitioned to BAU.

Substantial programme (19 status cycles) that touched Amber on 6 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Substantial programme (15 status cycles) that touched Amber on 2 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.

Substantial programme (14 status cycles) that touched Amber on 2 occasions but recovered before reaching Red. Demonstrates the Managed-Large pattern empirically associated with successful large-scale delivery.