James McGovern, Enterprise Architect for The Hartford, and all around Enterprise IT Thought Leader, recently posted the characteristics of Enterprise Architecture 1.0 versus Enterprise Architecture 2.0:
1.0 2.0
Abstract Authority Community
Project Oriented Management Strong
Technical LeadershipComprehensive Documentation Working Software
Following a Plan Responding to Change
Governance Stewardship
Rationalization Innovation
Outsourcing Open Sourcing
NDA Declarative Living
Large Analyst Firms Small Analyst Firms
Management Leadership
ERP for IT Burndown
CMMi Agile Methods
Best Practices Practical Considerations
Reference Architectures Shared Vision
Time Accounting Functional Delivery Accounting
Buy vs. Build Buy vs. Build vs. Open
Project Oriented Service Oriented
Politics Diplomacy
Polarization Dialog
Buy-in Enlistment
Restrictions Rights
Cathedral Style Development Bazaar Style Development
Process People
This is a great list. I see a lot of synergy with my own thoughts on Business-Driven Architecture. In typical James fashion, he encourages the architect community to discuss and comment upon his list:
If others have insight into emergent behavior in this space, please do not hesitate to either leave a comment and/or respond from your own blog. We do not mature as a profession until we start having honest open conversations amongst each other…
With that, I offer a few additions:
EA 1.0 EA 2.0
Big Bang Incremental
Rigid Tolerant
Technology-Driven Business-Driven
And encourage readers to participate along with James, in advancing EA 2.0…
Stefan Kleineikenscheidt says
Enterprise Architecture 2.0
Working in the platform and architecture department in a big cooperation, it is an everyday challenges to bring the platform development standards and architecture to all local subsidiaries around the globe. Therefore the following comparison table by …