Case Study: Tools and Strategies for Tackling Legacy Practices
summary
A CTO used Wardley Maps, Simon Brown’s C4 model and Domain-Driven Design (strategic design and context mapping) to tackle a failing monolithic system and the organizational practices that created it. The talk covers how to plan, communicate and challenge strategies, high-level overviews of C4, DDD strategic design and context mapping, Wardley Maps (landscape), and some startup software development anecdotes.
AI-written summary · about
chapters (17)
- 0:00Problem introduction
- 1:24Water Law project context
- 4:14Initial project discovery
- 9:48Infrastructure and servers analysis
- 12:38Development practices survey
- 13:19Domain-Driven Design intro
- 17:13Subdomain and core domain mapping
- 21:48Project organization and dependencies
- 22:11Conway's Law implications
- 25:46World Maps intro
- 26:49Value chain and practice evolution
- 35:10World Maps decision-making
- 39:26Technical practices and dev problems
- 41:55Bottleneck analysis
- 43:40Improvement strategy and changes
- 45:28Final strategy and resistance
- 47:12Summary and conclusions
related talks
34mPractical Tools and Strategies for Tackling Legacy Practices
35mGuiding teams, and shaping a portfolio using Wardley maps & DDD
44mArchitecture for Flow - Wardley Mapping, DDD, and Team Topologies
45mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
41mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
32mApplying Domain-Driven Design in legacy systems
47mArchitecture for Flow with Wardley Mapping, DDD, and Team Topologies
56mOptimizing for a fast flow of value with adaptive, socio-technical systems