How comic strips connect agile and architecture
summary
Uses comic strips to expose where agile transformations and architecture fail and how to fix them, backed by a 50,000-follower project and a published book. Argues architects must deliver an evolvable architecture with concrete fitness functions (performance, security, cyclomatic complexity) and shows a concrete half‑star rating example implemented with a toggle router to enable additive change. Recommends evolutionary DB practices, warns against resume‑driven tech choices, shifts metrics from vanity numbers to lead time, NPS and eNPS, and redefines product owner and scrum master roles for flow.
AI-written summary · about
chapters (16)
- 0:00Introduction and welcome
- 3:02Mission of comic strips in agile
- 7:15Evolving architecture over ivory towers
- 11:31Evolutionary architecture examples
- 14:40Coupling and technology stack traps
- 16:27Agile transformation pitfalls
- 20:41Management misconceptions in agile
- 24:32Annual budgeting vs agility
- 26:59The frozen middle dilemma
- 29:54Scrum Master role expectations
- 31:41Developer bottlenecks and bottlenecks
- 34:09Developer freedom and quality
- 36:17Empowered product owners
- 38:45Dependencies and scaling frameworks
- 40:47Avoiding agile islands
- 41:50Summary and key takeaways
related talks
47mA puppy dies when agile meets reality
38mAgile Architecture
01h 00mAgile Architecture
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World
51mWhy We Need Architects (and Architecture) on Agile Projects
47mAgile and Architecture: a meeting of the undead
49mAgile and Architecture: a meeting of the undead
48mDown the Ivory Tower towards Agile Architecture