MYT Governance Lab · Portfolio Control Tower

Recovering an At-Risk Program

— of
— projects have forecast finishes later than their original Baseline 1 commitments.
The largest slip is —
(—), the priced projects are earning
— of planned work (SPI), and each dollar spent buys
— dollars of planned work (CPI).

Archived checkpoint · 9 November 2026. This preserves the earlier state of MYT’s Portfolio Control Tower lab for comparison; it is not the latest checkpoint. This page uses embedded simulated data and does not refresh automatically. Earlier history is reconstructed; MYT publishes reviewed updates manually at meaningful stages, typically every two to three weeks depending on program progress. This lab remains in development.

Simulated lab data: fictional program, illustrative costs
Snapshot as of —
Planner Premium · Dataverse · Power Automate · Claude
Largest slip vs Baseline 1

—

—
Schedule performance (SPI)

—

earned ÷ planned value, 1.00 is on plan
Cost performance (CPI)

—

cumulative, includes the overrun inherited at takeover
Open risks and issues

—

— a week in illustrative cost of delay

The story so far

A PMO lead inherits four at-risk projects and has to decide, with data, what to do first. Each Monday a scheduled flow records a snapshot of every plan; everything before Nov 2 is reconstructed history.

  1. Takeover. All four projects are Red. Regional is five weeks past its Baseline 1 finish with 11 tasks overdue, all traced to one stalled task: vendor master data that failed validation in August.

  2. Decision CR-001. The delay is priced three ways before choosing a fix. The sponsor approves re-baselining Regional with containment (keep legacy invoicing live) over crashing or doing nothing. Baseline 1 is kept as the original commitment; Baseline 2 becomes the working plan.

  3. The watermelon. The first automatic snapshot turns Regional Green: the re-plan moved its overdue tasks into the future, yet it is already behind its new baseline. Green outside, red inside. The health rule is changed the same day to weigh progress and record a reason.

  4. Two CPIs. Actual costs are added, with an opening balance inherited from the finance ledger. Cumulative CPI keeps the inherited overrun visible; CPI since takeover will show whether it is still happening.

Forecast finish drift against Baseline 1

Weeks between each project’s forecast finish and its original Baseline 1 finish, week by week. Drift is always measured against Baseline 1, so a re-baseline never hides slip. The dashed line is Regional’s approved Baseline 2: from the takeover on, holding at or below it is recovery.

Schedule performance, week by week

Actual progress divided by planned progress against the baseline in force that week; 1.0 is on plan. A re-baseline restarts the plan, so Regional’s line breaks at the reset (ring) instead of jumping, which would look like a recovery that never happened.

Where each project stands

Latest weekly snapshot. Health weighs slip, overdue critical tasks and, from Nov 16, progress against plan. SPI here compares percent complete; the cost table below weights the same work by dollars, so the two can differ.

Project Health Planned Actual SPI

Two baselines, side by side

Baseline 1 is the accountability record. Where a change request approved a re-baseline, the current baseline is shown beside it.

Project Baseline 1 Current baseline Forecast vs Baseline 1

Earned value and cost performance

Priced from a lab rate card (illustrative). Earned value is the budgeted cost of the work actually done; SPI = earned ÷ planned value; CPI = earned value ÷ actual cost. Forecast at completion = spent so far + remaining work ÷ CPI. Site C has no hour estimates yet, so it is not priced.

Project Budget at completion Planned value Earned value Actual cost SPI CPI Forecast at completion

Risks, issues and decisions

Escalated items first, closed last. Weekly cost of delay is an illustrative assumption recorded with each item.

Type Project Item Status Weekly cost Decision
About this lab

This is a working lab by Manage Your Tech, run as a live program over several months. The plans are fictional and every figure is simulated or illustrative; no client data is used. Plans live in Microsoft Planner Premium, a scheduled Power Automate flow writes a weekly snapshot to Dataverse, and the risk register, rate card, baselines and actual costs are Dataverse tables.

Claude reads the data, drafts the weekly team updates, change requests and analysis, and builds these views. Every plan change, cost entry and decision is approved and applied by the PMO lead. This page is a frozen copy of the live Control Tower, refreshed at checkpoints.

Manage Your Tech · Governance Lab · Simulated data, snapshot refreshed at checkpoints · manageyourtech.ca