Architecture governance
Architecture governance projects follow because it makes their work faster: standards, reference patterns and a review that decides things once.
Project type
Governance design
Practice
Enterprise architecture
Where it reached
- People
- Process
- Information
- Technology
Where they started
Projects needed architecture boundaries they would actually follow, rather than making their own platform and integration choices each time.
What we did
- Standards and patterns. Set the standards and reference patterns projects work against.
- Review. Designed the architecture review — who sits on it and what it decides.
- Decision records. Recorded decisions so they are made once.
What changed
Architecture governance that makes projects faster rather than slower: standards to start from, a review that decides, and decisions that do not have to be argued again.
Want a result like this?
Bring the situation you are in. We will tell you where we would start, and whether it is worth doing now.