Architecture Modernization: Aligning Software, Strategy & Structure
summary
Argues modernization is a portfolio decision, not a rewrite, and shows five concrete tools: Listening tours, Impact mapping, Wardley Mapping, EventStorming and a modernization strategy selector, with roleplay and workshops (3–5 days, one ran with ~60 people) to pick what to change. Gives numbers: OpenTable did a 9‑month stop‑the‑world rewrite, one case cuts ingestion time by 80%, and Pendo claims ~80% of features are rarely used. Recommends 3–6 months for a first deliverable and an enabling team to keep work moving.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:40Why should a company modernize its architecture?
- 5:58Summary
- 6:22Talk overview
- 7:28Architecting for flow
- 17:415 essential tools for architecture modernization
- 18:00No 1: Listening (tours)
- 22:51No 2: Impact mapping
- 24:46No 3: Wardley Mapping
- 29:53No 4: EventStorming
- 32:37No 5: Modernization strategy selector
- 34:09Kickstarting & enabling architecture modernization
- 44:25Wrap-up
- 46:34Outro
related talks
40mTowards Effective Execution of Architecture Modernization
01h 00mHow to Make Better Modernization Decisions
59mArchitecture Modernization Anti-Patterns: The Cost of Good Intentions
58mSoftware Modernisation
48mContinuous Modernization
30mModernization: Taming the legacy and keeping the new house clean
47mRefactor Without Breaking Everything: Anatomy of Incremental Modernization Patterns
44m10 Lessons for Enterprise Code Modernization with OpenRewrite & Moderne