“Enterprise Architecture As A Service” – How – REACH for the STARS

In two prior blogs, I described why “Enterprise Architecture As A Service” (EA As A Service) would be a good thing and what it might look like.

Why? Because a properly implemented service delivery model would put the emphasis in more appropriate places:

Production and use value versus EA as a deliverable
Timely value along the way versus at the end
Clear expectations versus vague promise
Support and enablement versus ivory tower compliance
What? A portfolio of services provided on demand in service categories:

Planning Services to scope based on need
Buy-in/collaboration Services to ensure the right people in the organization are engaged
Development Services to build the right parts of an EA at the right time
Management Services to ensure that the EA efforts delivers value consistently
Usage Services to derive value from the EA
Decision Support Services to support Portfolio Governance decisions

The Adaptive Enterprise: Using Standards for Transformation – A Conversation with Marc Lankhorst

The rapid pace of change in technology and business today is driving the need for companies to be more adaptive than ever. Standards can help make these transitions easier for companies and aid them in their transformation efforts.

This blog is the first in a series that looks at how standards can be used together to help organizations better facilitate the transformations and changes they need to make. In this first installment, we spoke to Marc Lankhorst, Managing Consultant for BizzDesign, about the business imperatives that are driving enterprises to adopt a more adaptive approach to how they do business. Subsequent blogs in this series will explore the practical use of standards for adaptation and transformation.

“Enterprise Architecture As A Service” – What

In my previous blog, I described why “Enterprise Architecture As A Service” (EA As A Service) would be a good thing. Fundamentally because a properly implemented service delivery model would put the emphasis in more appropriate places:

– Production and use value versus EA as a deliverable
– Timely value along the way versus at the end
– Clear expectations versus vague promise
– Support and enablement versus ivory tower compliance

1 2 3 4 5 32