Software Modernisation
summary
Defines software modernization as a continuous effort to increase business agility and gives a concrete five-step approach: run cross-functional workshops, map the core value stream, pick a narrow business focus, measure with DORA metrics (deploy frequency, lead time, MTTR, change failure rate) and choose tactics — modularisation, strangler facade, refactor-in-place or parallel experiments. Calls out real constraints (a client with ~14,000 instances, 4,000 on‑premise), shows a payments parallel-architecture experiment that validates the approach, and recommends JetBrains/IntelliJ for safe refactoring.
AI-written summary · about
chapters (32)
- 0:00Introduction
- 2:55What is software modernization
- 4:46Why do we fail to make a case
- 6:47The disconnection
- 9:22Business inefficiencies
- 9:56Sustainable change
- 11:12Innovation
- 12:16Leverage technology
- 13:13Alignment
- 18:00Principles of DevOps
- 22:57Steps in an organisation initiative
- 24:30Focus your initiative
- 27:45Value stream mapping
- 28:48Understanding the current situation
- 29:40Constraints
- 30:00Metrics
- 30:19Accelerate
- 30:49Business Alignment
- 31:01Technical Alignment
- 31:57Endpoint Design Improvements
- 33:28Active Alignment
- 34:42Direction
- 35:22Incremental
- 36:24Strategy
- 38:52Architecture
- 40:10Mobilisation
- 42:43Team
- 44:28Backlog
- 44:51Summary
- 46:03Continuous Improvement Program
- 47:21Align the Business and Technology
- 48:02JetBrains Partner
related talks
47mArchitecture Modernization: Aligning Software, Strategy & Structure
48mContinuous Modernization
33mTo Refactor or Not: How to Systematically Modernize Your Java Applications
40mTowards Effective Execution of Architecture Modernization
47mRefactor Without Breaking Everything: Anatomy of Incremental Modernization Patterns
36mFrom Software to Systems: Modern Agility
38mModernization 101: A Beginner's Guide to Application Modernization and Methodology
21mTransforming Legacy Systems: A DevOps Journey to Modernization