The Agile Architecture Roadmap
summary
Describes a concrete process: create an architecture roadmap parallel to the product backlog, track epics and break them into incremental stories, and run combined sprints where three distributed teams share one sprint capacity. Uses Jira GreenHopper to show dashboards and estimates; the org reserves 20 of 100 release points for architecture work. Introduces an architecture owner who grooms stories, runs proof‑of‑concept sprints, and produces metrics so priorities, costs and progress become visible and negotiable.
AI-written summary · about
chapters (9)
- 0:00Introduction and motivation
- 10:00Traditional architecture limits
- 16:39Business value vs architecture
- 22:10Introducing architecture owner
- 27:45Sprint integration and proof of concept
- 31:42Tooling and roadmap demo
- 36:37Challenges and benefits
- 41:29Best practices and communication
- 44:18Q&A and closing
related talks
01h 02mWhy We Need Architects (and Architecture) on Agile Projects
01h 03mAgile Software Architecture
40mIs it possible for enterprise architects to be really agile?
38mAgile Architecture
51mWhy We Need Architects (and Architecture) on Agile Projects
01h 00mAgile Project Management Anti-Patterns
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World
48mDown the Ivory Tower towards Agile Architecture