Not a project with a delivery date. The program is the standing thing the projects were delivered against, and it ran for fifteen years.
It covered strategy, architecture assessments and multi-year capability roadmaps for a shared platform serving multiple independently governed agencies, and it drove application rationalization, platform consolidation and technology lifecycle planning across a portfolio nobody had assembled deliberately — three hundred-odd applications accumulated over decades by organizations with their own budgets and their own reasons.
Four viewpoints had to stay balanced: business, information, technical and solution. Programs that collapse to the technical viewpoint produce elegant patterns nobody adopts; programs that collapse to the business viewpoint produce roadmaps with no engineering underneath them.
The governing principles were the deliverable that mattered — the rules that guided solution decisions when no architect was in the room. Patterns were chosen to minimize total cost of ownership rather than to be interesting, because in a government estate the cost of a pattern is paid every year by somebody who did not choose it.
Outcome
Repeatable technology patterns the engineering and operations groups designed and deployed against, chosen to minimize total cost of ownership rather than to be interesting.