Aggregated enterprise architecture wisdom
This is such a poignant post that I felt compelled to repost it here. In a Linked in blog post by: Pallab Saha, he clearly positions why EA is a superset of IT architecture and why the two need to be kept separate. I am re…
When we talk about enterprise-architecture, what is ‘the enterprise’? For that matter, what is ‘enterprise’? Seems they’d be fairly foundational questions, yet most of the answers we see seem, well, kinda thin… If we hunt around on the net, we’ll find plenty of definitions for ‘enterprise’: “a business venture”, “a project or undertaking, typically one […]
This is such a poignant post that I felt compelled to repost it here. In a Linked in blog post by: Pallab Saha, he clearly positions why EA is a superset of IT architecture and why the two need to be kept separate. I am reminded of my study of Strunk and White’s The Elements of Style – the classic treatise on clarity and brevity of written expression. Pallab nailed it in these collection of key points:
Six Reasons Why EA Should NOT be Assigned to the IT Department
6. EA ≠ IT Architecture
5. True EA leads to redistribution of authority, which is beyond CIO jurisdiction.
4. EA value proposition (i.e. standardization vs. innovation) is solely business realizable.
3. The primary goal of EA is to build coherent enterprises, not better IT systems.
2. Synthesis takes precedence over analysis.
1. EA failure is an organization failure, not an IT failure.
It’s another week. Which means another (slightly-delayed) week’s-worth of Tweets and links. Usual categories, usual ‘Read more…’ link: Enterprise-architecture, business-strategy and all the business-big-picture stuff: jdevoo: How to set sustainability goals http://j.mp/qb6WX0 >> applying SMART principles #entarch jdevoo: Designing a sustainability dashboard? Modeling is not optional http://j.mp/p7PQA8 #entarch greblhad: Anyone has input on using http://ideascale.com/ […]