Architecture Modernization: Aligning Software, Strategy, and Structure
summary
Legacy systems slow flow: some teams deploy once a month, competitors iterate faster, and Pendo estimates ~80% of features are unused. Modernization combines domain work, UX and targeted tech changes — one royalty-processing modernization cuts ingestion time by 80% and speeds matching 5x. Practical tools are listening tours, impact mapping and event storming plus Wardley-style evolution maps; use a timeboxed first slice and an enabling team to keep progress going.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:53Why companies modernize
- 3:07The risks of legacy systems
- 6:40Architecture for flow
- 8:21Value streams and domains
- 19:08Essential modernization tools
- 26:38Advanced domain techniques
- 34:45Getting started effectively
- 39:02Kickstarter workshops and teams
- 42:56Wrap-up and Q&A
related talks
48mArchitecture Modernization: Aligning Software, Strategy, and Structure
01h 12mArchitecture Modernization: Aligning Software, Strategy, and Structure
40mArchitecture Modernization: Aligning Software, Strategy, and Structure
40mArchitecture Modernization with DDD
30mHow to make better modernization decisions
15mBuilding a Modernization Strategy
47mApplication Modernization: Renovating a House While You Live In It
43mBack to the Future