This blog, the second in a series with Marc Lankhorst, Managing Consultant for BiZZdesign, looks at how standards can be used together to help organizations better facilitate the transformations and changes they need to make.
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
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
The Open Group TOGAF Standard Version 9.2 was published April 16, 2018. A common misconception voiced by several people at that time was that Enterprise Architecture in general and the TOGAF Standard are barriers to enterprise agility.
This paper addresses that misconception by reference to specific sections of the standard; it does not assume the adoption of any specific agile method.
I was delighted to attend another one of The Open Group TOGAF® User Group meetings. This one was held in London on April 18, 2018 with great interactions between users of the TOGAF Standard, experts, and staff of The Open Group. Attendees got that chance to Share experiences, be Enlightened by news, and Engage in the development process by expressing needs – i.e. to SEE TOGAF a little differently.
In the fast paced technology driven businesses, quick turnaround solutions like microservices often take the precedence over “planned” integration. This strategy, although in short term, provides for better business value, in the long run, creates unmanageable technical debt. As uncontrolled business debt erodes business’s ability to grow further, uncontrolled technical debt erodes IT department’s ability to fund future innovations. Although in many cases it’s an easiest approach to take, piecemeal achievements are short lived. Soon, IT teams find themselves lost in a sea of fragmented software gizmos.