Does Your Team Really Understand What Is Valuable? w Adam Weisbart
Categories:
Adam Weisbart,
Agile,
Backlog Refinement,
Dave Prior,
drunken pm radio,
drunkenpm,
Prioritization,
Product Ownership,
Scrum,
value,
Weisbart
Categories: Adam Weisbart, Agile, Backlog Refinement, Dave Prior, drunken pm radio, drunkenpm, Prioritization, Product Ownership, Scrum, value, Weisbart
In this episode of the podcast Adam Weisbart and I take on the topic of how you can get clarity on value, how can you make sure your backlog reflects that understanding of value and how can you ensure the team has awareness of what “value” means to the organization. During the interview, Adam also shares some details about his upcoming Agile Virtual Summit (Bite Size) which is taking place on October 14, 2021. The event is free and there are going to be some great speakers, including people like Jim Benson, Richard Cheng, and Melissa Boggs who have all been guests on the podcast. You can learn more about the Agile Virtual Summit (Bite-Size!) and sign up using the link below. drunkenpmradio · Does Your Team Really Understand What Is Valuable? w Adam Weisbart Agile Virtual Summit (Bite-Size) If you’d like to contact Adam:
|
Catching up with Melissa Boggs
What is truly powerful about this interview is how open Melissa is about the things she learned about herself on this journey. She offers a great example of brave vulnerability and shows how, if you are in the business of helping others transform, you have to be willing to develop an inner sense of personal agility as well. drunkenpmradio · Catching up with Melissa Boggs Links from the Podcast
Contacting Melissa
|
The Product Goal with Ryan Ripley
“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. drunkenpmradio · The Product Goal w Ryan Ripley 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
|
Resistance to Change with Christine Converse and Ross Beurmann
drunkenpmradio · Resistance to Change with Christine Converse and Ross Beurmann CONTACTING CHRISTINE AND ROSS If you’d like to reach out to Christine or Ross, here are some ways to reach them: Christine Converse
Ross Beurmann
|
What To Do When They Want To Know Cost Per Point w Troy Lightfoot
Categories:
,
Agile,
Agile Estimation,
Agile Uprising,
Dave Prior,
drunken pm radio,
drunkenpm,
Scrum,
The Reluctant Agilist,
Troy Lightfoot
Categories: , Agile, Agile Estimation, Agile Uprising, Dave Prior, drunken pm radio, drunkenpm, Scrum, The Reluctant Agilist, Troy Lightfoot
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? or 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? or 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. drunkenpmradio · What To Do When They Want To Know Cost Per Point w Troy Lightfoot Links from the Podcast
Contacting Troy
|