In the two previous installments, we discussed planning and roadmapping in the context of enterprise architecture, and how you can use the concepts of the ArchiMate language to model your roadmaps. We showed how you can model the evolution of your ente…
The promise of enterprise architecture is that it helps improve decision making. Typically, the role of the enterprise architect is to advise and enable other stakeholders to make better decisions. Therefore, Enterprise Architecture – more than anythin…
In the recent few years, Enterprise Agility has become one of the key drivers for many organizations to be relevant and to sustain their core businesses. As the change is happening so rapidly in every business sector, if the organizations do not adapt to the speed and scale in delivering their services, they would soon become obsolete and run out of their customer base. To handle and to succeed in the business with the ever-changing business scenarios, transformation initiatives like driving Enterprise Agility has become the most important priority for present CXOs.
In our previous blog post on planning and roadmapping, we discussed the general idea of planning and roadmapping in the context of enterprise architecture and capability-based planning. We addressed different levels of roadmaps, ranging from short-term…
A key driver for management in general and enterprise architecture in particular is to get a better grip on the future, on the evolution of your enterprise. A common technique to support this is roadmapping. A roadmap is a strategic plan that shows the…
The Open Group will explore Enterprise Architecture (EA) best practices and open standards for business transformation at the event in Lima, Peru, on October 4 and 5, 2018. More detailed information can be found here.
The business environment is evolving. Changes to regulations, new customer demands and the increased use of information technologies and mobile devices are just some of the trends putting pressure on organizations to prioritize innovation and efficiency in order to remain competitive.
– Marc Lankhorst, Fabian Aulkemeier In a previous blog post on the features of our collaboration platform, we have explained how you can support people in working together on architectures and other models via structured workflows. In that post, …
The Open Group hosted its latest event July 23 – 26 in the Lone Star State at Houston’s Westin Oaks at the Galleria. The theme was ‘Digital Transformation in the Energy Industry’. We welcomed over 200 attendees from 13 countries, including Brazil, China, and the Netherlands.
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
One of the great things about doing my ‘Tetradian on Architectures‘ mini-video series is that I get to tackle real-world questions about everyday enterprise-architecture, sent in by people all around the world. In this case, for the current episode in…
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