2021. okt. 8.3 perc olvasás

Moving Enterprise Architecture Frameworks into the Future

Moving to an Agile Enterprise Architecture

One of the most common complaints of the traditional enterprise architecture function is that it does not keep up with the pace of change. It does not facilitate agility.

The development and adoption of the Agile methodology has done more to force enterprise architecture to change its approach than any other force in the business. Businesses must be able to rapidly change course, account for technological disruption, develop new capabilities or enhance customer experience of existing capabilities. Fortunately, recent technological advancements have enabled the automation of architecture processes. Architects can now spend time doing the things they always wanted to do, but never had the time. They can focus on exploring emerging technologies and innovation, build reference architectures for these, and help set and achieve strategic business objectives. To do this, though, architects must understand more than just technology. They must understand the business and how technology enables that business.

The Role of Enterprise Architecture is evolving: more business oriented

In the current transformative environment, companies are experiencing disruption and modernization in not just product offerings, but in management and organization as well. Employees now operate in an enterprise rife with complex systems, horizontal and matrixed communication channels and stakeholders who do not work with traditional mechanisms of hierarchical authority.

Decentralization of the Enterprise Architecture function

The command and control management espoused by Taylorism has been challenged by new methods of problem solving that have manifested in new management and organizational structures.

These methods have led to the transformation or elimination of traditional roles such as business analyst and project manager. The shift to more design thinking has led to a growing interest by business unit employees in the concepts of enterprise architecture. This has contributed to the decentralization of the enterprise architecture function and the relegation of the enterprise architect to a role of coach in the art and/or science of enterprise architecture.

The Expansion of Enterprise Architecture beyond IT

Another transformation of enterprise architecture is already underway, the expansion of enterprise architecture beyond the confines of IT. Enterprise Architecture is permeating the business. This expansion stems from business people who know that for all intents and purposes, their companies are technology companies. This also means that for business to function at a high level, it is necessary for architects to have a deep knowledge of technologies, know how these technologies are applied to business capabilities and functions, provide a master repository of architecture components and relationships, and maintain a common architecture methodology.

The Problem with Agile Methods

Agile methods solved some very specific problems. Projects had very high failure rates. Either the stakeholders were not getting what they expected, or time to value was not keeping up with the rapid pace of change in the marketplace. Also, many projects experienced heavy technical debt, causing enormous downstream costs when technologies were no longer viable and had to be updated. The results were inevitable immobility.

Changing the organizational structure by breaking the pyramidal hierarchies and focusing on interactions between individuals more than on processes and tools, changes could be more rapidly implemented thus allowing rapid changes in direction and development of user-friendly functionality. This organizational revolution did not come without risk. Small agile teams may be able to make rapid changes and adjust to meet changing requirements, but the absence of the traditional pyramidal structure means that the big picture is no longer seen. The collection of teams lose the perspective of a common goal and simply iterate on details that no longer contribute to the value of the original effort.

Enter Agile @ Scale

There is no argument against a need for agile thinking. Due to rapid technological advancement, where barriers to entry of new products in the marketplace are virtually non-existent, and where market shares are frequently redistributed, there is a strong need for a variable adjustment. This variable comes in the form of Agile @ Scale. One of the most popular examples of agile @ scale is SAFe (Scale Agile Framework). SAFe was designed in 2011 by Dean Leffingwe. This framework has shaken up traditional architecture. Not only does SAFe integrate with architecture frameworks, it allows the application of the methodology to larger groups that can work effectively without dispersing and according to a overarching plan. The purpose of SAFe is not to manage a project but to build a product. The product is decomposed into functionalities or capabilities instead of requirements. This provides a faster customer feedback loop and avoids costs of delayed product launches.

Click here to read the full article.