Replatform in a Year or Die: The Tale of a Turnaround
summary
A legacy desktop accounting product gets rebuilt on top of the existing AccountRight core (a single ~4M-line DLL) with a BFF layer and a Gateway, using vertical feature slices instead of microservices, aiming to ship 407 features in ~13 months. Delivery institutes kanban-style cycle metrics (typical cycle time ~19 days) and a fast/slow lane to hit an ~8-features-per-week throughput target. The result is a big-bang web release in March 2020 that succeeds and begins migrating users off the old stacks.
AI-written summary · about
chapters (7)
- 0:00Start
- 17:01System of work (take 1)
- 18:19System of work (take 2)
- 22:53Tradeoffs in analysis
- 37:34Overlapping communication structures
- 39:46Internal tech leadership
- 40:33From a project to a platform
related talks
30mProduction › Prototype: How a Small Team Replaced a Core Platform in 90 Days
26mDevOps and Lean in Legacy Environments
42mSo You Want To Rewrite That...
40mLegacy Evolution – The Innovation Opportunity!
44mRe-Platforming The Path For Betterment
58mJourney to the Cloud - a Rearchitecting Story
41mModernizing Legacy Apps - Platforms and Strategies
48mContinuous Modernization