A few weeks ago while I was teaching a CSM class, I got a Slack message from Ron Quartel pointing me to a tweet by Ryan Ripley. The tweet said “If you are sitting in a Scrum Training class and the trainer starts teaching Story Points, you should 1. Get up. 2. Demand Your Money Back, and 3. Walk out. You're wasting your time.
Here is a link to the tweet: https://bit.ly/3XsfPAP
I should mention I was just about to cover Story Points and I used Ryan's tweet in class as part of our conversation.
As soon as I saw Ryan's tweet, I DM'd him asking if we could do a podcast about it. I did this because A) I have a lot of respect for Ryan and value his opinion, B) earlier in my career I spent about 4 years fighting against Story Points, C) I do teach them in class because I believe that (used properly) they can be incredibly valuable to a Scrum Team, and D) I love getting into debates on topics I feel strongly about with really smart people who might be able to change my mind
So this podcast is Ryan and I talking through his reason for throwing shade on Story Points, my reasons for standing up for them, and the reasons I feel comfortable saying that we are aligned about why Story Points are good AND evil.
The Scrum Guide got an update last November and one of the concepts introduced was the Product Goal. The Scrum Guide says:
“The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define “what” will fulfill the Product Goal.
The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next.”
For some, myself included, taking that basic definition, extending it, and creating clarity on how the Product Goal fits in with other ways we talk about the Product Backlog has been challenging. So, I reached out for some help...
In this episode of The Reluctant Agilist, I'm joined by Ryan Ripley. Ryan is the co-author of "Fixing Your Scrum", the co-host of the Agile for Humans podcast and he's also a Professional Scrum Trainer. During the conversation, Ryan and I dig into what exactly the Prout Goal is, how teams can use it to deliver value and how it fits in with some of the other aspects of the Product Backlog.
If you'd like to check out the podcast Ryan and I recorded on his book Fixing Your Scrum you can find it here: https://bit.ly/3vIWNJq
Links from the Podcast
Ryan Ripley wears many hats. He's a Professional Scrum Trainer, an Agile Coach, the creator of the Agile for Humans podcast, a blogger, a speaker, and now... author!
Last month, Ryan and Todd Miller released Fixing Your Scrum (https://amzn.to/2Pi46En), a book chock full of real-life stories from two seasoned Agile coaches who spend their days helping organizations, teams, and individuals find a better way to work.
In this episode of The Reluctant Agilist, Ryan and I talk about the book, what motivated them to write it, and how it can help you figure out ways to address some of the issues you and your Scrum Team are facing.
During the interview, Ryan and I also discuss what led him to become a Professional Scrum Trainer and why he finds teaching Scrum and Agile to be such a rewarding way to spend his days.
If you haven't checked out Ryan's podcast Agile for Humans, that is something you definitely want to do. ryanripley.com/agile-for-humans/
Fixing Your Scrum by Ryan Ripley and Todd Miller https://amzn.to/2Pi46En
Fixing Your Scrum by Ryan Ripley and Todd Miller
Live in NYC