Intentional Architecture in Agile Organizations
summary
Company moves from three JavaScript frameworks in one product to an intentional architecture practice that standardizes components via a funded UI library (Mineral UI), pilots Clojure across services with a template service (auth, metrics, Kafka hooks) and trains via voluntary book clubs. Rollouts include rollback plans—Flow types are removed after trial—and testing is streamlined from five disparate test suites down to three, plus dedicated DevOps teams for CI/CD and user/system observability on production.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 2:26DevOps
- 3:49Communication
- 5:05Conways Law
- 5:59Intentional Architecture Goals
- 7:06What is an Architect
- 8:09Team autonomy vs team alignment
- 9:29Organizational impacts
- 11:24Technology planning
- 12:31Technology due diligence
- 14:46Case study
- 16:53Flowtype example
- 18:30Dev morale
- 22:56Agile Central
- 24:54Root Cause Analysis
- 26:07DevOps Architecture ROI
related talks
01h 00mAgile Architecture
38mAgile Architecture
48mDown the Ivory Tower towards Agile Architecture
46mArchitecture & DevOps
13mAgile Architecture: Enabling Innovation in a Rapidly Changing World
16mEveryone architect!
40mArchitecture Modernization: Aligning Software, Strategy, and Structure
46mAgility and Architecture Together – Enabling a Fast Flow of Change