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
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.
When I am teaching CSM and CSPO classes I frequently get questions from students who have trouble understanding how work flows from the release level down through product backlog items like User Stories on down to the task level. I do cover this in class but for some, it is not so easy to see.
If you'd like to reach out to Judy with follow up questions, here is her contact info:
This episode features a student question and a special appearance by Adam Weisbart.
I recently had a student in class who was struggling to get her team to participate during retrospectives. This is a fairly common problem for teams that are either trying to get the hang of how to run a retro, or teams that may have stuck with a particular tactic for so long that it has stopped working.
I invited Adam Weisbart to join me for the podcast. If Adam's name sounds familiar, it may be because you've taken a class from him, seen him speak at a conference, watched the video "Sh*t Bad Scrum Masters Say", or because you've used his Agile Adlibs or his retrospective facilitation kit, Recess. (We'll be spending time on those last two during the interview.)
If you've got teams that aren't fully engaging during your Retrospectives, you are not alone. This podcast has some ideas that should help you get that turned around.
Urs Reupke is a Certified Scrum Trainer and Agile Coach who works for the Hamburg-based Agile Consultancy It-Agile. A lot of Urs’s time and attention is focused on the work he does coaching management and providing leadership consulting as they move towards adopting a more Agile approach to work.
If you’d like to contact Urs, here is how you can reach him