5 Agile practices every SRE team should adopt
summary
Team keeps three-week sprints but drops ritualized scrum and uses the retrospective as the main lever to iterate how work happens; standups run twice-weekly or asynchronously in Slack for distributed shifts; planning becomes a weekly 30‑minute backlog rebalance that re-prioritizes toil-busting work instead of committing to velocity; SRE-written automation has test suites to avoid wiping customer data; pair programming is standard for onboarding and incident tasks to raise confidence and share knowledge.
AI-written summary · about
chapters (4)
related talks
25mSRE Guiding Principles & Transformational Framework
28mHow to Do SRE When You Have No SRE
42mDemystifying SRE and DevOps
25mUnleashing the potential of SRE for modern operations
37mSRE & Product Management: How to Level up Your Team (and Career!) by Thinking like a Product Manager
27mUnified Theory of SRE
30mWhen Is SRE Right For You?
27mHow Google SRE and developers work together
