Desciption

Overview

Scrum Video is an unique in its kind and extremely addictive simulation of Scrum. Teams during several Sprints create and show video films on free or given by the facilitator topics.

Is it cool?

We (coaches of Unusual Concepts company) played Video Scrum many times during last 2 years on our Certified Scrum Master (CSM) and Professional Scrum Master (PSM) (additional 3rd day) classes. We consider the game to be very effective in demonstrating and teaching main Scrum concepts. Besides, that’s a lot of fun and people really love Video Scrum.

Authorship

Original idea was created by Stacia Viscardi and then significantly updated and extended by us.

Why Video Scrum?

Indeed, there are number of Scrum simulations. First of all, comes to mind the popular Scrum Lego City simulation, created by Agile42. Despite this, we believe that Video Scrum Video has a number of advantages over other simulation:

• The team creates a real, not a "toy" product - video clip. We know that some people (this is not us :)) are skeptical about the simulation using Lego, considering it to be childish (we do not think so :)).
• Video Scrum is great for teaching professionals out of IT industry (marketing, sales etc.), for whom simulations that involve the creation of software products (eg, website) is not suitable.

• The complexity of the game is very close to the challenges that Scrum Team meet in their daily work. For example, lack of competences ("we do not know how to use this video program") and the need of developing them "on the fly", the inability to create the potentially releasable product increment ("we have filmed material but did not have time to mount a movie"), shared responsibility, teamwork ("what should I do, we have only one camera, I have nothing to do").
• The game very clearly demonstrates the philosophy of iterative-incremental development with a video clip as the ultimate product. It is not intuitive for teams that the output of each Sprint need to be the finished product. They often slide to waterfall thinking (scenario Sprint, filming Sprint, mounting Sprint).
• Video Scrum perfectly illustrates the importance and criticality of the feedback and presence of end-users during Sprint Review ("other teams are watching our movie and thus giving the feedback").
• Scrum video very clearly shows the importance of creating a "Done" product ("we forgot to check availability of codecs on the demo machine, and now we have nothing to show").

How much time does it take?

As a rule of thumb we consider 4 hours is enough time for playing full-blown Video Scrum. You can allocate less time for it but quality of the game will be compromised.

Number of players

We have noticed that the game with several teams - not less than two (2) but not more than four (4) 4-6 people in each is the most effective simulation because:

• Creates more fun.
• Results in more feedback during Sprint Reviews, when teams one after another demo their videos and give each other critical feedback.
• In the last Sprint it’s possible to present a task of integrating team’s increments..
• Creates a healthy competitive atmosphere.

Basic Game (facilitator instructions)

The participants should have a basic understanding of Scrum concepts (roles and responsibilities, events, artifacts). We use flip charts for teaching them. You’ll have to spend additional time for teaching Scrum if your audience is not well prepared.

Before Scrum.

1.1 Facilitator presents a legend for the teams ( 5 min):

«I’m the investor who is an avid fan of short movies and cartoons. I am willing to invest some money in making several movies for TV. You have to shoot your films using the Scrum. I will consult you on theoretical issues, and also help in facilitating a process of making films».

Sometimes we prefer to order "soap opera" for the teams which means that all films should be combined by some common storyline, for example, some characters and so on. We do this in case if we want to simulate the joint work of several teams on a single product.

The facilitator gives several restrictions from list below (you can take just a few or ALL of them):

1. Each team has 4 Sprints for shooting the film. Each Sprint a new version of the film should be demonstrated during the Sprint Review.
2. The film can be in any language - Russian, English, German, etc..
3. Films are demonstrated on the facilitator machine connected to the projector (it makes game more difficult) or the team working station.
4. The film should have some sound effects.
5. The film must have introduction, middle and conclusion parts.
6. The film should be not more than 2 minutes long.

1.2 Newly formed Scrum Team discuss possible topics for their films and select the Product Owner and the Scrum Master (5 minutes). The facilitator may play a role of the Scrum Master for one or several teams.

1.3 Scrum Teams formulate the Definition of Done (DoD) given the constraints posed by the facilitator of the game before (5 min).

1.4 Scrum Teams create initial Product Backlog (10 min) which is then used for the first Sprint Planning. Additionally teams may create release plan (10 min) and divide work across the Sprints. In this step you can identify the Waterfall teams that plan to make a film script for the first Sprint, start film shooting in the second Sprint etc.

Start Scrumming.

1.4 First Sprint:

• Sprint Planning (5 - 10 min).

• Sprint Execution, making films (20 - 30 min).

• Sprint Review (10 - 20 min) depending on the number of teams. The facilitator must ensure that all work on filming is stopped. Scrum Teams demonstrate their "Done" movies and after after that each team has 2 minutes for getting feedback from their peers, recording all the comments, advice and tips for improving their film.

• Sprint Retrospective (5 min).

• Joint Retrospective (5 - 20 minutes). Give your neutral observations and discuss what happened. Pay attention to the Waterfall team if there are any. Sometimes there’s a need to return back to the theory. This is the most important part of the game.

1.5 Sprints 2, 3, 4 follow.

And how to improve the simulation Video Scrum? Do you have any ideas that you are willing to share with us? We will be happy to receive your feedback.