![]() This kind of architect role is focused more on facilitation and enablement than control, as the number of solution architects in a federated environment typically dwarfs the number of enterprise architects. In this model, which is more commonly associated with cross-functional DevOps culture, the roles of solution and enterprise architects are generally broader in an effort to integrate the related concerns of infrastructure, operations, and security in product-oriented teams. The federated model’s enterprise architects facilitate only the most high-level planning and artifact creation and act as on-demand service providers to support distributed teams. The guild may be complemented by a small central architecture team or architecture center of excellence (CoE). Control and governance are typically the primary concerns of the central enterprise architecture team.īy contrast, the federated model generally relies upon a guild or “community of practice” of solution architects embedded into individual development teams. Further, centralized teams for related roles, such as infrastructure, operations, and security, are also held apart from the development function. In this model, development teams themselves may have few or no qualified solution architects, as this role is consolidated within the central architecture team. The central model involves a large-scale central architecture team that defines the process and artifacts required for approval of new work and ensures adherence by development teams. The architecture function is generally based on one of two fundamental models: central and federated (exhibit). ![]() How should the architecture function be designed in an agile enterprise? How can companies simultaneously ensure adequate stewardship of architecture across the organization without losing the benefits of agility and distributed problem solving? IT leaders can arrive at the right outcome by answering three primary questions. (For more on the role of enterprise architects in today’s digital environment, see “ How enterprise architects need to evolve to survive in a digital world.”) We therefore believe every software organization benefits from an empowered architecture function, regardless of its structure. Nonetheless, adopting comprehensive architectural goals and standards allows organizations to establish shared objectives, agreed-upon guidelines, and a common language. It can even create a learned helplessness in development teams, depriving them of the ability to flex their architectural muscles and learn by doing. Some agile proponents view the discrete architecture function as a silo that interferes with the natural flow of information and problem solving between agile teams and their engineers. This notion of architecture as a discrete and separate function is further challenged in a digital enterprise: architecture does not have a natural home in the idealized model of a flat, distributed agile-delivery organization made up of developers, designers, testers, and product owners. ![]() However, reducing the role of architecture to a compliance function or separating it from day-to-day operations confines its value to a policing entity or an abstract function in an ivory tower. Even many hollow IT organizations-those that contract out all hands-on product development-have kept architecture in house, viewing it as essential and nonfungible.Įspecially in highly regulated industries, the architecture function is often seen as inseparable from essential governance and compliance requirements. An effective architecture function also aims to generate efficiency and scaling benefits by platforming reusable assets and defining common patterns.Īs a result, some organizations have established architecture as a stand-alone department. It could be described as the art of making sure the many systems, products, and platforms within an organization work together seamlessly critical concerns such as security, reliability, and operability are incorporated and business change requirements are delivered within the expected time frame and cost parameters. Since the early days of IT, the importance of the architecture function has been appreciated. ApBy Christian Lilley, Klaas Ole Kürtz, Henning Soller, and Christian Stüer
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |