Video: The Scaling Dilemma - Mary Poppendieck
1.) COOPERATION
cross functional team is still a silo
team does not cooperate across teams, so silo, just multi functional silo
autonomy being so important, that
how do businesses work when large
the entire problem of large companies is the balance between autonomy and cooperation
What is the ideal team size? Agile answer is 7+-2
Robin Dunbar
inner circle | 3-5 | very close friends or family members |
sympathy group | 7-10 | close friends who care about each other's fate |
hunting group | 30-50 | collegues who care about each other's fate
-how much it takes to achieve a goal |
clan | 100-150 | people who maintain stable inter-personal relationships
-everybody knows eachother
-peer pressure works |
tribe | 500-2500 | people who speak the same language or dialect |
go modular
remove dependencies - also in codebase
That's how many it takes to bring a project like this to the market.
how Pixar managed to have great teamwork in big team ~200
When you get bigger than 7+-2
you still wanna have one team
maybe multiple sub-teams
but only 1 team goal
nobody succeeds unless that one succeeds
A) Shared Responsibility
Everybody succeeds or fails together
everybody on the team maintains situational awareness
What makes scaling work?
"Shared goals with situational awareness across the teams that share the goal"
2.) COMPLEXITY
how to get it stable?
where it's actually in production
How to poke your code base?
split deployment vs release with feature toggles
microservice = independently deployable
build, maintain, monitor, fix
extensive automation and monitoring
