All About Agile | Agile Development Made Easy

Team Commitment

This post is from George Dinwiddie's blog by George Dinwiddie. Click here to see the original post in full.

Most Scrum teams estimate their top priority stories, select those stories that add up to their historical velocity for their sprint backlog. Some teams simplify this by merely counting the stories, or using the mathematical reciprocal, cycle time. Others make it more complicated, calculating the effect of days off and other known distractions from the work.

However they calculate it, some people put a lot of faith in the historical data to guide the future. “It’s data,” they say, “it’s better than guesses and not subject to cognitive bias.” Not all data is easily measured and converted to numbers, though. Limiting yourself to this initial calculation is, itself, an example of anchoring bias.

After planning the work for the next short interval of time, it’s helpful if a team looks each other in the eyes and asks themselves, “Can we do this much; could we do more?” If a group can’t do this and give itself an honest answer, it’s probably not yet a true team. A true team will be able to make a gut judgement of what the team as a whole can or cannot do. This judgement will take into account data that may not yet be identified and articulated, much less converted to numbers.

I’ve observed teams ask themselves this question and then get really quiet. No, they don’t feel they can do this work. Eventually someone speaks their...

read more


Leave a Reply

What is 4 + 3 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)