Towards Effective Execution of Architecture Modernization
summary
Modernization is multi‑year, not an overnight rewrite: identify skills gaps quickly and create an architecture modernization enabling team to kickstart a few teams (example: helped 4 of 50 teams), run sequenced workshops and event storming, then encode learnings into a self‑service platform so teams scale without constant handholding. Align incentives via value streams to balance features vs modernization. Resolve domain drift by creating a shared model (collaborator → single profile → working agreement), publish RFCs and ADRs, and teams continue independently.
AI-written summary · about
chapters (11)
- 0:00Introduction to modernization
- 2:36When to modernize
- 5:32The problem after workshops
- 8:36Architectural capability gaps
- 11:47Modernization enabling teams
- 15:09AMET responsibilities
- 19:02Scaling the modernization effort
- 23:27Balancing work priorities
- 26:57Aligning organizational structure
- 31:22Unblocking dependencies
- 37:45Conclusion and recap
related talks
47mArchitecture Modernization: Aligning Software, Strategy & Structure
59mArchitecture Modernization Anti-Patterns: The Cost of Good Intentions
58mSoftware Modernisation
48mContinuous Modernization
30mModernization: Taming the legacy and keeping the new house clean
01h 00mHow to Make Better Modernization Decisions
47mRefactor Without Breaking Everything: Anatomy of Incremental Modernization Patterns
01mWe have learned how to design a modernisation facory