The Lego Game Sprint 2

Product Owners should hand out the stories for the second sprint. Explain that

they are in addition to the existing stories from the first sprint . Add stories not

completed in sprint 1. Add Bugs as stories.

Estimation

05

Ask teams to estimate the new stories, based on estimates for the first sprint.

Half completed stories, if any, need to be re-estimated.

Emphasize that the estimation should be consistent, not exact.

Sign-up

05

The same as before, but this time they should use velocity as a guide.

Ask each team how much they can do in the next sprint now that they know

their velocity. Tell them to only sign up for stories equivalent to their velocity. As

before customer decides what's important.

If a team has half-completed stories from the previous sprint, they should re

estimate the story in this sprint.

Development

15

QA / Showcase

05

Retrospective

15

Potential talking points this time around:

1.        How did estimation change between the two sprints? Do you feel

better about your estimates? Why?

2.        How did bugs (especially regression bugs) affect your velocity?

3.        Did the way in which work was divided change between these two

sprints? What drove this change?

4.        Compare the teams achievements at this point in terms of story points

and business value - show that story points != business value, and that

different teams will probably have different solutions for the same

problem. Also point out that velocity comparisons across teams are

meaningless.