Stay Updated: Posts | Comments   Follow us on Twitter

Name: Sreejith

Web Site: http://agilesuccessfactors.com

Posts by :

    A non IT Scrum simulation game – Learn scrum and self organizing through a game

    July 19th, 2018

    Author : Sreejith N .T.   ntsreejith@gmail.com

    SCOPE :  LEARN SCRUM AND SELF ORGANIZING THROUGH A GAME

    Contents

    • Objective: ……………………………………………………………………………………………………………………………………
    • Preparation …………………………………………………………………………………………………………………………………
    • Develop User Stories …………………………………………………………………………………………………………………….
    • Estimate User Stories ……………………………………………………………………………………………………………………
    • Order the Backlog ………………………………………………………………………………………………………………………..
    • Sprint Planning Meeting ……………………………………………………………………………………………………………….
    • Start Sprint ………………………………………………………………………………………………………………………………….
    • Day-1 ……………………………………………………………………………………………………………………………………………
    •           Daily Standup meeting …………………………………………………………………………………………………………..
    •           Work ……………………………………………………………………………………………………………………………………
    • Day-2 ………………………………………………………………………………………………………………………………………….
    •             Daily Standup meeting …………………………………………………………………………………………………………..
    •                Work …………………………………………………………………………………………………………………………………
    • Day-3
    •             Sprint review ………………………………………………………………………………………………………………………..
    •             Sprint Retrospective ………………………………………………………………………………………………………………..
    • Sample Product Backlog…………………………………………………………………………………………………………………….
    • Time Tracker……………………………………………………………………………………………………………………………………..

    Objective:

    Anything that is learned through game is well understood in terms of concepts and practices. As part of training and coaching IT teams on Scrum fundamentals, it will be useful to use games to have team understand the framework.

    This game is kept at high level so that creativity of coaches and teams can be leveraged to make it customized for your team and environment. This game can be done after all the Scrum roles, Artefacts and Scrum ceremonies are explained to the team.

    Activity-1

    Preparation

    • Color pen sets, four  A4 color papers, glue sticks, pencils and one A1 size white paper for each team.

    • One team can be of the size of 5 to 9 people.

    • Each team to identify a name for the team, identify a Product owner and a Scrum Master.

    • Scrum Master can use the Time tracker  to keep the time check.

    Activity-2

      Develop User Stories  :  30 minutes

      Please refer to Sample product backlog, identify User Roles and create User Stories as a team activity.

    Activity-3

      Estimate User Stories -  15 minutes

      Use relative sizing method (Small, Medium, Large, Extra Large) and relatively size the User Stories.

    Activity-4

       Order the Product Backlog as per priority (Product owner will lead this activity) - 30 minutes

        Product Owner to prioritize the Product Backlog which was created from the ‘Develop User Stories’ activity based on her preference.

    Activity-5 Sprint Planning Meeting - 20 minutes

          From the prioritised Product Backlog, the Development Team should select the items they think, can be achieved during a Sprint (Sprint duration is 30 minutes with 15 minutes for each Day-1 and Day-2) considering the order provided by the Product Owner. The whole team consults PO and writes a Sprint Goal together on a post-it card.

           The Development Team decides how the work will be delivered. They create a Sprint Backlog – a plan containing tasks that must be completed to achieve the agreed scope.

          Team to estimate the tasks to ensure that they are achievable within the total time available (i.e  30 minutes).

    Start Sprint Day-1

         Daily Standup meeting (5 minutes) :  Development Team get together; Each member summarizes the activity they are going to do as part of Day-1. What obstacles are in the way?

          Work (15 minutes)  : The Development Team works on the Sprint Backlog and adjusts where necessary. Stop working when the timebox of 15 minutes are over.  Scrum master to track the timebox.

    Sprint Day-2

          Development team continue the sprint

           Daily Standup meeting (5 minutes)  : Gather the Development Team together; each member answers the three questions to coordinate the work (What was accomplished on the first day? What will be done in the second day? What obstacles are in the way?). Adapt your plan for the second day of the Sprint to meet the Sprint Goal.

         Work (15 minutes) -  The Development Team works on the Sprint Backlog and adjusts where necessary. Stop working when the timebox of 15 minutes are over.

    Sprint Day-3

           Now is the time for Sprint review and Sprint retrospective.

          Sprint Review:

                Time Estimate -10 minutes per team

                Sprint Demo : Sprint is complete. Your Sprint is now over and it’s time to inspect the increment that you have

    delivered. Look at your initial Sprint Backlog, see what tasks have been completed and what, if anything,

    didn’t make it. The Development Team should then demonstrate to the Product Owner and  get feedback.

            Sprint Retrospective :  10 minutes

                        Now reflect on your Sprint, consider what worked well and what didn’t work. Talk about what you would have done differently if you were to do another Sprint.

    Sample Product Backlog

    Product Backlog for a Space and Moon Tour

    1. Create cover art, brand, and/or logo

    2. Define major sightseeing options for Moon tour

    3. Outline a “Wonders on Moon” expedition

    4. Set prices for the tours

    5. Outline warning messages (gravity, oxygen, fungi, etc.)

    6. Suggest clothing options

    7. Explain travel options to/from Earth

    8. Describe a “Human Sports” tour

    9. Outline refund policy

    10. Suggest related services

    Time Tracker

    Activity                                  Time Required

    Develop User Stories          15 minutes

    Estimate User Stories        15 minutes

    Order the backlog               15 minutes

    Sprint Planning Meeting    20 minutes

    Day-1

         Daily Stand up meeting          5 minutes

         Day-1 Work                              15 minutes

    Day-2

              Daily Stand up meeting         5 minutes

              Day-2 Work                              15 minutes

    Day-3

              Demo                                       10 minutes

              Retrospective                            10 minutes

    VN:F [1.9.16_1159]
    Rate This
    Rating: 2.3/5 (3 votes cast)

    No Comments "

Login

Discuss Comments
Agile Games Group