The architectures of large organizations can become quite large and complicated, posing a challenge for the architects developing and maintaining them. In previous discussions, we have addressed a number of techniques for organizing and controlling such large models to keep things manageable. In this installment, we look at the processes and practices you can use to optimize the collaboration between the people working on these architectures.
Capability Based Planning
In the first blog of this series, I explained how important it is to raise your digital change capability to become an adaptive enterprise. I also highlighted the role of effective communication, as well as approaches to categorize and visualize enterprise architecture descriptions based on the TOGAF and ArchiMate standards. In this series, I also included guidance on which approach to select for modeling Architecture and Solution Building Blocks (both are types of logical or physical components). To round out this series, I will end by discussing the connection to Deployed Solutions.
Business Outcome Journey Maps are a new technique that help you focus on the key aspects of value creation in your enterprise. Here we show you what they are, why they are useful and how they are supported in BiZZdesign Enterprise Studio.
In recent years, we see the audience and attention for business architecture steadily increase. A business architecture provides a business-oriented abstraction of the enterprise in its ecosystem, which helps the organization in decision-making and direction-setting. This maturation of the business architecture discipline makes the role of model-based support for design, analysis and decision-making also increasingly important. In this series of posts we will introduce you to useful techniques for business architecture modeling and how they are supported by BiZZdesign Enterprise Studio. Read more
In the past, my colleagues and I have written several blogs on the combination of enterprise architecture and agile ways of working (e.g. Enterprise Architecture and Agile Development: Opposites Attract?, Enterprise Architecture and Innovation: A cultural change, Escaping the Jaws of the Project Monster). In this blog, I want to focus in more detail on the use of the ArchiMate language in the context of agile methods, in particular the Scaled Agile Framework (SAFe). Read more
In several previous blogs, we have outlined how you can use ArchiMate 3 in the context of business architecture and strategy development, such as Capability-Based Planning, and combining it with the Business Motivation Model, the Business Model Canvas and the Balanced Scorecard. In this blog, we continue with the series, looking at how you can describe value chains, value streams, and value networks. Read more
In a recent article by McKinsey, they eloquently argued the importance of enterprise architecture for digital transformations. But they also provide some important criticism of the state of practice. To be really effective at supporting digital transformations, many enterprise architecture practices need to change their behavior.
As we have seen in the previous blog, ArchiSurance wants to establish several new capabilities to support its ‘Digital Customer Intimacy’ strategy, such as Digital Customer Management, Data-Driven Insurance, Data Acquisition, and Data Analysis. Positioning these in the context of its current capabilities leads to the following figure, using the ‘highlight’ function of BiZZdesign Enterprise Studio to emphasize these new elements. Read more
In our previous blog, we outlined the relationship between business strategy and capabilities at a high level. But we have not given you any guidance yet as to how to create a good overview of your capabilities. In this blog we look at why identifying capabilities is important for organizations, how they can be defined, how to classify them, and how to include them in a capability map.
In this series of blogs, we describe the use of the new ArchiMate 3.0 standard in practice. We use a fictitious but realistic example company, ArchiSurance, well-known to the users of ArchiMate as this is the company from the standard case study provided by The Open Group.
On June 14, The Open Group launched the new version of the ArchiMate modeling language for enterprise architecture at the Enterprise Architecture Conference 2016 in London. This is a new step in the development of a standard that started in Netherlands, but in the meantime has received broad international acceptance.
Agility has become a key ability of enterprises. The pace at which customers require changes, at which new laws and regulations affect services and introduce processes, and the ease with which competitors can disrupt your business, as Google and Apple do nowadays, leads to tremendous pressure. Pressure to change rapidly, to adopt new technologies, to generate growth, to scale up or to reduce cost. Read more
In theory, an ArchiMate® model can be created using just pen and pen, or a whiteboard and markers. There are also software platforms that provide an ArchiMate modeling environment, which come with many automated capabilities and analysis functions.
However in this post, we will focus on an important element in maturing into an advanced, mission critical modeling capability: the model repository.
Strategy execution remains a challenging task for many organizations. The ‘Digital Enterprise’ requires major business transformations, delivered at speed. Most organizations are in a constant state of change. The ‘unfreeze-change-freeze’ model, reasoning from the current to a desired future state, no longer applies; the current state is always in flux and the future state is a moving target. Read more
As outlined in another blog, architecture-based enterprise portfolio management plays a crucial role in an integrated business transformation approach. Portfolio management is responsible for allocating investments to various asset categories and for creating a healthy project and program portfolio mix that realizes the organizational goals. There should be a balance in, for example, the types of projects (development, research, etc.) and long-term and short-term projects.
The other day, while I was musing about the reasons why many large organizations see many of their IT initiatives fail or underachieve, I came up with a rather simple conclusion: ‘project thinking’ is the root cause of these disappointments. Let me explain. Read more
Very few organizations have a systematic and reliable way of translating a business strategy into action across all relevant elements of the organization. Implementing a long-term plan by successive decomposition, design and realization steps is only possible in stable circumstances. Classical top-down strategy implementation cannot keep up with the transformation speed required in a rapidly changing environment.
In my previous blog post on Enterprise Architecture at BiZZdesign in 2014, I described how the true value of architecture lies in its relationship with other disciplines within the enterprise.