Recently I heard the word scrum used to describe a type of collaborative problem solving. Having been on every aspect of a real rugby scrum (I have played every position within a scrum during six years of rugby), I was curious about this metaphor.
To see how this word is used in project development I turned to Wikipedia, which explains the terms origins this way:
In 1986, Hirotaka Takeuchi and Ikujiro Nonaka described a new holistic approach that would increase speed and flexibility in commercial new product development.[2] They compared this new holistic approach, in which the phases strongly overlap and the whole process is performed by one cross-functional team across the different phases, to rugby, where the whole team “tries to go to the distance as a unit, passing the ball back and forth”.
My own experience of a scrum does not fit that description, but is perhaps even a better analogy for true teamwork and collaboration. Here would be my own description of the scrum analogy:
Photo of Madison Women's Rugby by John Tewksbury
In a scrum, each team member has a defined role. For the scrum to achieve its intended outcome (to win possession of the ball and provide a “clean” ball to the rest of the team for play), each player must execute her own role as well as working together with the rest of the scrum on the timing of their movements. For example, the hooker has a unique role in “hooking” the ball with her foot under the legs of her team mates to secure possession of the ball. However, the hooker also needs to be concerned with maintaining a tight grip on her teammates (the props) so that they can put forth a united front and drive effectively. If one member does not understand her role and tries to do something else, it could endanger all eight members of the team (as well as the competing team for that matter!). In addition, all team members must remain aware of the movement of the scrum and be prepared to adjust accordingly. The other team may try to spin / wheel the scrum to gain possession, so each team member has a responsibility for remaining agile and responding to new information quickly.
Photo of Madison Women's Rugby by John Tewksbury
The scrum analogy is also useful for understanding different levels of system. I was focused on the individual and each person understanding her role. In addition, at the group level, the members of the scrum practice timing: tightening their grips and then driving forward in unison. At the inter-group level of system, the two opposing scrums must line up at a safe distance and at the correct alignment before engaging to prevent serious injuries. When there are rivalries or disagreements between two teams, it can sometimes show up in aggressive behaviors in the scrum. The referee in this analogy plays the important role of the regulator, ensuring that the teams are playing by the same set of rules and are engaging the safe and fair play. In an ideal game, the referee is hardly noticeable, allowing play to continue (employing the rugby law of advantage) unless there is a law violation which could result in serious injury. There are also larger levels of system in which the rugby players on the field interact with their surroundings. For example, when the ball goes out of bounds, players will sometimes yell at the fans not to touch it, because they are allowed to bring the ball back into play with a quick throw in if it has not been interfered with from the outside.
The best rugby scrums practice not just plays, but working together, quick thinking, and responsiveness. Throughout the game we would be continually feeding information to the scrum half about what was going on in the scrum and then making adjustments or reassigning roles as necessary.
