simplicable technology guide
»
enterprise architecture
»
enterprise architecture anti patterns
»
ea change management
Enterprise Architecture is not Change Management
posted by Anna Mar, May 14, 2011
Its a common Enterprise Architecture pitfall: becoming a change management team.
Gaps vs. Change Requests
Looking to fill the gaps section of your enterprise architecture? Just ask your business users — typically they're more than happy to tell you about IT problems. The problem with this approach is that your gaps become a direct replication of your change management system.
Gaps represent the architectural differences between your current and target states. Enterprise Architects are in a unique position to identify opportunities to fix the root causes of business pain points. User change requests often focus on symptoms — EA gaps are the cure.
When gaps become a wish list of features — the EA team are little more than scribes.
EA Tool vs. Change Management System
When gaps are change requests — there is a danger that your EA tool will be used as a change management system.
Future State vs. Solution Architecture
If your future state is not far enough in the future — there is a danger that it will read like the solution architecture for your next major project.
|
CxO level executives are demanding metrics for EA — can you deliver?
|
|
Learn about common root causes of security risks.
|
|
This is the way to prove to your stakeholders that your recommendations are not just whims.
|
|
Learn about the 10 most important patterns for SOA success.
|
Recently on Simplicable
| |
posted by John Spacey
Tools and strategies for IT managers.
|
| |
posted by Anna Mar
Big data is an earth shaking innovation!
|
| |
posted by Anna Mar
Which cloud strategies will fail and which will succeed?
|
| |
posted by Anna Mar
It sometimes feels as if we've entered a world of cloud and now there's nothing but cloud.
|
