Download the Agile Enterprise Architecture Report

The Agile Enterprise Architecture Report covers our experience - Agile Enterprise Architecture is real, practical and valuable. We do it every day. Field reports bridge the theoretical concepts and the practice of actually doing the work.

Report covers three uses of the term agile - developing enterprise agility, supporting agile software development, and using agile methods to develop enterprise architecture.

Enterprise agility is being able to deal with the unexpected

Enterprise architecture guides and constrains agile development to meet needs bigger than the product

Agile methods are a natural for developing enterprise architecture

Agility and Enterprise Architecture

Agile Enterprise Architecture Report Includes

Agile Methods to develop Enterprise Architecture

Epics, stories, and minimal viable product are simple techniques to break work down. Produce enough for the EA use case and the decision at hand. Get the decision and move forward.

Enterprise Architecture constrains agile development

Enterprise architecture supports agile development by determining the change approach, guiding backlog grooming, constraining sprint acceptance, solve dependency. Stay out of the product!

Three uses of the term agile

Six Agile EA uses cases cover the detail of Enterprise agility, supporting agile software development, and using agile methods. You build an effective EA Team by designing to the questions you answer.

Enterprise Architecture delivers across the spectrum

The work products that support enterprise strategy are wildly different from those that constrain agile software delivery. Develop the EA Team you need.

Download the Agile Enterprise Architecture Report

Conexiam's EA Capability Practice develops high-functioning enterprise architecture teams. Agile Enterprise Architecture is real, practical and valuable. We do it every day. The Agile Enterprise Architecture Report is what we see.

We built this as a field report. In the sciences, a field report bridges the theoretical concepts with the practice of actually doing the work. Theoretical concepts help us sustain a conversation across our distinct work practices. Theoretical concepts have to explain best-practice to develop and consume enterprise architecture.

All that matters is actually delivering beneficial architecture and improving our organizations.

 

Directing EA Teams to get into the detail of agile software development continues the unfortunate practice of calling IT-centric technology wizards Enterprise Architects. IT-centric technology wizards are not Enterprise Architects. Their work is not enterprise architecture.

Effective EA Teams' delivery is continuous and incremental - supporting the decision or action at hand. Architecture work performed after the decision is simply expensive documentation. Getting ahead of decision-making requires understanding what they need and when.

The work products used to constrain agile software delivery are wildly different from those supporting support enterprise strategy decisions. High functioning EA Teams can work across the spectrum.

Agile and Enterprise Architecture Work Product

What happens next

Download the Agile Enterprise Architecture Report

We will add you to an email list that focuses on being a better enterprise architect.

 

Scroll to Top