TOGAF and Agilism

TOGAF (The Open Group Architecture Framework) is an enterprise architecture framework that provides an approach to the design, planning, implementation, and governance of an enterprise information architecture. The Enterprise Architecture concept aligns strategy with business operations and demand to supply and demand from an IT perspective, ensuring that the necessary changes are identified and implemented to be in line with the defined strategy and objectives.


The definition of software-based systems architecture given by the ISO/IEC/IEEE 42010 standard can be summarized as: “the fundamental organization of a system, represented by its components, their relationships to each other and to their environment, and the principles that govern their design and evolution.


However, TOGAF has its own definition of what an architecture is, which in summary is “a formal description of a system, or a detailed plan of the system at the level of its components that guides its implementation”, or “the structure of components, their interrelationships, and the principles and guidelines that govern their design and evolution over time. (ref: Wikipedia).


ADM (Architecture Development Method) is the method defined by TOGAF for the development of an enterprise architecture that meets the business and information technology needs of an organization. It can be adjusted according to the needs of the organization itself.


How to apply AD in a Scrum project

The entry point in TOGAF is to produce the architectural vision and principles on which any IT response, solution or change is based to meet the needs of the business.
With that architecture work request, a description of the business strategy, its objectives and the drivers of the business have to come. Any architectural principles defined so far and any reference to existing repositories where the architectural information has been deposited.
Architectural principles are a subset of all the IT principles for responding within the organisation. Each principle has four parts:

  • Name: simple, price and easy to remember.
  • Statement: a phrase that describes what the principle consists of.
  • Rational: an explanation of why it is important and how it benefits the business
  • Implications: a list of what is required to address compliance with this principle and how it can impact the business
    There should be a basis of no more than 10-20 principles and the inherent constraints we encounter should also be identified. TOGAF provides a sample basis of 21 principles.
    This helps to establish the architectural context. This information as seen in the Scaled Framework (SAFE) should be fed into the Value Streams and detailed to create the enablers so that all key functionality to meet the business objectives can be achieved. Its inclusion within the ARTs (Agile Release Trains) ensures the construction of the Architectural Runway that serves as a base for the teams to create emerging architectures aligned with the defined principles and within the good use of the architectural runway.
    Architectural analysis can be related to:
  • Business architecture: related to the business flows so it can generate value.
  • Information architecture: entry, communication/transit, APIs, system interoperability, compliance, security, backup, archiving and destruction.
  • Application architecture: products, libraries, monitoring, metrics, governance, deployment, supervision.
  • Technical architecture: frameworks, languages, structures, utilities, repositories, branch and merge strategies, deployment, …

For its use, it is vital the evangelization on:

  • Sharing and approval of the vision and associated principles.
  • the identification and understanding of Non-Functional Requirements (NFRs) and their implementation.
  • The capacity and dimensioning of the systems.
  • Good programming practices (TDD, SOLID, YAGNI, …)

To enable changes within the agile teams and give them the ability to make emerging designs. The ability to make architectural reviews – similar to peer programming and code reviews – on proposed changes to teams and their publication and link to enterprise repositories, as well as defined roadmaps to cover the identified architectural principles, should be provided.


Likewise, it is fundamental to establish a design thinking / lean start up pattern to establish what is necessary, what needs to be changed or implemented and why, and to make phased implementations to iterate over the solutions and enable at all times the ability to implement fundamental business requirements to reach the organization’s objectives.

To enable changes within the agile teams and give them the ability to make emerging designs. The ability to make architectural reviews – similar to peer programming and code reviews – on proposed changes to teams and their publication and link to enterprise repositories, as well as defined roadmaps to cover the identified architectural principles, should be provided.


Likewise, it is fundamental to establish a design thinking / lean start up pattern to establish what is necessary, what needs to be changed or implemented and why, and to make phased implementations to iterate over the solutions and enable at all times the ability to implement fundamental business requirements to reach the organization’s objectives.


Supporting these activities through Communities or Guilds focused on architecture review is a good way to support and cross-cutting best practices and use cases.

Ref:

https://www.ben-morris.com/can-togaf-and-agile-really-go-together/
http://opengroup.co.za/sites/default/files/presentations/Successfully%20Doing%20TOGAF%20in%20a%20Scrum%20Project%20-Marvin%20Williams.pdf
http://pubs.opengroup.org/architecture/togaf8-doc/arch/chap29.html#tag_30_06
https://www.scaledagileframework.com/architectural-runway/
https://simplicable.com/new/non-functional-requirements
https://thefullstack.xyz/dry-yagni-kiss-tdd-soc-bdfu/

Enterprise  Architecture and Innnovation Management. Ed.Corso. Martin Owen, Alan Burnett.

Leave a Reply

Your email address will not be published. Required fields are marked *