|Entry for hiranabe||Syndicate hiranabe's entries|
A tree grows stronger and a river runs longer -- Two types of scaling Agile
Author: hiranabe (7:55 am)
After Agile has been adopted so widely, scaling agility across the enterprise is now a topic for these years.
In this blog, I ponder two ways to scale Agile -- a "Tree" and a "River" as metaphores in the mother nature.
This is a natural extension of Scrum from a team to a project of scrum teams or a progam of scrum projects, and maybe to a company with a product portofolio.
In this model, typically each scrum team has standups everyday and retrospectives after each sprint, while scrum masters form an upper level scrum and have standups and retrospectives after the ones of the sub-teams. Even a company board meeting can be seen as a top level scrum. In this way, tree type scaling shares (and needs) strong synchronization of the teams though out the organization. I assume Jeff Sutherland's Patient Keeper and its Type C Scrum is a good example of this strong "scrum" company.
A tree shares a rhythm, location, climate, mood and so on as a living thing. It scales strongly but within a size of tree.
The other scaling strategy is to connect different teams such as a marketing team, development team, and QA teams with queues between them.
I would call this a "River" or lean type scaling, where multiple teams
work asynchronously in their own rhythm and culture using buffers inbetween. Lean is an attitude to make value flow seeing the whole.
In this "river" type, even the concept of iteration is not necessary. Using kanban or other information-sharing and buffer-management tool, the work flows from upstream to downstream through the whole value stream across the enterprise.
A river runs through countries sharing a flow, but each country has its own climate, rhythm and culture.
When scaling Agile, a company with less than 100 employees, like an energetic startup, can and should use tree type scaling to get a whole company agility and to create value from its teams. It is like a growing tree pumping water and nutrients from the soil, sharing one strong culture and sense of timing in possibly a collocated workplace.
On the other hand, a big company with different division cultures or a big project with multiple companies, can use river type scaling
more effectively because each sub-team naturally has different rhythms and wants to move independently from the other teams. It is like a river runs across a continent making a value flow to the ocean connecting different regions.
Tree scales with a stronger synergy, while a river scales a lot broader.
Trackback URL of this entry
Posted: 2010/4/30 9:28 Updated: 2010/4/30 9:28
awesome post! You can indeed combine the two models, using a pod of a tree flowing through the river, to make efficient scaling in larger organizations.