Dragon1 Way of Working

Second part of Dragon1

Dragon1 'Way of Working' elaborates on the second part of Dragon1. The ‘Way of Working’ offers various instruments, allowing the architect and other stakeholders to collaborate effectively on visual enterprise architecture within the company. What is expected of everyone?

Dragon1 also proposes setting up the company to support visual enterprise architecture work. For example, where does the company start working with visual enterprise architecture? And how can you grow as a company to the next level of maturity in working with visual enterprise architecture?

The following paragraphs outline which working method concepts of Dragon1 are essential to working with visual enterprise architecture. These working method concepts are presented within the working method framework. Why is Dragon1 built up from these working method concepts, and what are the mutual relationships between these working method concepts?

Way of Working Framework

The Dragon1 way of working can be described as a whole with an architecture framework. The framework consists of eight working method concepts. The working method primarily revolves around the question: who does what, when, how, and why. The starting point is that the better architects and stakeholders align, the more efficiently the company can work with visual enterprise architecture.

The Way of Working Framework shows the most important concepts that are part of the way of working of the method.

Architecture Role Playing

The concept of Architecture Role Playing indicates which groups of people within the company should play a role in working with visual enterprise architecture, according to Dragon1. Dragon1 indicates the most essential tasks, powers, and interests each person has in working with visual enterprise architecture. It also explains how to collaborate on visual enterprise architecture as optimally as possible.

Architects

The concept of Architects focuses on the architectural role of 'the architect'. The architect focuses on the essential aspects of working with visual enterprise architecture, such as creating architecture designs that support various architectures. Dragon1 offers a suggestion here on how the architect, as a person, should approach their architectural work. What does that mean for the architect when organizing his work? And what does that mean for the architectural services he can offer the company?

Design Assignment and Design Strategy

The concept ‘Design Assignment’ and the concept ‘Design Strategy’ are recognized as separate concepts. Together, they form the architect's most critical discipline, according to Dragon1. Together, they give the architect tools to engage in their architectural work effectively. Which specific strategies or approaches can he use for this?

Architecture Products

The concept of Architecture Products has also been recognized as a separate concept, because this concept includes several essential products that result from the architecture work processes. Architecture products that architects often create and for which high-quality requirements are set are referred to as an architect's professional products.

Architecture Organization

The concept of Architecture Organization indicates that an internal organization can be set up when a company has become enthusiastic about working with visual enterprise architecture. With what and how can you as a company best start with visual enterprise architecture according to Dragon1?

Architecture Maturity

The concept of ‘Architecture Maturity’ indicates how the company, using the architecture maturity model of Dragon1, can determine how far the company is in working with visual enterprise architecture. What steps can the company take to grow to the next level of working with visual enterprise architecture?