The Agile Team Onion

transcript

@ewebber

The Agile team onion A model for agile teams in large organisations (or how many pizzas do you really need to feed your team?)

Emily Webber @ewebber emilywebber.co.uk / tacitlondon.com

@ewebber

Photo by Su-Lin

@ewebber

“as a team gets bigger, the number of links that need to be managed among members goes up at an accelerating, almost exponential rate. It’s managing the links between members that gets teams into trouble.”

- Robin Dunbar

@ewebber

A multidisciplinary team has all the roles it needs to design, build and operate a service

@ewebber

Photo by zacktionman

@ewebber

Security and risk

Business operations

Policy

Public relations

Finance

Suppliers

@ewebber

Photo by Katerina Hlavata

@ewebber

Photo by joinash

@ewebber

An iteration simulation

@ewebber

What really happens

@ewebber

Legal Marketing Security

@ewebber

What’s been delivered?

@ewebber

Agile team onion

@ewebber

Core team Deliver the thing

@ewebber

Collaborators specialist information, assurance as needed, reduce dependencies and blockers

@ewebber

Supporters keep informed, feed into broader organisational priorities

@ewebber

“Working directly with the legal team, with a greater understanding of each other’s challenges and constraints, led to some pretty important successes for online voter registration and the people using it.”

- Pete Herlihy product manager for online voter registration

@ewebber

Making your own Agile Team Onion

• Get the right people in the room • Map out who is in each ring • Prioritise the collaborators • Agree on what questions you need to

answer • Agree who will talk to them • Talk to them

@ewebber

Thanks.