DevOps Game Paper Tower Challenge


In this simulation, we will apply DevOps Values and Culture in building the tallest Paper Tower.

DevOps is not a goal, but a never-ending process of Continual Improvement – Gene Kim

DevOps Values


DevOps 3 ways


DevOps enables to

  • Accelerate the flow of work – faster delivery
  • Amplify feedback – fast feedback and feed forward
  • Continuous Improvement

DevOps game – Paper Tower Challenge

Build the tallest freestanding tower with Paper that will support the balloon.

Supplies for each team

  • 5 sheets of newspaper
  • one yard of tape
  • one balloon
  • One yard of threadScreenshot_2.png


Game Rules

  • Build tallest freestanding tower with just 5 newspapers
  • The balloon should be tied at the top of the Tower.
  • 18 min to build a tower.
  • Each team should have a role of Development, Database, QA, and Operations.
  • DevOps principles & practices have to be applied while building.
  • At the end, one representative from each team should talk about the Principles and Value of DevOps they have applied while building.
  • Evaluation is based on the DevOps Principles applied and Product delivery.

I have conducted this session @ Relevance Lab Bangalore hosted by CodeOps Technologies, around 40 team members participated and we had 5 teams.

We had 5 teams started to build the tallest tower.



By 18 minutes teams have done with their product and getting ready for Retro.


A representative from each team Demoed quality product and shared the DevOps principles & practices they have applied while building.

The team who has applied most of the DevOps principles & practices and delivered a quality product, they were the winners!

Learnings from game

  • We need to be Agile.
  • Marshmallow is the “Assumptions” of a project. Assumptions play an important role in development, assumptions have to be identified and analyzed in the early stage of a project.
  • Everyone follows the same Culture.
  • Each team has members of Development, Database, QA, and Operations by this we eliminating Silo teams.
  • Knowledge sharing happens among team members, this will enable Generalized than Specialized team members.
  • Team members from DEV, Database, QA, Operations are involved from the start of Project.
  • Everyone is responsible for delivering.
  • The team built trust with each other.
  • The team is communicating and collaborating at every point of a time.
  • Work is visible to everyone, the team has up-to-date information on the status of the work so that if any WAIT is happening that can be addressed immediately and enable a fast flow of work from left to right i.e. Business to Customer.
  • Valuing feedback as all the different department team members are in one team here, feedback from QA is being immediately incorporated.
  • Reduced Batch size so that small work can be deployed quickly and frequently in order to decrease the overhead of QA testing at the end, Integration happens at the end and so on.
  • The team is empowered to fail fast and continually learn from success and failure.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Create a website or blog at

Up ↑

%d bloggers like this: