Cultivating architecture
summary
Large orgs keep team autonomy but need concrete governance: use trade-off sliders to prioritise architectural requirements, run a lighthouse/boats workshop (goals, winds, anchors, risks) to surface cross-team concerns, and codify ~5 guiding principles (John Lewis uses 18 as reference; aim smaller). Structure principles with TOGAF-style rationale → implications and map practices on a technology radar (adopt/trial/assess/hold). Rely on State of DevOps / Accelerate findings: autonomy predicts trust and voice, so measure team trust, adoption, and delivery metrics to iterate rather than prescribe.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:21Why autonomy
- 2:51Challenges
- 4:03Governance
- 8:19Architectural Requirements
- 9:48Prioritize
- 10:41Alignment
- 10:59Architecture Principle
- 11:49Example
- 12:20Principle Content
- 13:27John Lewis Principles
- 14:40Strategic goals
- 15:07Principles
- 17:40Three approaches
- 19:28Retrospective
- 21:38Rational Implications
- 24:13Sensible Defaults
- 24:59State of DevOps
- 25:32Autonomy
- 26:50Learning culture
- 27:19Principals
- 28:15Conclusion
related talks
49mCultivating Architecture
40mPractices from trenches for embracing evolutionary architecture in wild
25mLeapfrogging from Good to a Great Architect
48mDown the Ivory Tower towards Agile Architecture
45mTeam and Software: Making an Impact as an Architect
35mOrganization: A Tool for Software Architects
41mCultivating Architecture in an Agile World
46mArchitecture & DevOps