http://elegantcode.com/2007/09/14/the-backlog-estimation-snail-pace-anti-pattern/?utm_source=rss&utm_medium=rss&utm_campaign=the-backlog-estimation-snail-pace-anti-pattern Tue, 08 May 2012 09:13:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://elegantcode.com/2007/09/14/the-backlog-estimation-snail-pace-anti-pattern/comment-page-1/#comment-11739 Jon Arild Tørresdal Fri, 12 Oct 2007 22:21:52 +0000 http://elegantcode.com/?p=649#comment-11739 Couldn't agree more! We've been using planning poker and planningpoker.com for about a year now and it has worked out great for us. Not only for realizing that spending a lot of time doing estimates is a waste of time, but seeing that it actually works in practice! I think that combining planning poker with an iteration based development approach is the best. What we've found out is that as long as we keep doing the wrong estimates, everything works out! By that I mean that the velocity (how much work a team can do per iteration) the team is capable of committing to is regulated by the errors in the estimates. It will not work the first time you try it, probably not the second time either, but as the team starts to get into this kind of thinking you will see the results. Couldn’t agree more! We’ve been using planning poker and planningpoker.com for about a year now and it has worked out great for us. Not only for realizing that spending a lot of time doing estimates is a waste of time, but seeing that it actually works in practice! I think that combining planning poker with an iteration based development approach is the best. What we’ve found out is that as long as we keep doing the wrong estimates, everything works out! By that I mean that the velocity (how much work a team can do per iteration) the team is capable of committing to is regulated by the errors in the estimates. It will not work the first time you try it, probably not the second time either, but as the team starts to get into this kind of thinking you will see the results.

]]>