I spent many hours of my life playing RPGs. It started in a secondary school with “talking” D&D and Warhammer, and then smoothly moved to less problematic computer games such as Icewind Dale (I still have nightmares related to the second part), Baldur’s Gate, Neverwinter Nights, Morrowind (which is probably my favorite one), and phenomenal The Witcher, of course.

A few years later I logged into World of Warcraft for a while and … logged out after almost two years, due to the necessary visits to the addiction treatment center. Oh, I had a similar love story with Football Manager, but only a few will understand this fascination;)

Why am I writing about it?
What turned me on the most in role-playing games was building a team from characters with different traits (races, classes, specializations), leveling them by gaining experience points, and — in the case of WoW — a team PvE mode.
What always interests me at work are the people I work with. Mindset, Skills, Tools, Communication, Communication.

Comparing a fearless group of adventurers who are trying to get the magical artifact guarded by a terrifying and invincible demon, to the development team trying to deliver features to the Client is… funny :) Let’s say that our Deamon’s name is Deadline, his Minions are Users, and our boring daily work turns into a pretty good dungeon.

To be clear: the main boss is NOT the Client, although I know the comparison fits very well in many projects :P The client, or his representative, should be a part of our Team.
I am saying it quietly, bowing my head under the burden of my own mistakes.

Let’s build the Team!




Ok, that’s naturally Project Manager, right? No. I see here rather a Scrum Master, and the keyword here is Servant Leader — a person who takes care of other team members and has the Client in the context. He has to observe, he has to react, and he has to have a brain in addition to his eyes. He needs to be responsible for the entire team. This role is a bit ungrateful because people pay attention to it (they shout at this person and swear) usually when they die, but when everything is going fine then no one thinks about healers. But often when Manager wants to build a team he is looking for Healer at first.


In the professional reality, we have different projects, different pressures, and we have to have in mind not only technology, infrastructure, but also the composition of the team and different characteristics of the members. I saw and participated in projects where there was chaos, although the team was consist of great specialists


It was the point that began my fascination with agile and Scrum because tools such as pair programming, planning poker, daily scrum are mainly aimed at improving the quality of communication, so understanding, so efficiency, and helping to respond better to the crisis in the project.
Then the technical quality comes by the way.

And to be clear: communication in scrum is not daily scrum moved into the waterfall and “more talking than doing” just so that the Project Manager or Team Leader can build and satisfy their comfort zone;) by maximizing micromanagement.


Yet another thing is metaphors. One of the best books I have read about Scrum is “Scrum. How to manage agile projects. “ written by Mariusz Chrapko. This reading helped me to realize that scrum, and especially its translation, is a constant play with words and metaphors. We build an abstraction that allows us to better focus on the goal and achieve it effectively because everyone understands the story they are actors of.

Games can be understood by little children. If you have made it so far, thank you, and feel free to share your thoughts in the comment section below. I am glad if this post provokes someone to reflect on the perception of the team, co-workers, or employees. And games, of course.

Agile Web Developer