The 10 Year Microsoft Journey To Continuous Flow
summary
Describes a ten‑year shift from four‑year boxed releases to a hybrid SaaS/on‑prem model with a single code base serving millions of accounts, triweekly cloud deployments and quarterly on‑prem rollups. Claims include 15x technical‑debt reduction and 2x schedule speedup, three‑week sprints, cross‑discipline feature crews kept 12–18 months, fully automated deploys with feature flags and scale‑unit canaries across Azure regions, no maintenance windows, monthly service reviews driving MTTD/MTTR and funnel experiments that raised signup conversion from ~30% to ~50%.
AI-written summary · about
chapters (5)
- 0:00Start
- 0:03The 10 Year Microsoft Journey To Continuous Flow Sam Guckenheimer Microsoft
- 7:15Scrum Teams (a.k.a. "Feature Crews") Cross-discipline 8-12 people Led by their triad Intact for 12-18 months Autonomous backlog
- 18:00Feature Flag Pattern Al code is deployed, but feature flags control exposure Flags provide runtime control down to individual user Users can be added or removed with no redeployment Enables dark launch Mechanism for progressive experimentation and refinement
- 30:40DEVOPS ENTERPRISE SUMMIT
related talks
49mOur DevOps journey – Microsoft’s internal transformation story
44mDevOps at Microsoft: Our Internal Transformation Story
53mKeynote: Enterprise transformation (and you can too)
01h 01mFrom one release per quarter to 30 times a day
37mFrom Waterfall to Agile
32mEnterprise transformation (and you can too)
01h 02mBuild a DevOps Culture: Microsoft's Journey to adopt an Agile Mindset and DevOps culture
07mWhat we learned moving 65,000 Microsofties to DevOps...