~/talk

Effective DevOps for Organizations

links:none on file
slides:none on file

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

  1. 0:00Introduction
  2. 3:39Defining DevOps challenges
  3. 7:09Five ideals of DevOps
  4. 10:40Locality and simplicity
  5. 21:22Focus flow and joy
  6. 30:12Improving daily work
  7. 39:52Psychological safety
  8. 44:07Customer obsession
  9. 52:48Long-term DevOps success
  10. 53:09Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.