Paul Miles — CLM Glossary Programme Tracker (Burndown & Flow, Excel)

Tag: S-2026-06-27-paul-clm-glossary-programme-tracker Type: own-writing Author(s): AI agent (Claude Opus 4.8) for Paul / Red Strata Date of source: 2026-06-27 Date ingested: 2026-06-27 Authority weight: medium — an AI-built reporting tool grounded in the squad’s existing T-03/T-06 templates; design choices confirmed by Paul, but not yet run against live programme data. Raw file: S-2026-06-27-paul-clm-glossary-programme-tracker.md

What it claims

An Excel measurement and forecasting layer for the CLM Glossary Acceleration Squad that turns the counts the Glossary Build Kit already emits — the T-03 Clustering Summary sheet and the T-06 Status Summary (9-state lifecycle: Harvested → Clustered → Drafted → In Review → Conflict—In Workshop → Ready to be approved → Approved → Published → Retired) — into the two reports requested in the project brief.

1. Flow report — a Cumulative Flow Diagram of terms by status over sprints, a current-distribution bar chart, and a flow-totals panel (total terms, clusters, recommended/Ready, approved+published, % mastered).
2. Burndown — a chart with a rising scope line (backlog grows as harvesting discovers terms), a remaining-to-master burndown, a dashed ideal glide path, and a velocity-based forecast line that projects from the last actual sprint at average velocity to zero (= forecast completion date), with a RAG status comparing forecast to plan.

Design decisions were confirmed with Paul via a multiple-choice prompt: Excel-only (Power BI offered as an optional fast-follow but not built); capture history both ways (a one-click per-sprint Snapshot Log as primary, plus a Status Reconstruction sheet backfilling cumulative Approved/Published from T-06 date columns); a combined programme view (no per-squad A/B split in v1.0); and a parameterised scope that grows with harvest so the burndown re-baselines automatically.

The workbook CLM_Glossary_Programme_Tracker.xlsx has seven sheets: Exec Summary (KPI cards + Mastered-vs-Remaining doughnut), Burndown (metrics + forecast chart), Flow (CFD), Sprint Snapshot Log (the time series, with auto Mastered/Remaining/Velocity formulas), Current Counts (input / Power Query landing block), Status Reconstruction, and Config & Guide (parameters, snapshot mapping, Power Query wiring steps, source-file links). Operating model: refresh counts into Current Counts (Power Query refresh-on-open or paste), append one Snapshot row per sprint, and the charts recalc. It is a macro-free .xlsx for a regulated setting; charts use NA() for future/forecast rows (Excel’s recommended gap method), hidden via conditional formatting, with zero #REF!/#DIV/0!/#VALUE!/#NAME? errors.

A separate demo (Programme Tracker Demo/CLM_Glossary_Programme_Tracker_DEMO.xlsx) is fully populated with 8 sprints of illustrative mock data (scope 60→212, mastered 6→185, ~87% mastered, forecast one week ahead of plan, RAG GREEN) so the charts and forecast render for stakeholder demos — all synthetic.

All files saved to _ClaudeWorkspace/09 Taxonomy Tool/, with an Approach & Work Breakdown record.

Notable quotes

“A burn down chart that clearly displays the increased backlog across the process, and the burn down rate with forecast time to master all terms.” — the project brief (as stated by Paul).

What’s speculative vs. asserted

• Asserted (grounded): the data feeds (read directly from the squad’s T-03 Summary and T-06 Status Summary sheets); the lifecycle statuses and clustering match-types (from the templates’ own Lists); the forecast and RAG arithmetic (deterministic Excel formulas, recalculated and verified).
• Speculative / to-confirm: the velocity forecast is linear on average throughput and does not model SME-availability dips, scope shocks or Day-1 front-loading — indicative, re-read each sprint; the planned completion sprint (10) and RAG thresholds are placeholder parameters for Paul to set against the real Day-1 deadline; the demo data is mock, not measured.

Topics this feeds

• CLM Glossary Acceleration Squad — the tracker measures throughput and forecasts completion for this squad’s glossary mastering programme.

Open questions raised

• Confirm the planned completion sprint and RAG thresholds against the real Day-1 deadline.
• Whether to wire Power Query to the live SharePoint templates now, or run manual refresh until the squads are live.
• Whether/when to add the per-squad A/B split and/or a Power BI exec tier.