Glossary

Post-go-live governance

The set of practices that preserve architectural coherence after go-live: reviewing the catalog and capability map, re-approving processes when they change, and evolving the data model by design.

The set of practices that preserve architectural coherence after go-live: reviewing the catalog and capability map, re-approving processes when they change, and evolving the data model by design. Go-live does not close the cycle: it starts it.

It is the phase projects treat as finished and where architecture decays. The team disbands, the adjustments continue, and two years later the repository describes a process that is no longer the one running.

Related terms

Architecture contract

The instrument governing implementation and deployment to ensure conformance with the defined architecture.

Conformance checking

The quantification of the proportion of real cases that respect the approved design, its rules and its controls.

Evidence-based continuous improvement

The practice of redesigning from operational data (timings, backlog, rework, exceptions, data quality, satisfaction) rather than opinion or perceived efficiency.

Versioning and reapproval

The regime by which every material change to a process, rule, data item, service level, offering or indicator is versioned and re-approved.