Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • 31
    +1 for the focus on complexity, not time. Translating to raw hours will be easy once you have enough sprints under your belt. I found that the variability between stories gets washed out over time. Commented Jan 9, 2013 at 17:02
  • 17
    So really, complexity points might be a clearer term than story points, and any task with too many complexity points is too complex and probably involves too many risks and unknowns to deal with all in one go. Complexity has exponential cost, and the poor sod who gets stuck with that task is going dig a hole so deep he won't be seen again for weeks or months. Better make a simpler task of understanding the complex task first, and dividing it up into smaller tasks with less risky and better understood complexity. Commented Jan 10, 2013 at 10:06
  • 4
    Time and cost are effects, complexity is the cause, and you can't understand time without understanding complexity. Commented Jan 10, 2013 at 10:06
  • 9
    Story points = Complexity points - 2 syllables. :-D Commented Jan 10, 2013 at 13:45
  • 7
    Has anyone ever considered calling story points "casting cost?" => nerd Commented Jul 29, 2014 at 17:51