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
While most of us have spent the past several months struggling to adjust to the new normal of being 100% remote, Molood Ceccarelli has not. In 2016, Molood realized that even though Agile coaches and thought leaders frequently talk about how important it is for all of us to be co-located, most of her work was remote and she’d been able to figure out how to work with agile teams. This realization inspired her to start Remote Forever and refocus her efforts 100% on helping people get better at working remotely.
In this episode of the podcast, Molood and I discuss some of the key things she has learned in developing her ability to work remotely, how she runs experiments to continue improving at working this way and how she stays inspired with the work she does. We also discuss the upcoming 2020 Remote Forever Summit.
In 2017 Molood put together the first Remote Forever Summit. She was expecting a small crowd at the event but there were 2,700 registrants. Last year there were over 10,000. This year, the fourth annual Remote Forever Summit will take place from November 11-17. The event has speakers from all over the world who will be leading sessions on a wide range of topics relevant to anyone working remotely including how to develop a more genuine connection with those you interact with online, how to inspire successful, collaborative teams, how to create an intentional remote culture, and how to manage Agile transformation online.
Also, you can attend the conference for free.
Remote Forever Summit https://remoteforeversummit.com/
What do you do when they start asking for cost per point?
This issue often arrives wrapped in requests that are pure in their intent and seem to be reasonable requests from the business…
How much are we spending each month and how many points are we delivering for that spend?
Since we are now estimating work in User Story Points, we need to be able to determine how much to charge for the work that clients are asking for. So how much does a point cost us?
We need to evaluate the change requests so we can decide which ones to move forward with and which ones to reject. We’re estimating them in User Story Points, which gives us a relative idea of risk, complexity, and effort, but not cost. We need to be able to translate points to dollars so we can understand if the value we’d receive from the change is worth the cost.
I had a student recently who was qetting requests like this from the business, so I asked Agile Coach Troy Lightfoot to join me for a podcast where we could unpack the issues that often come with the cost per point question, the pros and cons of tracking it, and some things to take into account when you formulate your response to the request.
Links from the Podcast
Since the Covid-19 Quarantining began, we’ve all had to adjust to our work-life taking place 100% online. Whether you are working in a traditional environment or in Agile, this change has impacted your teams’ ability to engage, learn, and collaborate online. In this episode of the podcast, I am joined by Braden Cundiff who works in the International Division of McGraw-Hill Education serving in a Product Ownership role for international education products.
Braden’s work involves creating tools and products that are used in collaborative, educational environments all across the globe. He also has a background that includes teaching, agile coaching, and transformation. This allows him to offer a unique perspective on how to create an effective online environment for your teams.
At the start of the interview, Braden and I also discuss his role as a Product Owner and he offers his take on the one question that comes up in every single Product Owner class I teach … “How do I get better at saying ’No’?”
This is not part of the regular blog/podcast, but it might be interesting, so I'm sharing the link... Jessica Wolfe, Derek Huether and I recorded a Zoom call discussing what we'd learned from our first week of working in quarantine. We each experienced things that week that caught us by surprise. In some cases, those surprises were pretty awesome. In other cases, not so much.
We're going to try and make this an ongoing thing.