ScrumMaster instructions for ScrumsSruction

This is the first time most of the participants have seen Scrum so try to keep them agile

The job of the scrum master in general is to be responsible for process and to get obstacles out of the way. 

So...

Encourage the team not to take too many stories into a sprint backlog. It is easier to add work than to drop it and we value ONLY completed stories in a sprint. 

Keep the time for the team and make sure they know the time to the end of the sprint (10 minute sprints). 

Help the team to get more work if they finish the sprint backlog before time runs out.

Help the team decide (with the product owner) which stories to drop if it becomes necessary and it looks like there won't be time to complete everything in the sprint. 

Encourage the customer to be creative in writing additional stories to make this as fun as possible. The given stories (product backlog) isn't fixed here. The customer can change anything, but changes only at the beginning of a sprint. 

At the 5 minute mark, have a 1 minute Scrum- Everyone says what they have been doing, What they intend to do, what obstacles they find in their way and whether they think they can complete everything. 

If supplies become a bottleneck, help them by retrieving things from the common area. 

----------
At the beginning. Each team will need a product owner who will order the stories quickly - roughly. The developers can be thinking about the "metaphor" for the project while this goes on and looking over the materials.Materials will likely be a bottleneck (especially scissors). The teams will need to be flexible about materials.