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