Thursday, January 22, 2009

Story points for Estimation

Mike Cohn, author of Agile Estimating and Planning wrote in his comments to his "To Re-estimate or not; that is the question" article ...

"... When I do iteration (sprint) planning I don’t even consider the story point estimates. We grab one item from the product backlog, break it into tasks and hours, discuss whether we can commit and then repeat until full. The story points–as I use them–are for long-term planning. When we plan an iteration and take a lot more time to do so we do it by discussing tasks, hours and commitment."

check out "Why I Don’t Use Story Points for Sprint Planning" for more of his thoughts on this.


Curious Attempt Bunny said...

I never got to be overly obsessed with estimation (above and beyond everyone being involved). What's interesting to me is that once you discard the notion of an iteration that estimation becomes a waste of time (I'm the only one on the team that think so, though).

Nigel said...

I think I follow you, but how do the gold-owners know roughly how much it's going to cost if you don't estimate anything?

GitHub Projects