Implementing TOGAF Using SCRUM Methodology
Implementing TOGAF (The Open Group Architecture Framework) using Scrum requires blending the structured, enterprise-wide approach of TOGAF with the agile, iterative delivery model of Scrum. Below is a step-by-step guide to achieve this:
1. Understand TOGAF and Scrum Synergy
- TOGAF provides a high-level framework for enterprise architecture (EA) with phases like ADM (Architecture Development Method).
- Scrum is an agile methodology for iterative software/product development with Sprints, backlogs, and cross-functional teams.
- Goal: Use Scrum to execute TOGAF phases incrementally while maintaining agility.
2. Map TOGAF ADM Phases to Scrum Sprints
Instead of executing TOGAF linearly, break it into iterative cycles (Sprints):
| TOGAF Phase | Scrum Implementation |
|---|---|
| Preliminary Phase | Sprint 0 (Setup governance, roles, tools) |
| Phase A: Vision | Product Backlog (Epics for EA vision) |
| Phase B-D: Business, Data, Application, Technology Architecture | Split into Sprint-sized increments (e.g., one domain per Sprint) |
| Phase E: Opportunities & Solutions | Backlog refinement for implementation |
| Phase F: Migration Planning | Sprint tasks for roadmap prioritisation |
| Phase G: Implementation | Scrum Sprints (deliver architecture increments) |
| Phase H: Change Management | Continuous improvement (Sprint Retrospectives) |
3. Adapt TOGAF Artifacts to Scrum
- Architecture Backlog: Replace TOGAF deliverables with a prioritised backlog (e.g., “Define Data Architecture” as a Sprint Goal).
- Sprint Planning: Select architecture tasks (e.g., “Develop Application Architecture Model”) for a Sprint.
- Incremental Delivery: Release architecture artefacts iteratively (e.g., a subset of the Technology Architecture per Sprint).
4. Roles and Responsibilities
| TOGAF Role | Scrum Role | Responsibilities |
|---|---|---|
| Enterprise Architect | Product Owner (or Scrum Team Architect) | Prioritises architecture backlog |
| Architecture Board | Stakeholders (in Sprint Reviews) | Reviews EA increments |
| Scrum Master | Facilitates Agile TOGAF process | Removes blockers |
5. Practical Implementation Steps
Sprint 0 (Preliminary Phase):
- Define EA governance, tools, and Scrum team structure.
- Create a high-level Architecture Vision (Epic).
Architecture Sprints (Phases A-D):
- Each Sprint delivers a piece of the architecture (e.g., Business Process Models in Sprint 1, Application Landscape in Sprint 2).
- Use Sprint Reviews for stakeholder feedback.
Migration Planning (Phase E-F):
- Prioritise transition architectures in the backlog.
- Use Scrum to plan implementation steps (e.g., “Migrate System X” as a Sprint Goal).
Implementation (Phase G):
- Deliver architecture-guided solutions in development Sprints.
- Validate against EA principles in Definition of Done.
Continuous Improvement (Phase H):
- Reflect on architecture adoption in Retrospectives.
- Update EA backlog based on feedback.
6. Tools & Techniques
- Backlog Management: Jira, Azure DevOps (tag TOGAF-related items).
- Modelling Tools: ArchiMate, Lucidchart (integrated into Sprint work).
- Governance: Embed EA checks in Sprint Reviews/Retrospectives.
7. Challenges & Mitigations
| Challenge | Solution |
|---|---|
| TOGAF’s documentation-heavy | Focus on “just enough” architecture per Sprint. |
| Stakeholder alignment | Regular Sprint Reviews with EA Board. |
| Balancing agility vs. governance | Define lightweight EA guardrails. |
8. Example Sprint Cycle
- Sprint Goal: “Define Core Business Capabilities Map.”
- Tasks:
- Model business processes (BPMN).
- Validate with stakeholders.
- Update Architecture Repository.
- Outcome: A draft Business Architecture artifact (refined in next Sprint).