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.
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.
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.
Earlier this month, I wrote the first blog post in a series based on a World Cafe discussion we had around the lacking relations between policies and measures in many organizations. The discussion took place in the form of 4 debate rounds. In the previous blog post, I presented Information Security as a necessity of life. There is no doubt that Information Security is a very important topic for most organizations, but during the debate, many participants were uncertain as to whether, and how to communicate to the rest of the company about it. In this blog post, I will present the conclusions of this discussion.
Sharing knowledge and good practices is one of our core values at BiZZdesign. We regularly organize and contribute to online and offline seminars, conferences and round table sessions. After one such presentation entitled “Security is not an IT problem”, we organized a World Café to discuss the related topics like security architecture, security controls, and security systems. Please share your good and worst practices by reacting to this blog.
Most enterprise architects believe that Enterprise Architecture is a relevant discipline for members of the board. However, CxO’s often aren’t really of the same opinion. We believe that is because they do not usually experience the true value of architecture. What can an architect do to improve this? Below we present seven useful tips.
The Open Group Architecture Framework (TOGAF) is the most popular framework for developing an enterprise architecture (EA). It is an open standard and may be used freely by any organization wishing to develop an enterprise architecture for use within that organization. BiZZdesign believes in an EA approach that is based on open standards and frameworks. We combine and pre-package frameworks and standards like TOGAF and ArchiMate as an accelerated approach to jump-start customers’ EA programs. In this blog we will explain how we use TOGAF as framework, apply it in practice, with the goal of doing business-outcome-driven EA.
Until quite recently, IT security was exclusively the domain of security specialists. However, in the last couple of years, organizations have started to realize that IT-related risks cannot be seen in isolation, and should be considered as an integral part of Enterprise Risk and Security Management (ERSM). ERSM includes methods and techniques used by organizations to manage all types of risks related to the achievements of their objectives.
In a previous blog post, Marc Lankhorst discussed the value of EA in managing risk, compliance and security in the enterprise. He suggested a number of steps to take next; two of these steps are discussed in more detail in this blog:
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.
In my previous blog posts, I discussed the way I see strategy work and the types of models that can be used, and how the business model canvas should be the focal point for architecture work. In this blog post, I will show that enterprise architecture is the tool to go from strategy and business model to execution.
Business models are a helpful way to define a business strategy and steer an organization in the “right” direction. Furthermore, business models foster discussions on the way organizations want to deliver value to their customers. Building business models is fun! Thinking about your organization and its future in an abstract manner is addictive, since there is no chance of failure…
Times are tough: many businesses are struggling to stay afloat in the wild economic currents. Many organizations attempt to find a “blue ocean” of uncontested space, but let’s face it: most of us are stuck in a “red ocean” with a lot of competition, growing power of both suppliers and consumers and increased threat of substitutes. Indeed, one can argue that it is “all hands on deck” for many organizations in their struggle to survive.
Over the last two decades, Lean management has proved to be very powerful in improving an organization’s business process performance. During the same time frame, Enterprise Architecture came up as a discipline for controlling the complexity of organizations, their processes, information and IT. At first glance, both approaches appear very different in nature. Read more
One of the most popular topics to debate amongst architects is: what is the proper level of abstraction needed to be applied when creating architectures? Although always a lengthy debate, I don’t ever recall reaching a conclusion that was satisfactory to me. Even worse, at times, my architectural work was discredited by people, claiming “its level of abstraction was too high to be useful.” Read more