Tools over Processes over People... Or Not?
summary
A high-performing DevOps team collapses under churn and burnout, then survives a big reset that redefines values and takes about nine to ten months to stabilize. Recommendations: form service/product teams sized four to six (absolute max 10, the two pizza rule), keep teams together ≈1 year, install strong Scrum Masters/agile coaches, and create a team API to structure requests. Example: three engineers run a fully automated build pipeline for ~10,000 customers.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:16Team burnout story
- 8:27Agile Manifesto principles
- 10:34Intrinsic motivation research
- 13:40Agile anti-patterns
- 15:48Adopting Agile and DevOps
- 17:37Building service teams
- 20:08Autonomy in teams
- 21:55Mastery through mistakes
- 23:42Team purpose and goals
- 25:07Agile mindset
- 26:10Q&A
related talks
22mOrganising a fast growing DevOps team a real life use case
28mBreaking the Trenches: Nurturing a Continuous Improvement Culture in DevOps
37mFrozen DevOps? Team Topologies Comes to the Rescue!
33mBuilding Sustainable Teams to Handle Uncertainty
17mBeyond DevOps – Holistic transformations in uncertain times
42mFrom Chaos to Control, from Control to Freedom
20mDoing Things the Hard Way
52mDevops @Scale