Skip to main content

Timeline for Story Points flaw?

Current License: CC BY-SA 4.0

9 events
when toggle format what by license comment
Feb 14, 2019 at 22:39 comment added Venture2099 This is nonsense and your account must be a parody with that name.
Feb 14, 2019 at 19:24 comment added Daniel If they are able to make precise estimates with this sizing chart, why not just use hours? I won't argue that all work needs relative estimation - it doesn't. Some work is known and can be estimated in actual time in which cases it is far simpler to just estimate with real-time units. Story points are used in relative estimation which provides value in complex and unfamiliar work where precise time estimates aren't possible.
Feb 14, 2019 at 17:20 comment added Cort Ammon So you have roughly tied story to hours with a conversion factor of 10 story points = 1 hour (give or take). I feel this answer needs a disclaimer of sorts. The general use of story points is not tied directly to time. That's what velocity estimation is for. I wish your answer pointed out that your approach is a special case: the degenerate case where story points and hours are the same.
Feb 14, 2019 at 15:26 comment added MrScrumMaster It is in the perfect world true. Dear Daniel, have you ever estimate the price for your customer? This is a framework and you can make some changes for your team, My Dev team always make a great and precise estimate with this sizing chart.
Feb 14, 2019 at 14:36 comment added Daniel A fundamental principle of relative estimation is that it is not tied to time. Any relationship to time is a correlation for that particular team and circumstance.
S Feb 14, 2019 at 13:18 history suggested Bart van Ingen Schenau CC BY-SA 4.0
Improve formatting
Feb 14, 2019 at 12:56 review Suggested edits
S Feb 14, 2019 at 13:18
Feb 14, 2019 at 11:22 history edited MrScrumMaster CC BY-SA 4.0
added 60 characters in body
Feb 14, 2019 at 11:12 history answered MrScrumMaster CC BY-SA 4.0