Key takeaways
- EA helps agile teams deliver faster, without slowing them down.
- Reactive contribution: technical debt from sprints; proactive contribution: standards, reusable components, and guardrails.
- For mature products: simplify the ecosystem with the ADM and aim for operational excellence.
- Enterprise agility is broader than agile software development.
- Partitions, levels, and iteration make the ADM responsive.
What EA brings to an agile environment
Digital transformation is driven by fast-changing technologies that alter how people work, communicate, and entertain themselves. In this context, EA supports agile teams by giving them visibility on topics an isolated product team cannot see. The Study Guide groups these contributions into three families, which must be told apart in scenario questions.
- Reactive: handle the technical debt produced by sprints in a cohesive, connected way
- Proactive: anticipate needs by publishing standards and reusable components, overseen by governance guardrails
- Mature products: simplify the complexity of the digital ecosystem with the ADM and establish an EA Capability aimed at operational excellence
Enterprise agility and agile development
The word “agile” often evokes the Manifesto for Agile Software Development. Its principles can be used to adapt TOGAF, but enterprise agility is a broader context that calls for other techniques. It matters because it helps react better to change: more customer- and product-centric, more efficient, better able to ensure regulatory compliance.
EA acts there as a framework for change, linked to strategic direction and business value. It offers enough visibility across the organization to master complexity, sustain continuous change, and limit unforeseen side effects. The guardrails it provides remain proportionate: they oversee re-use without approving every backlog item.
TOGAF concepts serving agility
TOGAF meets the need for responsiveness through three concepts already seen in this chapter. Partitions divide the work into several initiatives run in parallel. Levels allow the architecture to be developed at different granularities, from strategic framing down to the detail of one capability. Iteration allows short cycles and successive revisions.
For more, the standard points to the Series Guides “Applying the ADM Using Agile Sprints” and “Enabling Enterprise Agility”, and to the Open Agile Architecture standard. Guide G217 specifically addresses using TOGAF in the digital enterprise.
TERMS TO KNOW
The terms, in context.
- Technical debt
- Future cost of technical shortcuts taken to deliver faster.
- Guardrails
- Light governance overseeing the re-use of standard components.
- Enterprise agility
- Ability of the whole enterprise to react quickly to change.
- Digital enterprise
- Enterprise creating value through digital products and services.
- Open Agile Architecture
- Open Group standard for architecture in an agile context.