Quboo games gives you the option to get score based on some possible actions:
- When you fix a Sonar Issue that was created before a given date. The score you get is proportional to the amount of debt you are paying (calculated by Sonar).
- When you release your project.
- When you write documentation.
You can choose to integrate Quboo with all these Game Modes or play only one, depending on the needs of your teams.
Badges are just a nice status that you may obtain by performing certain actions. This is a growing list, since the Quboo Team is introducing new badges every now and then:
- Early Bird (Sonar Game). If you get score very early during a given campaign.
- Unit Tester (Sonar Game. Depending on how much test coverage you’re adding, you get one or more of the UT Ranks.
- Security Guard (Sonar Game). Fix at least one issue of type Vulnerability.
The Quboo Leaderboards are sorted lists, by score in descending order, of your players and teams (whose score is just the sum of the score of all its players).
These are the main screens in Quboo and contain all you need to know the status of the game: the scores, badges, who is winning at a given time and campaign information.
A Quboo Campaign defines the period of time you’re playing to become winner, which means having the highest score when the campaign finishes. They have a defined start date and end date and, by default, campaigns in Quboo are sequential. Your next campaign will start the day after the current campaign finishes.
Every new campaign all the statistics are set to zero. This is very important in the game because it allows everybody to compete.
You can organize your players in teams. This encourages everybody to participate since teams also compete with each other.
The game’s objective is to become winner by the end of a campaign. If you want, you can introduce small rewards for the winners so it’s even more encouraging: tees, mugs, gift cards, etc.
Anyway, keep in mind that the game is ultimately a way to make some actions more interesting. Your real rewards are reducing technical debt, increment your release pace, improve your documentation, etc.
Keep it fun
We like Quboo because it spices up the process. However, there are also other people that feels manipulated by it, even if you clearly state that it’s not the reason why you introduce the game. This may happen and it should be seen as normal. It’s the main reason why participating in the game should be optional.
Try to avoid making Quboo a serious topic: do not link it to company goals, do not use it for team/personal performance evaluation, do not offer big rewards.
It is important that, if you introduce this game in your organization, you explain it honestly: what you want to achieve and how to play. There will be people who like it and people who don’t. And, whatever the result is, feel free to share the feedback with us.