...and asked what we think of when we picture a chaotic team. Our answers were:
- Unpredictable results
- Difficult to manager
Then he added another word:
... and asked what we think of when we picture an orderly team. Our answers were:
- Easy to manage
He then pointed out that both chaos and order have good and bad aspects. Though wild, a chaotic team is free to experiment and be innovative, and though easier to manage, an orderly team's innovation can be stifled. So there is a line between chaos and order, and it's on that line that an Agile team rides. But the line is not a straight line. It moves back and forth over the life of a project. Sometimes a team is more orderly and other times they are more chaotic. Looking at it this way, the line is really a wave between chaos and order alternately drifting between the two.
Taking that a step further we can say that Agile teams "surf" this wave through the life of the project. And like surfing it is easy to fall. A team can very quickly fall into too much chaos and become uncontrollable. And just as quickly a team become too ordered where no new ideas are sparking.
One of Scrum's tag-lines (as well as one of it's founder's website) is Control Chaos. This is the essence of Scrum. Just enough chaos to be free thinking and just enough order to be successful.