Architecture Modernization: Aligning Software, Strategy, and Structure
summary
Covers concrete modernization moves: using value streams and event storming to find domain-aligned boundaries, impact mapping and wly mapping (evolution mapping) to prioritize, plus using CodeScene to spot coupling; shows OpenTable moving from monthly releases to multiple daily deployments in about a year and an Ice/royalty system cutting ingestion time by 80% and making matching 5x faster. Recommends 3–6 month “first slice” proofs, 3–5 day kickoff workshops with cross‑stakeholders, and an enabling team to coach other teams rather than centralize architecture.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:00Big Companies
- 4:23Open Table
- 5:45Why companies need to modernize
- 7:22What this talk covers
- 9:12What is flow
- 12:05Four Guiding Principles
- 14:35Ice
- 16:17Beat Your Parity
- 17:21Full Stack Modernization
- 19:59Listening
- 22:05Impact Mapping
- 26:25Anticipate
- 27:45Event Storming
- 29:21Modernization Strategy Selector
- 30:51CodeScene
- 34:52Kickstarter Workshops
- 38:08Recap
related talks
01h 12mArchitecture Modernization: Aligning Software, Strategy, and Structure
48mArchitecture Modernization: Aligning Software, Strategy, and Structure
48mArchitecture Modernization: Aligning Software, Strategy, and Structure
40mArchitecture Modernization with DDD
46mMaster Software Architecture: From Simplicity to Complexity
30mHow to make better modernization decisions
38mModern Enterprise Architecture: Architecting for Outcomes
15mHow to build a winning app modernization strategy & deliver on it