Programme delivery artifacts as code. Working generators and battle-tested templates from 20+ years of UK financial services delivery, because programmes deserve better than inherited spreadsheets with someone else's broken macros.
| Tool | What it produces | Run it |
|---|---|---|
raid_generator.py |
A complete RAID log workbook: four registers with dropdown validation, auto-calculated risk scores (probability × impact), RAG conditional formatting, and a summary dashboard that counts what matters | python generators/raid_generator.py my_raid.xlsx |
A pre-built example is in sample-output/ if you just want the workbook.
Requires: Python 3.10+, pip install openpyxl
| Template | What it enforces |
|---|---|
| Cutover runbook | Every step owned, verified, and reversible. Binary go/no-go criteria. A named rollback owner, because rollback-by-committee is how windows get missed |
| Weekly status report | Decisions above achievements. RAG with teeth: six weeks of Amber with the same commentary is Red wearing Amber's clothes |
Three opinions are baked into everything here:
- Artifacts should be generated, not inherited. A RAID log built by a script is consistent on every programme, version-controlled, and improvable by pull request. The one inherited from the last PM is none of those things.
- Templates should enforce discipline, not just structure. Empty boxes don't make programmes honest. Each template embeds the rules that make the artifact worth filling in: binary criteria, named owners, consequence-of-delay columns.
- The exec cut and the working record are different documents. Summary sheets and top-3 tables exist because nobody senior reads row 147 of a register, and pretending they do is how risks hide in plain sight.
- Programme plan-on-a-page generator (pptx)
- Benefits tracking workbook
- Lessons-learned database with structured capture format
- Stakeholder/RACI matrix generator
Suggestions and PRs welcome via issues.
MIT. Use it on your programme, today, no attribution needed.