Our DevOps journey – Microsoft’s internal transformation story
summary
Microsoft reduces releases from three years to three weeks by reshaping people, process and product: 40 co‑located scrum feature teams, rotation and a SWAT rotation for deployments; continuous deployment into six deployment rings with safe rollouts, 79,000 unit tests run per pull request and six hundred merges a day; feature flags replace rollbacks; telemetry (about seven terabytes daily) and petabytes of logs enable zero‑downtime upgrades and monitored, incremental rollouts instead of big freezes.
AI-written summary · about
chapters (4)
- 0:00Start
- 2:11DevOps is the union of people, process, and products to enable continuous delivery of value to our end users
- 39:43Deployment principles No down time Fully automated Joint ownership between engineering and ops Decoupled services clear contracts Feature flags
- 44:31Feature flags Decouples engineering and marketing Control exposure Granular Controlled via PowerShell Supports early feedback, experimentation Conferences, launches
related talks
44mDevOps at Microsoft: Our Internal Transformation Story
01h 02mBuild a DevOps Culture: Microsoft's Journey to adopt an Agile Mindset and DevOps culture
53mKeynote: Enterprise transformation (and you can too)
37mFrom Waterfall to Agile
44m#Devops Journey
07mWhat we learned moving 65,000 Microsofties to DevOps...
31mThe 10 Year Microsoft Journey To Continuous Flow
01h 01mAgile Evolution: An Enterprise transformation that shows that you can too
