Does a Phase 1 / Phase 2 Approach Ever Actually Work?
summary
Argues that phased releases often stall — the myth of 2.0 — and shows concrete examples: Robinhood ships a Bitcoin UI placed above stocks with over 1 million people in line before buy/sell is fully live, Microsoft Dynamics uses 1.0/2.0/3.0 roadmaps, and teams split huge rewrites into measured increments. Recommends splitting big features to deliver measurable value early, use phases for API integrations or geographic rollouts, avoid half-finished UI relaunches, and guard against a culture that relegates hard work to phase two.
AI-written summary · about
chapters (4)
- 0:00Start
- 6:14Examples of Phased Approaches
- 20:46When to Use a Phased Approach
- 39:03When NOT to Use a Phased Approach
related talks
39mMinimal Viable Architecture
01h 29mMonolithic Delivery
32mA Tale of Two Cities - Early Adoption Stories
53m#NoProjects Beyond Projects - Why Projects Are Wrong & What To Do Instead
29mFrom big to small and back again
32mSailing through Digital Transformation
45mPlatform Engineering: Lessons from the Rise and Fall of eBay
24mFrom Startup to Scale Up Designing for Growth from Day One