DevOps with LEGO

LEGO is being the best game to simulate our work, let us learn DevOps through Lego.

I have conducted this session @ Microsoft Bangalore through Containers Developers Meetup and hosted by CodeOps Technologies

In this LEGO game, we had multiple teams participated, each team takes one business requirement to deliver. We have used LEGO Deep Sea Exploration Vessel – Lego, you can use any LEGO set.

Our mission was to recover sunken treasure with the Deep Sea Exploration Vessel! A shipwreck with a cargo of gold bars has been spotted at the bottom of the ocean. we need build high-tech diving equipment.

Our goal is we need to build high-tech diving equipment.

DevOps with Lego

Game Rules

  1. Minimum 4 team members to max 8
  2. Each team should have a role of Development, Database, QA, and Operations.
  3. 15 min to build LEGO
  4. DevOps principles have to be applied while building LEGO
  5. At the end, one representative from each team should talk about the Principles and Value of DevOps they have applied while building
  6. Evaluation is based on the DevOps Principles applied and Product delivery.

We had 5 teams was building scuba scooter, Lifeboat with 2 crew members, the submarine with domed cockpit, Remote submarine, and shark cage respectively.

Team building Lego and applying DevOps principles

By 15 minutes team has delivered Product and getting ready for presentation.

Legos are designed by Team through DevOps principles

A representative from each team presented their approach.


The team who has applied most of the DevOps Principles, they were the winners!

DevOps winners

Learnings from LEGO game

  • 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.
Containers Developer Meetup @ Microsoft, Bangalore

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: