Effective DevOps for Organizations
summary
Shows how Azure DevOps reorganizes into 40 feature teams of about 10–12 engineers with delegated authority, drops long-lived branches for trunk-based development, and introduces a rotating shield team to protect flow. Engineering scorecards enforce actionable metrics (bug cap = five per dev, LSIs prioritized), test strategy moves to L0 units (about 84,000 L0 unit tests run with selective test impact to cut feedback from ~48 hours to ~23 minutes), and feature flags plus private previews validate customers — the result: a jump from ~22 to ~320 features/year.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:39Defining DevOps challenges
- 7:09Five ideals of DevOps
- 10:40Locality and simplicity
- 21:22Focus flow and joy
- 30:12Improving daily work
- 39:52Psychological safety
- 44:07Customer obsession
- 52:48Long-term DevOps success
- 53:09Q&A
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
44m#Devops Journey
01h 01mAgile Evolution: An Enterprise transformation that shows that you can too
33mMoving 75,000 Engineers To DevOps On The Public Cloud
01h 01mPragmatic DevOps - How and Why
54mEffective DevOps for Organizations
37mFrom Waterfall to Agile
