Today we will speak to Kit Merker, COO of Nobl9 about Service Level Objectives (SLO). Kit provides down-to-earth advice for adopting and using SLOs to benefit teams AND organizations. 

Kit’s bio:

This image has an empty alt attribute; its file name is kit-merker-head-shot-1.png

Kit Merker’s 20+ year career spans product management, engineering, evangelism and community-building roles at Google, Microsoft, JFrog, and the governing board of the Cloud Native Computing Foundation (CNCF). He is currently Chief Operating Officer for Nobl9, driving community and growth for service reliability for enterprise development teams.

Contact information:

Re-Read Saturday News 

This week we re-read Chapter 6 of Project to Product  https://amzn.to/2WzvPac (Amazon Affiliate Link). In the chapter the author tells four stories of disruption — they are interesting in their own right. Still, if we look for a common thread I would suggest the communication needed to manage the balance between flow items (features, defects, risks, and debts). 

This image has an empty alt attribute; its file name is Bac4r5CiWkVs_SNsPoyNOhDPDeEBb70bpRqhs0use923_ND7bia32EGBuJxbCt8-PF6Wgf9qrX6BdlJLjMqkMHo0TL5uj1GoyYpxfQxpjKE3xi4iaQqvvbqnQM41JKOjnW-VfxvD

Catch up on previous installments:

Week 1: Foreword and Introduction – https://bit.ly/39gIt0A 

Week 2: Age of Software – https://bit.ly/2XYvqyI 

Week 3: From Project to Product – https://bit.ly/3mhwJBb 

Week 4: Introducing The Flow Framework – https://bit.ly/3lqJTwd

Week 5: Capturing Flow Metrics – https://bit.ly/3GjCffC 

Week 6: Connecting to Business Results – https://bit.ly/3BTROqQ 

Week 8: Tracking Disruptions –https://bit.ly/3neIs5h 

Next SPaMCAST 

Next week an essay on the role of the team lead in Scrum. As Mellisa Greller points out, the role of the TL is often overlooked. When a role is overlooked it causes friction. Unless you are starting a campfire, friction is not a great idea.