In 2016, I first introduced the Team Onion model (as the Agile Team Onion). Since then, it’s had a few iterations and now has a new website home of its own at teamonion.works.
Continue reading
A blog about people, teams, culture, organisations, agile delivery and other things
In 2016, I first introduced the Team Onion model (as the Agile Team Onion). Since then, it’s had a few iterations and now has a new website home of its own at teamonion.works.
Continue readingThe Team Onion now has a new home at teamonion.works
**UPDATE** The Agile Team Onion is now the Team Onion, same model slightly new name. Because you don’t need to be an agile team to use it.
I’ve recently been playing with ways of explaining the extended team for large and largeish organisations. I get frustrated when I see Agile teams that are essentially siloed off from the wider business (for many reasons). This causes dependency and communication issues and means they just aren’t able to deliver anything very quickly. I don’t think the answer is just to throw everyone in together as it’s not always that practical and can cause its own communication issues as the team gets really big. I’ve been using the team onion to describe a model of how it might work.
Continue reading