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