Build - Run - Improve - Repeat
How do you explain to someone (your manager?) that you shouldn't think about delivering new software faster if you can't manage to deliver better quality? How do you tell them to forget about continuous delivery for a while and focus first on continuous integration first, especially if they have already set their mind on a certain toolsuite or a certain tool vendor?
What if you could make them experience the impact of their decisions? In a safe environment? That is exactly what this game aims to do:
You build, it you run it, means you focus on all activities, all stages of the DevOps cycle, starting with Plan:
You improve it, means you gradually improve your way of working, by investing in all the different activities all the stages of the DevOps cycle
It's all in the game...
This game is designed as a board game in which you need to deliver new features, by going through all the activities of the different stages of the DevOps cycle.
Delivering features means earning revenue you can invest in improvements. Initially this delivery of features will go slow, but with the right investments and improvements you will benefit gradually and steadily. You build up a foundation of good practices that pay back later. You do this by improving the maturity level of the different activities of the cycle. You start with zero maturity and can already invest in improving some activities.
The game lets you experience what happens of you invest in the wrong things, or in the wrong order... And believe me: lot's of things can go wrong! Mainly incidents, and not always your own fault.
What can possibly go wrong?
A new vulnerability can be reported. You need to fix that as quickly as possible.
A bug was found in your code. Depending on how fast you discover this bug (which is determined by your maturity), you will lose more or less money. And you still need to fix this bug, off course.
Your systems can be hacked. Again, depending on how fast you discover this attack (which is determined by your maturity), you will lose more or less money. And you still need to fix this exploit, off course.
The fact that bugs and security breaches can cause financial damage to your organization, means that you need to be very cautious about your investments: not investing is deadly, but doing too many investments at once and not having enough credits left can make you bankrupt. And you never know up front what the financial impact of an incident will be...