#Devops Journey
summary
Microsoft reports moving 82,000+ Microsofties onto VSTS and running about 40 feature crews inside an ~800-person org using three-week sprints with a fourth-week progressive deployment across seven rings. The engineering model merges dev and test roles, enforces one master branch with feature flags, and runs roughly 70,000 tests per PR build (mostly L0/L1) so PRs fail fast; teams block new features if technical debt exceeds thresholds. The process is incremental and still evolving.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 3:46Internal Journey
- 4:58How we started
- 8:56Why did it work
- 9:47Solution
- 14:48Dan Pink
- 15:48Wikipedia
- 16:28Guiding Principles
- 18:20Strategy Planning
- 26:45Organizational Changes
- 29:19Test Landscape
- 31:13Backend
- 33:27Release
- 35:14Feature Flag
related talks
44mDevOps at Microsoft: Our Internal Transformation Story
06mGetting VSTS to "Production"
49mOur DevOps journey – Microsoft’s internal transformation story
01h 02mEffective DevOps for Organizations
33mMoving 75,000 Engineers To DevOps On The Public Cloud
07mWhat we learned moving 65,000 Microsofties to DevOps...
01h 01mAgile Evolution: An Enterprise transformation that shows that you can too
01h 02mBuild a DevOps Culture: Microsoft's Journey to adopt an Agile Mindset and DevOps culture
