Agile Enterprise Architecture

A Framework to support Digital and Agile Transformation of the Enterprise.

Agile Transformation (AX)

Adoption of principles and practices that support continuous innovation

Digital Transformation (DX)

Adoption of technology to improve efficiency, value or innovation.

Inspiration

The content herein has been inspired by the latest developments in Enterprise Architecture

Open Agile Architecture™ — A Standard of the Open Group

The Open Group Architecture Framework — TOGAF

Lean Enterprise Institute

Scaled Agile Framework (SAFe)

Lean IX — DSM Web — C4 Model

Background

Architectural Styles

  • Emergence Architecture refers to what appears (desirable or undesirable functions) or materializes (desirable or undesirable outcomes) when a complex system operates

  • Intentional Architecture traditionally involves Big Design Up Front (BDUF) and is associated with waterfall model of system development.

    • In an Agile environment, one must only do just Enough Design Up Front (EDUF) ot create an adaptable foundation that can address unexpected requirements with little to no reengineering.

  • Concurrent Architecture performs simultaneous, rapid, low-cost analysis on multiple solutions to converge on the best available option.

  • Continuous Architecture facilitates ongoing incremental changes to the product or platform.

  • Architecture Refactoring is the normal restructuring that occurs when an architecture evolves.

Framework

An Agile Enterprise Architecture leverages a combination of emergent and intentional architecture that promotes segmentation to facilitate concurrent, continuous development and built-in capacity for architecture refactoring.

Goals

An effective Agile Architecture minimizes unnecessary complexity or undesirable outcomes by leveraging

  1. Modularity - to facilitate autonomy and resilience,

  2. Standardization - to support rapid software or system reconfiguration, and

  3. Partitioning (Segmentation) - to allow system components to evolve as independently as possible.

Principles

  1. Business Driven — Architecture is designed to help provide anci support the capabilities necessary for the business' vision and goals.

  2. Value Focus — Architecture aligned with business activities must always add value

  3. Collaborative — All internal and external stakeholders define requirements, early and ofen

  4. Just Enough, Just In Time — Minimal definition to communicate a capability then refine and implement a solution only when actually needed

  5. Iterative (Think Big, Act Small) — Maintain a strategic vision but avoid elaborate plans to deliver frequent, incremental value

  6. Return on Investment (ROI) - Understand the true cost vs the outcome of a technology investment

Blueprint

To ensure that the technology architecture remains in alignment with the current and future needs of the business, the following artifacts should be created and continually maintained

Business Capability Map

A Business Capability Map is the articulation of the resources and expertise an organization needs to perform core functions in order to better strategize technology solutions that meet those needs.

Multi-Domain Matrix

A Multiple Domain Matrices (MDM) facilitates analysis of a system's (or organization's) structure across several perspectives within a single view by a combining Domain Mapping Matrix (DMM) between two Design Structure Matrices (DSM).

C4 Model

The C4 Model is an "abstraction-first" approach to diagramming software architecture, based upon abstractions that refect how software architects and developers think about and build software.

Approach

Teams work cross-functionally to design and develop a set of modular building blocks that can be configured and assembled to rapidly adapt and scale with the business. In order to maintain product-market fit and agility, the disciplines of Design Thinking and Lean Product & Process Development are leveraged. One or more of the following concepts can be used when developing new products or implementing new systems.

Value Streams

Value-Stream Mapping represents all of the activities, both value and non-value creating, required to deliver a product or service.

Customer Journeys

A Customer Journey Map is a visual representation of a customer’s experience with a business at every stage and across all channels that illustrate the factors that directly or indirectly motivate or inhibit their progress.

Experience Design (UX)

Develop holistic experiences for all users across all aspects of a service or product

Minimum Viable Products (MVP)

Build products with just enough features to be usable to generate early feedback for future development