Architecture Modernization: Aligning Software, Strategy, and Structure
summary
Argues modernization is a business problem not just a tech swap and shows concrete tools and metrics: use value streams to align teams and boundaries, run listening sessions and impact mapping to tie changes to business outcomes, apply event storming and WLY mapping to decide where to invest, and run CodeScene on VCS to find coupled churn. Examples: ICE cuts ingestion time by 80% and 5x matching productivity; Pendo-style analysis suggests ~80% of features are rarely used. Recommends a kickoff workshop, a temporary enabling team, and delivering a first slice in 3–6 months.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:09When modernization is not necessary
- 3:40Risks of legacy systems
- 5:24Business drivers for modernization
- 7:11Modernization beyond tech
- 8:36Value streams in architecture
- 10:00Four architecture fundamentals
- 12:55Case study: Ice outcomes
- 14:03What to modernize vs discard
- 15:30Full-stack modernization
- 17:38Modernizing processes and domains
- 20:08Tool 1: Listening to stakeholders
- 25:08Tool 2: Impact mapping
- 27:58Tool 3: Wily mapping
- 31:51Tool 4: Event storming
- 35:44Tool 5: Modernization strategies
- 37:51Honorable mention: CodeScene
- 38:55Starting modernization timelines
- 41:04Risk versus reward
- 43:32Kickstarter workshops
- 46:46Sustaining momentum
- 48:33Summary
- 51:48Q&A
related talks
48mArchitecture Modernization: Aligning Software, Strategy, and Structure
40mArchitecture Modernization: Aligning Software, Strategy, and Structure
48mArchitecture Modernization: Aligning Software, Strategy, and Structure
40mArchitecture Modernization with DDD
30mHow to make better modernization decisions
46mMaster Software Architecture: From Simplicity to Complexity
47mApplication Modernization: Renovating a House While You Live In It
15mBuilding a Modernization Strategy