Wargaming is one of the leaders in the free-to-play massively multiplayer online market that delivers authentic gaming experiences and services across PC, console and mobile platforms. The company has developed over 15 successful games, including the widely known title, World of Tanks.Targetprocess has been in use at Wargaming since 2017. This case study will focus on the implementation of automation rules in Wargaming, which was done with the help of the Targetprocess Automation Rules Engine.
We talked to Yulia Ivantsova and Diana Paliychuk. They work with the tools and processes for game development and are the ones who implement Targetprocess automations for the entire company.
We decided to look for a portfolio management tool for our company, and Targetprocess was a brilliant candidate because it’s a really unbelievably customizable and flexible tool, especially for our unique company setup.
We were shocked by how customizable and flexible the tool is and actually we still believe in that. It’s very customizable, like nothing we’ve seen before. So now we use it for lots of other projects, for various teams, and for lots of purposes, not limited to portfolio management.
Before I answer this question, I should tell you a bit more about the organization structure of Wargaming.
It consists of several divisions and departments, and Wargaming is working on several game products. It’s a massive company, so it’s not possible to say that we’ve covered this and that department. In some departments, some small teams are working in Targetprocess. In other departments, huge game development teams are working in Targetprocess. For each and every one of them, their setup will be very specific.
We’ve implemented Automation Rules for World of Tanks, and once others saw it, they wanted it. So for every person working in Wargaming, we gave them a chance to ask for some automation and we were able to do it. So it’s actually for every user of the system [Targetprocess – the editor’s note], not just for a particular team.
Just to make it clear, the World of Tanks team is pretty unique. The development team consists of more than 1,000 people in several locations spread all over the globe. Just imagine trying to coordinate them all working together. Initially, Targetprocess helped us a bit, [before the Automation Rules were introduced – the editor’s note] but just not enough at that moment.
When Automation Rules arrived, they turned out to be a real time saver. Most importantly, they help a person involved in any process for the World of Tanks team to easily contribute and perform any kind of action, and to participate in a process, no matter how complex it is, with just a few simple steps in the [Targetprocess – the editor’s note] system (because the system helps and controls).
Automation Rules make it possible to initiate dozens of rules and hundreds of actions with just one click. One click from a user and the system performs 10 actions, or 30 actions. Oh, rather 10 or 30 rules, and each rule consists of a sequence of actions, and if we count actions it would be in the hundreds.
Before Automation Rules, we used a set-up with webhooks and metrics and other automations that already existed in the system, but not all this functionality is easy to use, and it has some limits. Automation Rules do not have limits in Targetprocess.
So, at the moment, when we want to do something we just ask about the possibility, and in 99% of cases, we can do this with Automation Rules. Automation Rules, at the moment, do not have limits in Targetprocess. No other system we’ve seen allows that. They allow you to perform any action in Targetprocess automatically, or any sequence of actions, or a sequence of actions of any complexity, length or even logic. And by “any” I literally mean any. Imagine you have hundreds of sequences of rules interconnected in your system and they are all working together triggered by one another. They basically make your Targetprocess instance a living thing.
If a company is small, you can say “this process is automated”. For Wargaming it’s not possible to tell. There are hundreds of them.
The Planning 2020 for World of Tanks, across 4 locations, was an enormous event, and Targetprocess with automations really helped. It’s the latest big-impact example.
Perhaps the easiest way to explain is with numbers, there are more than 140 projects in our Targetprocess production instances, and at least 130 processes, and more than 400 rules.
To improve performance, we do not create rules that automate just one action. We always automate a sequence. So if you break them into actions you will have many more, more than 400 rules.
140+ projects, 130+ processes, more than 400 rules.
Not all of these people are working in Targetprocess [software], but I can comment on World of Tanks. We have about 1,000 people in the team, and for me it’s really my daily job to do something for automation.
There are lots of other teams that benefit from the Automation Rules in Targetprocess, because the rules help them in their day-to-day work. They make the work less monotonous and easier. It also helps to link small teams together, to help them collaborate, and sometimes even encourage whole departments to work on issues in cooperation. They help us to manage access at the same time, to keep information secure, so there are tons of examples of workflows.
It helps to link small teams together, and encourage whole departments to work on issues in collaboration. When you’re looking for an automation tool, try to understand: is it ok for your process or not? If the software says “I can do anything, just tell me exactly what you need”, it’s perfect.
When we were looking for an automation tool, we tried to understand what exactly we needed to automate. All our requirements were unique. Everything we want to do is not totally covered by any single tool. That meant we needed something that could be flexible and customizable, so we could develop something ourselves without additional development in the tool. Small automations, large-scale automations and anything else.