Estimate

Estimation and Meeting Sprint Commitments

In this episode of SoundNotes, Dave Prior and Derek Huether respond to a couple questions from students who have taken a LeadingAgile CSM and/or CSPO class over the past couple months. Here are the questions they will address in this short video podcast:

Question 1:

My team seems to have a problem with estimating and understanding the estimating concepts. The team members are accustomed to traditional waterfall projects and estimating everything in units of time. How can I help them understand estimating, but continue to complete the sprints with no PBIs (Product Backlog Items) rolling over to the next sprint?

Question 2:

I have a team lead who is skeptical of scrum, especially metrics related to the process. He doesn’t think carryover matters from sprint to sprint as long as we’re “creating value” and getting the program priorities completed. Any advice on how to convince him that metrics can be a tool for good, and that the sanctity of the sprint commitment matters?

The Best Estimating Technique

When you think of estimating and planning techniques, what method do you think of first?  Do you use a parametric technique, Monte Carlo simulation, or something else?  I was over at the Implementing Scrum website and found an awesome post, asking this same question.  If you think people get crazy whether or not you should utilize an Agile approach or a traditional project management approach on a project, wait until you talk about how to estimate work.  In the traditional project management world, I've seen people use SLOC and PERT to arrive at an estimate.  In the Agile world, I've used story points and have seen others use gummy bears and t-shirt sizes. In the end, I really don't care what estimation technique is used and I'm pretty sure the customer won't either.  All anyone should be worried about is if the estimates are accurate and if you get the work done.  Am I right or am I wrong?  I would love to read your input.

Estimating by Gummy Bears

Thank you to Mike Vizdos for letting me use his cartoon and for the inspiration for this post.