The KISS of Enterprise Architecture Governance
posted by Anna Mar, August 14, 2012There's a tendency for enterprise architecture governance processes to start off simple and become more complex with time.
As the complexity of the process grows — there's a danger it will become bureaucratic and burdensome. When this happens, it's time to get back to the basics. What's the EA governance process really meant to achieve?
The answer is straightforward — EA governance is intended to ensure that IT projects have an efficient architecture that supports the business.
A basic 9 point sanity check gets you most of the way there:
1. Redundancy
Does the project duplicate functionality that already exists in the architecture?2. Value
Does the project provide sufficient value to the business relative to cost?3. Strategy Mapping
Does the project map to the business and IT strategy?4. Due Diligence
Has the project performed their architectural due diligence?5. Enterprise Capabilities
Does the architecture provide the capabilities required by enterprise programs such as business continuity & resiliency planning, risk & compliance, enterprise security, user accessibility, legal?6. Technical Capabilities
Does the architecture provide reasonable technical robustness?7. Over Engineering
Is the architecture overbuilt?8. Common Services
Does the project leverage common services or is it reinventing the wheel?9. Standards
Does the project leverage enterprise standards?Recently on Simplicable
Cloud Guideposted by John SpaceyA guide to cloud computing including cheat sheets, best practices and metrics. |
Web Security: Battleships and Locustsposted by Anna MarThere are two types of web security threats: battleships and locusts. |
Web Security Illustratedposted by John SpaceyHow would you explain web security to your grandmother? |