Q & A

on YouTube ↗10m

" summary

Shows how to use a coarse Eisenhower-style rubric plus tracking to choose work, treat SREs as first-line product feedback for the platform, and let them prototype platform code so issues get fixed faster. Recommends spikes to answer unknowns, rescuing and splitting stalled tickets, and preferring kanban for interrupt-driven ops while using scrum for planned scope. Emphasizes visible dashboards and reducing WIP so status is discoverable without daily standups.

AI-written summary · about

" chapters (6)

1. 0:00Intro
2. 0:55Complexity and Difficulty
3. 2:17Splitting a Team
4. 3:46Standups
5. 4:27Time Estimates
6. 6:49Scrum vs Kanban

" related talks

• 37mSRE & Product Management: How to Level up Your Team (and Career!) by Thinking like a Product ManagerJen Wohlner · SREcon19 Europe/Middle East/Africa
• 21mLive Q&A Session #1Joe Gasperetti · Reliability @Scale 2024
• 30mSRE & Product Management: How to Level up Your Team (and Career!) by Thinking like a Product ManagerJen Wohlner · SREcon19 Americas
• 20m5 Agile practices every SRE team should adoptManuel Dewald · DevConf.CZ 2021
• 29mDriving clarity in ambiguous projectsScott Triglia · StaffPlus New York 2022
• 51mHacking Your ProcessesRichard Wellum · NDC Minnesota 2019
• 32mPanel discussion: The journey to building effective engineering teamsXConf Australia 2023
• 46mCracking the cadence of your software engineering 1:1sAdrienne Lowe, Spencer Norman, Alexandra Sobhani, Kwasi Ohene-Adu · LeadDev Live Summer 2020