Comments on: Sprint Burndowns in Story Points or Time? http://www.njamin.org/blog/scrum/sprint-burndowns-in-story-points-or-time-163.php Sun, 07 Feb 2010 20:21:04 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Nathan http://www.njamin.org/blog/scrum/sprint-burndowns-in-story-points-or-time-163.php/comment-page-1#comment-1906 Nathan Sun, 26 Apr 2009 09:49:35 +0000 http://www.njamin.org/blog/?p=163#comment-1906 Hi Przemek! Thanks for your comment. I have to agree with you: Story points are not accurate enough to give any valuable information <strong>during</strong> a Sprint. We've done it that way until now but I think we will change things - despite Jeff Sutherland's experience ;-) Hi Przemek!

Thanks for your comment. I have to agree with you: Story points are not accurate enough to give any valuable information during a Sprint.

We’ve done it that way until now but I think we will change things – despite Jeff Sutherland’s experience ;-)

]]> By: Przemek http://www.njamin.org/blog/scrum/sprint-burndowns-in-story-points-or-time-163.php/comment-page-1#comment-1905 Przemek Fri, 24 Apr 2009 14:07:24 +0000 http://www.njamin.org/blog/?p=163#comment-1905 To me it makes more sense for a burn down to be based on time remaining and not story points. The reason is simple, the story points and time remaining are both estimates, however as the story points are a one-off estimation done before a user story is started it is generally a less accurate measure. The time remaining on the other hand is a daily updated estimate on what is remaining to do for a user story. So assuming the purpose of the burn down is to give an indication on how the team is proceeding with the sprint and whether expectations are being met, the time remaining burn down should be the more accurate one. I find it hard to believe that the overhead would be so great as to not be practical within most projects. If the task isn't started the the value doesn't change, if the story is being worked on then the estimate of a task should be simple. To me it makes more sense for a burn down to be based on time remaining and not story points. The reason is simple, the story points and time remaining are both estimates, however as the story points are a one-off estimation done before a user story is started it is generally a less accurate measure. The time remaining on the other hand is a daily updated estimate on what is remaining to do for a user story. So assuming the purpose of the burn down is to give an indication on how the team is proceeding with the sprint and whether expectations are being met, the time remaining burn down should be the more accurate one. I find it hard to believe that the overhead would be so great as to not be practical within most projects. If the task isn’t started the the value doesn’t change, if the story is being worked on then the estimate of a task should be simple.

]]>