An agile simulation teaches agile concepts by letting people experience them with their hands instead of explaining them on slides. In the Okaloa Flow Lab, teams move cards across a board game, track metrics and deliberately change parameters such as work-in-progress limits. What stays abstract on a slide turns into intuition, especially for managers who have little insight into how agile teams work.
Key Takeaways
- Learning through simulation sticks much better than a slide presentation, because it speaks to intuition rather than only to the rational mind.
- Managers only really understand agile mechanisms such as the pull principle once they have seen the effect for themselves in a safe simulation, without putting a real project at risk.
- The traditional project round is designed to end in frustration: a board full of half-finished and blocked work that makes the extreme of classic project management visible.
- Teams that set a work-in-progress limit in the second round finish about 50 percent faster, although blockers are just as likely and the same events come in.
- The retrospective after the first round almost always turns into a blame game: teams look for causes outside themselves instead of seeing their own way of working as the lever.
Why an Agile Simulation Beats a Lecture
Teams understand agile principles better when they live through them in a simulation than when they read about them on a slide. That is the idea behind an agile simulation such as the Okaloa Flow Lab, a board game developed by a team in Belgium. It lets players work through flow, quality and agile mechanics directly on the table.
Andreas Wübbeke uses this approach both at university and with companies. The contrast with conventional teaching is easy to see. Instead of explaining why a work-in-progress limit makes sense or why T-shaped profiles help a team, the simulation shows these effects as they happen.
The idea comes from sports coaching. In soccer, a constraint such as one-touch play trains players to pass faster in tight spaces, and they carry that skill into the match. The simulation works the same way: it sets boundaries, and within them the participants are free to move and experiment.
“It works so much better because it doesn’t speak to the rational part of your mind. It speaks to your intuition. You can try it out with your own hands.”
(Andreas Wübbeke)
How a Flow Simulation Like the Okaloa Flow Lab Works
Each simulation board has five players: four work as the team, one starts out as the project manager. The players move work items, which are cards, across the board and record numbers and statistics in every round.
Johanna Maduch describes the start as deliberately old-school. You begin with a round of traditional project management and only then move on to the agile version. At the end, the metrics from both rounds can be compared, and that comparison settles discussions that would otherwise go around in circles.
Andreas has flipped the usual order of learning. The hands-on simulation comes first, then a retrospective on what happened and what the statistics show, and only then the theory behind it. The guiding question is always the same: What just happened here, and why?
Next, the team changes one parameter it controls, such as a work-in-progress limit. The events in the game and the dice stay the same. That way you can see whether the result gets better or worse without mixing up cause and effect.
A traditional round and an agile round, including the time to work out the mechanisms in between, take about half a day in total.
Leaving Things Out on Purpose
A simulation deliberately leaves things out. That is its purpose, not a flaw. Some effects are buried under other factors in real project work and only become visible once reality has been stripped down.
A typical opening is the traditional project management round, which is built to end in frustration. The board is full, everything is half done, and a lot of work is blocked. The first retrospective almost always turns into a blame game. Too much work is coming in, the players say, blockers show up too often, the odds are too high.
That is exactly where the learning happens. At first, the players don’t notice that they could change how they work and raise the team’s output considerably. In the second round they finish about 50 percent faster, even though blockers are just as likely and the same number of events come in. More gets done, the board is emptier, and the team feels better.
Testers and seasoned practitioners like to pick apart every rule and every card when they sit down at the board. That calls for an experienced facilitator with enough seniority to keep the session on track. A good answer to their objections is the transfer question: How could the effect you just saw carry over into your own work?
Versions That Grow with the Team’s Knowledge
The simulation comes in several versions that build on one another as the players learn. You start with a traditional setup, then play in a more agile way, and some changes stay in place for good. The project manager is part of the game at the beginning and is later replaced by other roles or drops out almost entirely.
Two new modules have come out of this toolkit, each with a different focus:
| Variant | Mechanics | Learning Focus |
|---|---|---|
| Timeboxing | Time as the constraint: five minutes instead of a fixed number of iterations, core process partly reduced | Team development, faster action, estimation |
| Continuous Improvement | Defects are added to work items statistically, on top of blockers | When to test and how much |
In the Continuous Improvement variant, the defects aren’t real bugs that someone has to find. They are added statistically. The players have to weigh their options: When do I test? How much do I test? Is it worth skipping tests to get more finished by the end?
The variants can be combined. You can see what happens when a team tests heavily early on, or drop testing from the game entirely and look at the result. A skills simulation sets two extremes side by side: as much learning within the team as possible on one side, as much specialist expertise as possible on the other.
How a Simulation Shows the Effect of WIP Limits
Nobody understands agile values such as T-shaped profiles or WIP limits just because they are on a slide. People often carry them around as untested beliefs: I want a WIP limit, I want T-shaped people, because that is what agile means.
The simulation turns that belief into experience. You can go from one extreme to the other and find out what a decision actually does. Instead of arguing ten times about the right limit, one team plays above it, one below it, one without any limit, and everyone compares the numbers.
This way of working lets people make mistakes without any risk. The setting is safe, and no real project is at stake. Even people who hold on to fixed ideas in their daily work are willing to try something new here.
Why Simulations Work So Well for Managers
Simulations work especially well with managers and senior executives, because there is often a disconnect between them and the agile teams. Managers drop in for the review, look at something and leave again. They are not part of the cycle: no planning, no retrospective, none of the practices that hold agile work together.
That gap breeds misunderstandings. The pull principle, where teams pull their own work, is a classic. From a traditional management perspective it sounds like losing control: if the teams pull their own work, where does that leave me and my push? Once managers play through how much pulling improves the flow of work, they start to understand the mechanism.
Managers need more support for this step than a room full of students. Experienced managers bring a lot of practical knowledge and ask very fundamental questions. A trainer needs equally fundamental, clear answers ready.
Learning with Your Hands Goes Deeper
Material sticks better when people experience it. At university, this shows up in the grades: students remember the mechanisms much better after a simulation than after studying a slide deck.
The principle behind this is constraint-led learning, whose positive effect has also been described in research. The sports training methods mentioned above come from the same approach: the training environment is designed so that certain automatic responses develop over time.
A lecture reaches only the conscious, cognitive mind at first. Yet people spend much of the day on autopilot, because the brain is expensive to run and prefers routines. Touch and hands-on work speak to intuition directly, and cognition follows intuition. That creates a shortcut to learning that no lecture can offer.
Why an Agile Simulation Belongs in the Room, Not Online
Team dynamics are the reason to play the simulation in person. Sitting together around the board does something to people, and teams play with very different levels of ambition. It is much harder to read how a team is feeling online than at a shared table.
Frequently Asked Questions
How much time should you set aside for a flow simulation?
For a classic and an agile simulation, including the analysis of the mechanisms at play between them, about half a day is sufficient in total. The simulation is played with five people per simulation board: four work as a team, and one takes on the role of project manager at the start. In each round, the participants record numbers and statistics that can be compared at the end.
Why does such a simulation start with traditional project management instead of going straight to agile?
The traditional round intentionally ends in a frustrating situation: the board is full, everything is half-finished, and a lot of work is blocked. This extreme scenario provides the benchmark for the agile round. Since the same metrics are tracked in both rounds, it eliminates discussions that would otherwise go around in circles.
How much does a work-in-progress (WIP) limit affect a team’s performance?
In the second round of the simulation, teams working with a set WIP limit complete tasks about 50 percent faster. The key is that the framework conditions do not change: neither the probability of blockers nor the number of incoming events decreases. The board becomes less crowded, more work gets done, and the team feels better.
Why do teams first look for the causes of poor results outside their own actions?
In the first retrospective, a blame game almost always ensues: too much work is coming in, blockers occur too often, and the probabilities are too high. That is precisely where the learning opportunity lies. At first, participants overlook the fact that they could change their own way of working to significantly improve performance.
Do simulations also work with managers and top executives?
Yes, that’s exactly where they’re most effective, because there’s often a disconnect between management and agile teams. Managers show up for the review and then leave again without being part of planning, retrospectives, or the other mechanisms. A classic example is the pull principle, which, from a traditional perspective, sounds like a loss of control until you run through its impact on workflow.
Can a board game simulation also be conducted online?
In-person sessions provide a better setting because team dynamics are part of the learning process. Sitting together at the board has a certain effect on people, and teams operate with very different levels of ambition. It’s much harder to gauge how a team is feeling online than it is when everyone is gathered around the same table.
Why does hands-on learning stick better than a lecture?
A lecture initially appeals only to the cognitive mind. However, people spend a large part of the day on autopilot because the brain is energy-intensive and prefers automatic processes. Hands-on experience directly engages intuition, with cognition following afterward. This is based on the principle of constraint-led learning, from which the corresponding sports methods also originate.
