Home » Software Development

The ScrumMaster as a Chess Master

30 April 2013 No Comment

In the preface of his book Essential Scrum, Kenneth Rubin writes “giving a new Scrum team just The Scrum Guide and expecting good results would be like giving a new chess player a 15-page description of the rules of chess and expecting her to be able to play a reasonable game of chess after reading it.”

I like this analogy as the basic rules of Scrum seem simple, but a successful Scrum project, like a good chess game, depends on the ability to use these rules in the game context. Like Scrum, a chess game starts with a limited set of simple rules and six types of pieces. It is however the diversity of the situations that makes difficult to play chess at high level. Incidentally, chess has also a “timeboxing” feature as you are allowed only a limited amount of time to make all your moves. I admit having had only a limited practice with chess years ago, but I think that ScrumMasters and project managers could be inspired by some of the chess masters’ best practices.

Chess masters learn by heart all the classical openings of their game. ScrumMasters should study the Scrum theory to understand the trade-off of their choices in all situations. Chess masters use the lessons from previous games and know by heart the full detail of historical games. ScrumMasters should participate to conferences or local Scrum groups meetings to learn from the experience of their peers. When they compete in a chess tournament, important chess masters have an advisory team to help them see the game with a different perspective. ScrumMasters should have a network of fellow ScrumMasters that will serve as a sounding board when they face some issues. Chess masters have an initial strategy but should be ready to change it during the game to counter the opponent moves. ScrumMasters should be able to react to every event that happens to the project. Chess masters are ready to sacrifice a piece to gain a better position. ScumMasters have to be ready to suffer some short-term pain if this should lead to long term gains. They will not dictate team decisions and allow team members to make “mistakes” if they could learn from it and change their practices.

Chessboard: ScrumMaster as a Chess Master

There is however a big difference between the game of chess and Scrum: people are not pieces that you can manipulate at will. The moves of chess pieces are strictly regulated. Their number and characteristic defined at the beginning of the game. Personal reactions of Scrum team members are not (completely) predictable or logical. On the positive side, the ScrumMaster could be able to create its own team or change team members in case of problems. Being a good chess master, ScrumMaster or software developer is also based on how much theory and experience, yours and those from others, you can use to think about when you have to solve problems. Nothing replaces the time you need to spend to acquire it. And this could be the last lesson from the chess masters: even if you are talented, you have to work hard to become one.

Related Content:

Comments are closed.