Experience communication, collaboration, and leadership in a team by letting individuals collaboratively follow a circuit using a single pen by pulling strings.

Practice standup meetings with a dysfunctional one.

Learn about roles and responsibilities across team, Product Owner and Scrum Master.

Understand how the Product Owner’s ability to describe features leads to better results. Learn about different possible interpretations and good and bad styles of test.

Learn about acceptance criteria, their definition, and customer communication.

Understand the basic Scrum process. Why are iterations, planning, and Product Owner communication important?

Learn and conduct a risk assessment using Jenga blocks.

Learn basic agile practices including the planning process in iterative software development.

Experience and learn: (1) negotiate an iteration plan, (2) use velocity to measure and make a predictable schedule.

Understand high performing teams by focusing on people utilization (instead of completing projects early), continuous partial attention, effect of lack of face-to-face communication, limiting work-in-progress.

Learn about how iterations help to identify the assumptions in the project, its cost and duration and the real customer needs.

Understand the advantages of iterative planning vs. all-up-front planning.

Learn about Scrum and its basic meeting types: Backlog grooming, Sprint planning, Daily Scrum, Sprint review, Sprint retrospective.

Learn about communication, lack of negotiation and requirements clarity using the game of Chinese Whispers.

Learn about Tayloristic vs. Agile knowledge sharing.

Understand the reasons behind agile, and the principles that the methodology is built on. Specifically targeted at designers and aims to highlight the benefits of agile, and illustrate how design activities can occur in an agile environment. This game is designed for a large number of people 50-150.

Learn about the importance of continuous flow.

Learn about how the basic practices such as iteration planning, iteration review, and retrospective can help teams to self-organize.