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.

5
  • 1
    You are using only the single previous sprint velocity to decide the next sprint's capability? Commented Jun 11, 2015 at 18:38
  • No, we use the trailing 2 velocities, but the average still takes a hit which doesn't represent the actual work done due to this abnormality. Commented Jun 11, 2015 at 18:43
  • 1
    You say once in a blue moon... how often does this actually happen? Once a year? How far off is the initially estimated point capacity from what was accomplished / actual (how much does this whack the velocity off by)? Commented Jun 11, 2015 at 18:45
  • Why not simply attach a revised estimate to that story that you use when doing future velocity calculations? Commented Jun 11, 2015 at 18:48
  • @yellavon, Has anything mentioned here caused you to look at your method of calculating velocity? Commented Jul 13, 2015 at 23:07