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
  • You could use the total of estimated hours as a check to see if there's time enough in the sprint to perform them. Commented Aug 28, 2011 at 20:46
  • @Kwebble: And what would you get from it? It doesn't matter once you did commitment. You will see that at the end of the sprint anyway. Commented Aug 28, 2011 at 20:50
  • The tasks are created during sprint planning. If you know at that point not all user stories can be delivered the expectation of the PO can be adjusted at the start. It's probably more useful for teams that are still learning to estimate their velocity. Commented Aug 28, 2011 at 21:15
  • @Kwebble: I don't think that expectation should be adjusted. That is the point of the commitment - the responsibility. Especially for new teams it is important to learn that commitment doesn't change. Btw. their estimation can be wrong and they can still fulfill the commitment but they will know it only by their progress later in the sprint not by their "estimates" = guessing. Velocity is not estimated, velocity is measured and computed from passed sprints. But you are right that new team should try Scrum as is with estimation and improve it later after they are more familiar with the process. Commented Aug 29, 2011 at 6:27
  • Good insight, guys! This is still giving me some trouble, could you please take a look at the comment I just added to the thread spawn from the original question. Comments much appreciated!!! Commented Aug 30, 2011 at 17:24