Digital Transformation with TOGAF: Embracing Agile Architecture
A common myth is that Enterprise Architecture (EA) and Agile cannot coexist. People often see EA as a "ivory tower" where everything is designed up-front in a waterfall process, while Agile is about "failing fast" and building things incrementally.
In reality, successful digital transformation requires both. You need the agility to deliver quickly, and you need the architectural vision to ensure those deliveries aren't building a fragmented, unmanageable mess. This is the world of Agile Architecture.
Moving Away from "Big Design Up Front" (BDUF)
In the old days of EA, architects would spend 6 months designing a 300-page "Architecture Definition Document" before a single line of code was written. This is called Big Design Up Front (BDUF).
In a digital transformation, this approach fails because by the time the design is finished, the business requirements have already changed.
The Agile Architecture Alternative: "Just-In-Time" Design
Agile EA focuses on Just-In-Time (JIT) design. This means designing just enough of the architecture to support the current and next few sprints. You don’t design for every possible future; you design for the immediate needs while keeping your eyes on the long-term strategic goals.
Mapping the TOGAF ADM to Agile
How do we actually use the ADM in an Agile environment? The key is to run the ADM in shorter, faster cycles (Iterations).
- Strategic Cycle (Long-term): Running a high-level ADM cycle (Preliminary through Phase H) over a 6-12 month horizon to set the overall direction.
- Segment/Program Cycle (Mid-term): Running an ADM cycle for a specific value stream or program every 2-3 months.
- Capability/Sprint Cycle (Short-term): Running a very lightweight ADM cycle for a specific team every 2-4 weeks.
This layered approach ensures that the "Big Picture" (TOGAF) and the "Delivery Speed" (Agile) stay in sync.
The "Architecture Runway" Concept
A key concept in Agile Architecture is the Architecture Runway. Think of a runway for a plane: the plane (the delivery team) needs a safe, smooth surface to take off.
The "runway" consists of the technical infrastructure, APIs, data models, and standards that the teams need to deliver features without hitting a wall. The architect's job is to stay 1-2 steps ahead of the delivery teams, building out the runway just before it's needed.
If the runway is too short, the delivery team has to stop and build it themselves, which slows down the "velocity." If the runway is too long, you've wasted time building things that might never be used.
Why Agile EA is Growing in Popularity
1. Faster Time to Market
By breaking the architecture into smaller, deliverable pieces, you can start seeing value from your digital transformation much sooner.
2. Better Stakeholder Alignment
In Agile EA, the architect is part of the delivery team. They are in the daily stand-ups and the retrospectives. This means they can adjust the architecture instantly based on real-world feedback.
3. Reduced Risk
Waterfall EA is a "big bet" — if the design is wrong, you don't find out until after months of work. Agile EA allows you to "fail fast" and pivot the architecture before millions have been spent.
Summary
Modern Enterprise Architecture is not about control; it's about enablement. By embracing Agile principles, you can turn your architecture from a bottleneck into an accelerator. You can guide your organization’s digital transformation with a clear vision while still delivering at the speed of the market.
In our next post, we’ll look at how to build a team that can handle this complexity: The Architecture Capability Framework — Building Maturity.
This post is part of the TOGAF 9.2 Masterclass series. Don't forget to check out our previous post on The Architect’s Journey — Career Paths & Roles.