logo
  • Home
  • Events
    • Events
    • Calendar
    • Map
    • Hosting an event
  • Community
    • Players
    • Games
    • Articles
    • Testimonials
  • About
    • Our story
    • Our values
    • Our format
  • Contact
logo

play is the way

Explore

  • Home
  • About
  • Contact

Resources

  • Our events
  • Our players
  • Our games
  • Our articles

Address

  • #play14 a.s.b.l.
    46 boulevard Jules Salentiny
    L-2511 Luxembourg
    LUXEMBOUG
  • [email protected]

© 2014 - 2025 #play14 developed by Cédric Pontet

  • Privacy Policy
  • Terms of Service
footer-logo

Yata - A DevOps game

x-y-game_01.png
Prev
X + Y game
yata-a-devops-game_00.jpg
  • CategoryGame
  • PublishedJul 1st, 2017
devOps
collaboration

Summary

This game will demonstrate some of the most important principles behind DevOps.

Materials

  • 1 set of 150-200 bricks/caplas
  • 2 pens
  • The printed rules
  • Whiteboard
  • Space

How to play

Download the rules in the resources section on the right sidebar

Setup

Space: You will need a large space with 2 tables to play.

As a facilitator explains the game from the rules, then:

  • Separate physically the Dev and Ops teams
  • Put the “Dev” environment on the dev table
  • Put the “Pre-production” and “Production” environments on the ops table
  • Add the base structure for tower bases on each environment. The base must be as in the image below : (base structure represents the environments (DB, Frameworks, Languages, …)) 

base.png

Rules

Sprints: There will be 4 sprints during this game. Each sprint will be organized as described in the sprint image. For each sprint, the facilitator must distribute the corresponding cards (# sprint number).

Goal

The goal is to aim for maximum points by delivering features to production (deployment). We will use wooden bricks to do so.

Roles

roles.png

Sprints

sprint.png

Sprint 1: Documentation approach vs collaboration

  • DEV: 3 minutes to build and deliver to pre-prod
  • OPS: Refuse any non-documented tower

 

RETROSPECTIVE

  • Stop starting, start finishing / Work In Progress (W.I.P) limits
  • Keep It Simple & Stupid (K.I.S.S)
  • Production deployment requires collaboration and reveals problems.
  • Silo breaks the collaboration

Sprint 2: Silo again

No collaboration: it is forbidden to communicate with Ops (by the top management)

  • DEV: Document the delivery + no cards for them
  • OPS: T shape base in pre-prod + prod

 

RETROSPECTIVE

  • Opposite objectives between Dev & Ops (accounting, different priorities/projects/visions)
  • Definition of done
  • Always think about the targeted environment

 

ACTION

Delivery and deployment in the presence of both teams.

Sprint 3: Culture of collaboration

Move from siloed delivery to collaboration: everyone in one room.

  • DEV: construct, starting by taking back the previous tower + cards for Sprint 3
  • OPS: facilitates the deployment in pre-prod + prod

 

RETROSPECTIVE

  • Collaboration makes it possible to deliver
  • Focus on culture/collaboration
  • Collaboration saves time

Sprint 4: Automation

  • DEV: construct, starting by taking back the previous tower + cards for Sprint 4
  • OPS: automate the deployment between pre-prod and prod

 

RETROSPECTIVE

  • Clone of production (blue/green deployment), could be simulated by swapping two pre-production and production post-its
  • Automate deployment and acceptance testing, instead of manually doing it
  • Pre-production environment for practicing before production
  • Continuous deployment card by card, the ops manager sums the deployment times
  • Automation saves time

Conclusion

  • Evolution of the metrics used on the boards, and aggregation into one shared board (performance, process, people, KPI linked to events)
  • Collaboration is a skill that can be learned
  • Explain the basic principles of DevOps (Be C.A.L.M.S)

devops.png

Images

  • Timebox45-60 mins
  • ScaleMin 6, Max 10, can be played in multiple parallel groups
  • Ratings
    Energy
    Connection
    Silliness
  • First playedLuxembourg 2017
  • Proposed byadrien-muller.jpg
    Adrien Muller
    yoan-thirion.jpg
    Yoan Thirion
  • Documented byadrien-muller.jpg
    Adrien Muller
    yoan-thirion.jpg
    Yoan Thirion

Resources

  • Yata.pdf