Member-only story
Why Agile Teams Should Play Chess
Imagine a game of chess. 16 pieces, 64 squares and two opponents. It’s a very simple and controlled environment. However, after three moves each by black and white there are over nine million possible next moves.
The number of possible unique chess games is far greater than the number of electrons in the universe (roughly 10¹²⁰ vs. 10⁷⁹).
The astronomical complexity of chess is what creates the universal reverence for the game. In other words, it’s really difficult to be really good. You have to think as you play. Adaptability is the number one competitive advantage.
Both chess players and agile teams have to make lots of small and short-term decisions over time to achieve long-term strategies.
So, if you want to be a more effective agile team, you could start by playing more chess.
Good chess players start with overarching rules which they interpret to decide on the best moves that lead to winning games. When things get difficult and they need to adapt, they are able to use their creativity and logic to come out on top. Bad chess players play individual moves with no regard for overarching rules. They inevitably fall prey to their more adaptable opponents.
