Again, the grid:
| OPTIMIZING / GROUPING | INDEPENDENT | MANAGED | TRIBAL |
|---|---|---|---|
| INTUITION | Hero | Supernanny | HPT |
| PLANNING | Caterer | Director | |
| FEEDBACK | Scientist |
Filling out the rest of the grid turns out to be pretty easy once we have this framework.
the best known managed-feedback system in American industry is 6-Sigma. The best known examples of tribal planning situations are groups of very smart engineers or physicists solving very hard, long-term problems, for instance among the NASA mission control engineers. And one of the only known tribal feedback systems yet invented is the eXtreme Programming (XP) discipline of software development. Also, parts of the Toyota Production System, and some of the modern U.S. Marine tactics described in their strategy manual: Warfighting.
| OPTIMIZING / GROUPING | INDEPENDENT | MANAGED | TRIBAL |
|---|---|---|---|
| INTUITION | Hero | Supernanny | HPT |
| PLANNING | Caterer | Director | Mission Control |
| FEEDBACK | Scientist | Six Sigma | XP Team |
Given this grid, we see several interesting questions to ponder:
Where do you most want your teams to be on this grid? What row and/or column do you not want your teams to be in?
Can you name people who live in different grid-locations than you do?
What row or column is central to the Agile software movement? What about the signatories on the Agile manifesto? And what row and/or column are they pushing against?
Where does RUP fall? Classic waterfall? Rapid prototyping?
Exactly how unlike Kanban or Scrum is XP or BDD?
One Reply to “The Method Grid”
Comments are closed.