Agile fundamentals for teams

In this video, we're going introduce the team onion. We'll look at the structure of the model and explain how to map your own.

When delivering products and services, teams rarely work in isolation. It's likely you've already seen these challenges. Imagine you're working towards your goals. To succeed, you're often reliant on others outside your immediate group. In large organisations, like those in the public sector, this can lead to silos. As a consequence, communication between teams becomes slow and complicated.

To address this challenge, you can use the Team Onion model. This is a tool that helps teams identify their dependencies. It enables you to identify who you need to bring into your work, and when. It encourages you to think beyond your immediate team. You'll need to consider who else is crucial to deliver the product or service.

At the centre of the Team Onion is the Core Team. These are the people responsible for delivering the product or service. They'll be in regular communication with each other. This is because they're the ones working day-to-day on the product. In Agile, this might include roles like Product Managers, Developers, and Delivery Managers.

Next, we have Collaborators. These people who bring in specialist knowledge or skills. They aim to help the core team at specific stages in the development lifecycle. For example, they might provide assurance or offer specific expertise. They can help remove blockers that slow down delivery. They are not working on the product every day, but they play a crucial role in keeping things moving.

Their involvement depends on the needs of the team. So, it’s essential to communicate with Collaborators at regular intervals. The specific timing will vary depending on the context.

Finally, we have the Supporters. These are people who need to stay informed about the team’s progress. They may represent the wider organisational goals and priorities. They help ensure that what the team delivers, aligns with the bigger picture. Teams often communicate with these once per sprint or iteration. This keeps them in the loop on how things are progressing.

So how do you apply the Team Onion to your own work? Start by identifying your stakeholders. Who is in your core team? Who will be your collaborators, and when will you need their input? Finally, who are the supporters you need to keep informed?

Once you've done this, you can plan how to involve them. For example, which events do they need to attend?

Mapping out your team onion, has many benefits. You’ll identify dependencies, improve collaboration, and improve delivery.

Remember, teams don’t work in isolation. Successful delivery depends on a network of people supporting and collaborating.