Ignite - Product Owners are Reliabilibuddies

on YouTube ↗05m

" summary

Teams identify system boundaries, define customer-facing capabilities, and agree on a plain-language definition of "available." SLIs and SLOs get instrumented and tracked as real percentages of customer-facing availability, with failures logged and baselines established. Risk matrix sessions map likelihood and impact from incident history, producing risk-ranked architectural diagram output and likelihood/impact ratings. Prioritized fixes become actionable work by adding two backlog tickets per risk and scheduling regular reviews so product owners can balance reliability with feature delivery.

AI-written summary · about

" chapters (11)

1. 0:00Intro
2. 1:24METHODOLOGIES!
3. 1:54SLIS: A SIMPLE RECIPE
4. 2:09SLIS: FIRST, IDENTIFY WHAT MATTERS
5. 2:24WHAT DOES "AVAILABLE" MEAN?
6. 2:40SLIS: MEASURE THE CAPABILITY, BASELINE THE SLO
7. 2:57SLIS: REVIEW & ITERATE
8. 3:24RISK MATRIX!
9. 3:54WHAT COULD POSSIBLY GO WRONG?
10. 4:09DOCUMENT!
11. 4:24PRIORITIZE!

" related talks

• 06mIgnite - A DevOps Necessary Evil: MarketingClaudia Ring · DevOpsDays Rockies 2016
• 06mIgnite: A day in the life of an OSS maintainerPatrick Stephens · Open Source Monitoring Conference 2024
• 41mProduct Owner & Developer: An Unexpected JourneyRené Hoffmann · code.talks commerce 2018
• 17mVisualization to the rescueBartosz Zbierajewski, Wojciech Buras · AgileByExample 2016
• 38mBreaking Down Silos Between Platform and Product TeamsRebecca Fitzhugh · DPE Summit 2025
• 52mEmpowerment in the Software Delivery LifecycleMartin Reynolds, Alan Shimmel, Cheryl Razzell, Jenny Donnelly · {unscripted} 2021
• 06mIgnite: Programming your infrastructureDave Long · DevOpsDays Philadelphia 2016
• 44mEnhancing the Performance of Engineering TeamsKaterina Trajchevska · code.talks 2023