Shortening the Architectural Feedback Loop
summary
Claims that shortening architecture feedback loops speeds uncertainty reduction and yields better, more adaptable designs, and gives five concrete practices: focus on architectural decisions as the primary deliverable, publish each decision in a decision register or Jira ticket, solicit immediate comments via Confluence or a Wiki, and keep docs minimal rather than a 50+ page template. Shows a working pattern where a macro generates a snapshot from the decision register for approvals, and argues architects should get involved in delivery to validate decisions quickly.
AI-written summary · about
chapters (16)
- 0:00Intro
- 1:40Combining Architecture with agile working; conflicting paradigms?
- 4:10Benefits of combining agile & architecture
- 7:44Two architecture feedback loops
- 11:03The cone of uncertainty
- 13:10Why shorten architectural feedback loop?
- 14:015 tips for shorter feedback loops
- 15:50Architectural decisions are your primary deliverable
- 19:25Continuously share concerns & decisions
- 20:13Invite immediate feedback from stakeholders
- 23:08Simplify your architecture documentation template
- 28:03Goal-driven architecture documentation
- 30:18Get involved in delivery
- 32:25Survey results about shortening feedback loop
- 33:37Conclusion
- 34:03Outro
related talks
49mCultivating Architecture
30mCommunicating and documenting architectural decisions
41mArchitecture and Agility: A Shared Skillset!
24mThe too many faces of Architecture
37mArchitecting for Tomorrow: A Pragmatic Perspective
51mWhy We Need Architects (and Architecture) on Agile Projects
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World
28mThe lean architect: Experimenting your way to better decisions