Skip to main content
13 events
when toggle format what by license comment
Mar 27, 2018 at 2:20 comment added Todd A. Jacobs The problem is that you're estimating in man-hours instead of story points. This is generally considered an agile anti-pattern, but some frameworks like SAFe encourage it. The bigger problem is that you can't directly equate aggregate availability with level-of-effort, especially across individuals with differing skill sets and abilities.
Mar 26, 2018 at 20:52 history edited Tiago Cardoso CC BY-SA 3.0
Rephrase the title
Nov 7, 2017 at 12:43 review Close votes
Nov 9, 2017 at 7:42
Oct 30, 2017 at 10:15 answer added Alper timeline score: -1
Oct 28, 2017 at 19:27 comment added Bart van Ingen Schenau To break this habit, could you turn your task/story estimates into ranges? Like, story A is estimated to take between 6 and 10 hours of work, rather than 7.5 hours. Then you can't just add stories to a sprint till you get 100% resource utilization.
Oct 23, 2017 at 19:47 answer added Baracus timeline score: -1
Oct 23, 2017 at 19:41 comment added Baracus So the problem here is estimation. Get better at estimation and the work will fit (or rather, the work will fit as often as it doesn't fit). Hours vs Story Points vs some other measure of "size" doesn't matter if you can't estimate well.
Oct 23, 2017 at 19:21 comment added bobo2000 From people not estimating 37 hours worth of work in 37 hours accurately. It's the same reason why you will never get exactly 40 hours worth of work in a 40 hour week.
Oct 23, 2017 at 19:18 comment added Baracus I'm curious to know why you think you can't get 37 hours worth of work done in 37 hours?
Oct 23, 2017 at 17:28 answer added Daniel timeline score: 2
Oct 23, 2017 at 16:33 answer added Tob timeline score: -1
Oct 23, 2017 at 16:26 comment added Alan Larimer What does The Scrum Guide say? What does the Manifesto for Agile Software Development say?
Oct 23, 2017 at 16:15 history asked bobo2000 CC BY-SA 3.0