Cheat notes · Module 02 · The product and its people
Teams and how they work together
A five-minute review for when you have done this module and want it back in your head. Open the full module for the steps and the lab, or the full text to print.
The idea
A platform team exists to reduce product teams' cognitive load. Team Topologies names four team types and three interaction modes, and collaboration is planned to end in X-as-a-Service.
Remember
- Team types: stream-aligned, platform, enabling, complicated-subsystem.
- Modes: collaboration (costly, temporary), X-as-a-Service (the default for a working platform), facilitating (teaching).
- Collaboration needs
untilandtheninteams.yaml(ruleT4). - The owner in
platform.yamlmust be a team of typeplatform(T5). - From here on every
ownermust be a team inteams.yaml(O1).
Pitfalls
- A collaboration with no end turns the platform team into part of one product team.
- An owner that is a stream-aligned team fails
T5.
Test yourself
Answer in your head first, then open the answer.
Which mode should most teams have with the platform most of the time?
X-as-a-Service.
What is an enabling team for?
Helping other teams learn a skill, then stepping back.
Why does collaboration need an end date?
It costs both teams time; the platform team can only do it with a few teams at once.
Where module 02 leaves you: teams.yaml passes the check, and the check now also confirms that the owner in platform.yaml is a platform team. The platform team collaborates with checkout until a date, and then becomes X-as-a-Service.