In the final installment of our series on structuring Agile teams, here is an iterative process, in the form of questions, to help project leaders design the most appropriate team structure for the project at hand.
Editor's Note: This series is excerpted from Mike Cohn’s new bookSucceeding With Agile. In part one, the author explained the importance of keeping teams small. In part two, he recommended orienting each team around the delivery of end-to-end user-visible functionality. In part three, he shared factors for making sure the right people get on each team. In part four, he explained the importance of not overloading individuals by forcing them to work on multiple projects. Here, in the final installment, he concludes with nine questions to ask when starting a multi-team project.
The following is a set of guidelines to consider in designing an appropriate team structure. Each guideline is presented in the form of a question to be asked of a current or proposed team. The questions are intended to be asked iteratively. Ask each question of a current or proposed team, changing the structure as appropriate based on the answer. As the structure changes, re-ask the questions until you can answer “yes” to each.
1. Does the structure accentuate the strengths, shore up the weaknesses, and support the motivations
"Not all chemicals are bad. Without chemicals such as hydrogen and oxygen, for example, there would be no way to make water, a vital ingredient in beer."