Agile through the lens of modern board games: a game worth playing

As a Scrum Master working in Agile software development projects, I've always been fascinated by the way modern board games can teach us valuable lessons about teamwork, effective communication, and problem-solving. It's no surprise that many of these same principles are also at the core of agile methodologies for software development.

This article will explore the connection between the Agile mindset and modern boardgames and how they can be used together to learn more about agility and empower our teams to transform their way of thinking.

Chapter 1: "From Luck to Strategy"

I don’t remember exactly when I started playing board games. Perhaps “Monopoly” was the first one or maybe “T.E.G” (an Argentinian version of the world famous “Risk”) but what I can tell you is that I am still enjoying the journey and things have changed a lot since then.

This article is not about board games, but “modern” board games. The evolution of board games has seen a shift from games that rely heavily on luck to ones that require strategy and planning, sometimes even focus on waste reduction through resource optimization (Ahem…, Lean). Classic games such as “Clue” and “Monopoly” were primarily based on chance and relied on players rolling dice or drawing cards to determine their next move. After the dice rolling it was common to have just one or two options to complete the turn. However, modern board games have moved towards a greater emphasis on strategy, where players are required to make decisions and plan out their moves in order to succeed. Planning ahead is key and sometimes you need to decide between gaining some nice resources now or sacrifice that instant of glory to take revenge in round four.

This shift has led to a growing industry of board games, with a wide range of options available to players. The variety of modern board games has also increased dramatically compared to the classic games of the past, with games available for all ages and interests, from complex strategy games to simple party games. Themes that can vary from “Exploding Kittens” to spending some relaxing time in “Santorini”.

Chapter 2: “Cooperate or compete?…Why not both?”

One day I was having an Analysis Paralysis (*) moment when I needed to decide between the thirty five options I had available in the board to place my farmer meeple in “Agricola”, when I realized the incredible amount of touch points between some of my day-to-day work decisions and the ones I need to take when playing board games.

In some modern board games players must collaborate and make strategic decisions to achieve a common goal. This is not dissimilar to the way that agile development teams work together to deliver software. In both cases, success is dependent on clear communication, adaptability, and the ability to work together as a cohesive unit.

Cooperative modern board games, such as “Pandemic” and “Dead of Winter”, can help grow the agile mindset by encouraging players to communicate and share information effectively. In these games, players must work together to achieve a common objective, such as saving the world from a deadly disease (maybe not the most appetizing theme right now) or surviving a harsh winter reinforcing the agile principle of collaboration which is essential for success in agile software development.

On the other hand, competitive modern board games such as the previously mentioned “Agricola”, “Wingspan”, or “Viticulture”, promote strategic thinking and adaptability. These games require players to make strategic decisions and adapt to changing circumstances in order to outcompete their opponents. Being adaptive and responsive to change is other of the key principles of Agile.

Competitive games also encourage players to think creatively and come up with new solutions to problems. These games often require players to balance short-term and long-term goals and make trade-offs between different resources and actions. That sounds a lot like the balance that is pursued between a Sprint Goal and the Product Goal, right?

Both cooperative and competitive modern board games can help grow the agile mindset. The difference is that cooperative games generally focus on promoting teamwork and collaboration, while competitive games focus on promoting adaptability and strategic thinking.

Chapter 3: “Terraforming a planet, transforming a Team”

Now let's take a look at some examples of modern board games and how they can be used as a tool for learning and practicing Agile principles.

“Terraforming Mars” is a board game that simulates the process of terraforming a planet - you may be guessing which one - , in which the players take on the role of different corporations working and competing to transform the planet by adding water, creating a habitable atmosphere, and building infrastructure.

This is a competitive game but we are all placing infrastructure on the same planet so every player action affects each other in different ways.

In Agile software development, teams work in regular periods of time - sprints - to deliver usable software to the customer, similarly in “Terraforming Mars” players work in rounds to improve the planet's habitability. Each piece of infrastructure constructs on the previous one to terraform the planet just like each increment of usable software is built upon the previous increment. Also, Agile methodologies emphasize on flexibility and adaptability, allowing teams to respond quickly to changes, and the same applies in this game as players must adapt to the changing conditions on Mars provoked by the actions of other players. Additionally, both Agile software development and “Terraforming Mars” require players/teams to prioritize, plan and balance the resources to achieve their goals.

By the way, if you haven’t played terraforming Mars, I really recommend you to do so.?

Now let’s take a look at one game that is actually based on the principles of Lean manufacturing.

“Kanban: EV” is a board game designed by Vital Lacerda that simulates an electric automotive production facility that takes advantage of the?Kanban method to manage and improve workflows to guarantee a just-in-time production.

By simulating an automotive production facility, the game provides a challenging and interactive way to learn about managing workflows, balancing inventory, limiting work in progress and continuously improve. I challenge you to think of anything more Lean (*) than that.

Be aware that “Kanban: Automotive Revolution” is a challenging game that I can personally recommend to some more experienced players. Vital Lacerda is well known for his beautiful, elegant and complex games.

To evidence that I am not talking about anything too novel, I would like to present to you an exemplary intersection of these two worlds : “Planning Poker” (*). Often referred to as “Scrum Poker”, it is a gamification technique used to estimate the relative size of development tasks. It is commonly used in agile software development, and it helps teams to quickly estimate the size of tasks and backlog items.?

“Playing” this “board game” is an interactive way to reinforce agile principles and practices. It helps teams to understand the importance of relative estimation and to practice techniques for achieving consensus. By providing a safe and controlled environment to experiment and learn, “Planning Poker” allows teams to practice and improve their estimation skills and to better understand the process of estimation and the role it plays in agile software development.

I have personally concluded from my Scrum Master experience that “Planning Poker” is an excellent way to keep the Agile teams engaged during estimations while reinforcing the idea of uncertainty and forecasts in detriment of accuracy and roadmaps.

Chapter 4: "Software development is some sort of a game"

I personally enjoy developing code in my free time. Some python small projects here and there…and guess what? I have also observed some improvements in my coding skills that I can relate with playing board games.

Software developers must analyze the requirements, design a solution, and write code to implement it. The strategies you develop through game play have a lot in common with software development. Both require a high level of problem-solving skills, as players or developers must navigate complex systems and make some hard decisions in order to succeed. In board games, players must analyze the current game state, predict the future state, anticipate their opponents' moves, and come up with a plan to achieve their objectives.?

Playing modern board games can help software developers to improve their problem-solving skills. “Ark Nova” for example, requires players to think strategically and plan ahead to get the best out of their Eco park . As players make decisions to balance earnings and conservation projects, they encounter new environment challenges and must adapt their strategies accordingly. This can help software developers to train their adaptation skills to be prepared for the changing requirements and unexpected issues that naturally arise during the development process.

Chapter 5: “Let’s play more”

In today's world, we are constantly surrounded by screens, whether it's our phones, laptops, or televisions. Board games provide a welcome break from screens, allowing us to engage with others in a fun and interactive way. It allows us to focus on the present moment and the tactile nature of the game's components can provide a sense of satisfaction and accomplishment that is hard to find with digital interactions.

Sitting at the table for a game round is also helpful to exercise different types of thinking, for example, memory, spatial, and critical thinking. These exercises can help to improve cognitive function and provide a mental break from the constant stimulation of the digital world.

So next time you and your team are looking for a fun and engaging way to improve your agile skills, why don’t try a modern board game?. Whether you choose a cooperative game like “Pandemic” or a competitive game like “Terraforming Mars”, you're sure to find valuable lessons that can be applied to your agile software development projects.

_

Thanks for reading!

Annexes:

(*) Analysis Paralysis: In the context of board games, analysis paralysis (also known as “AP”) refers to the phenomenon where a player becomes overwhelmed by the big number of options available to them and is unable to make a decision in a timely manner, thereby slowing down the game for the other players.?

(*) Lean: Learn Lean from its source: https://www.lean.org/explore-lean/what-is-lean/

(*) Planning Poker: The process involves each team member independently selecting a card with a numerical value (generally a modified version of the fibonacci series) that represents their estimate for a particular development task, and then revealing their cards simultaneously. The team then discusses any discrepancies and reaches a consensus on the final estimation. Planning Poker can help to reduce bias while promoting transparent collaboration and communication among team members ultimately building trust.

The games in the article:

- Monopoly (Charles Darrow, 1935)

- T.E.G (Argentinian version of Risk, David Jiterman, 1978)

- Exploding Kittens (Elan Lee, Matthew Inman, Shane Small, 2015)

- Santorini (Gordon Hamilton, 2016)

- Agricola (Uwe Rosenberg, 2007)

- Pandemic (Matt Leacock, 2008)

- Dead of Winter (Jonathan Gilmour and Isaac Vega, 2014)

- Wingspan (Elizabeth Hargrave, 2019)

- Viticulture (Jamey Stegmaier and Alan Stone, 2013)

- Terraforming Mars (Jacob Fryxelius, 2016)

- Kanban: EV (Vital Lacerda, 2020)

- Ark Nova (Mathias Wigge, 2021)

Hello there! If you want to know more about me visit me in: