Comments on: Hours of remaining effort http://marcin.floryan.pl/blog/2010/07/hours-of-remaining-effort working with people, working with code Wed, 01 Feb 2012 22:34:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Nader Talai http://marcin.floryan.pl/blog/2010/07/hours-of-remaining-effort/comment-page-1#comment-155 Nader Talai Tue, 20 Jul 2010 08:58:00 +0000 http://marcin.floryan.pl/?p=198#comment-155 Agree with story points being better for the Y-axis. If you break down your stories and say every stories is less than two days you can even have story count on the Y-axis. Which works and also forces you to break down the stories so you can see how you are progressing towards your sprint goal. Agree with story points being better for the Y-axis.

If you break down your stories and say every stories is less than two days you can even have story count on the Y-axis. Which works and also forces you to break down the stories so you can see how you are progressing towards your sprint goal.

]]> By: Ben Mathews http://marcin.floryan.pl/blog/2010/07/hours-of-remaining-effort/comment-page-1#comment-153 Ben Mathews Mon, 19 Jul 2010 23:34:11 +0000 http://marcin.floryan.pl/?p=198#comment-153 Funnily enough, one of my teams is moving to only reporting points burndown. Our motivation comes from a desire to do task creation when we're ready to start the story rather than upfront in a planning session, meaning ideal hours isn't even known at the start of the sprint. Funnily enough, one of my teams is moving to only reporting points burndown. Our motivation comes from a desire to do task creation when we’re ready to start the story rather than upfront in a planning session, meaning ideal hours isn’t even known at the start of the sprint.

]]>