This guest lecture at the Masters of Software Engineering graduate program covers common organizational challenges to achieve fast flow and high performing teams. Key aspects of Team Topologies that are covered include the four fundamental team types, the team API, cognitive load, and the three core team interaction modes.
The Elephant in the Kubernetes Room: Team Interactions at Scale @ Velocity Be...Manuel Pais
Semelhante a Fast Flow & Organizational Evolution with Team Topologies @ Masters of Software Engineering (MSE) - Carnegie Mellon University, Apr 2021 (20)
2. Manuel Pais
2
Co-author of the book Team Topologies
IT organizational consultant and trainer
Ex-dev, ex-build manager, ex-tester,
ex-team lead, ex-DevOps lead
MSE 2010 Alumni
3. Team Topologies
3
Organizing business and
technology teams for fast flow
Matthew Skelton & Manuel Pais
IT Revolution Press, 2019
teamtopologies.com/book
4. 4
Philip Fisher-Ogden,
Director of Engineering at
Netflix:
“thanks for your insightful
articulations of devops
topologies. They inspired
many discussions and
helped us to think about
what model Netflix teams
could be/are using.”
https://twitter.com/philip_pfo/status/999074792123740160
5. topology
the way in which constituent parts are
interrelated or arranged
Greek: τοπολογία (τόπος == ‘place’)
5
21. “Great products emerge from
empowered, fully cross-functional
teams.”
– John Cutler, 2019
21
22. “Despite striving to be
cross-functional, one of the thornier
problems product teams often face is
lacking some necessary
competence.”
– Peter Neumark, 2015
22
52. “A digital platform is a foundation of
self-service APIs, tools, services,
knowledge and support which are
arranged as a compelling internal
product.”
– Evan Bottcher, 2018
52
53. “A digital platform is a foundation of
self-service APIs, tools, services,
knowledge and support which are
arranged as a compelling internal
product.”
– Evan Bottcher, 2018
53
54. A good platform is
treated as a product
(reliable, usable,
fit for purpose)
54
62. “For effective team-first ownership
of software, teams need to
continuously define, advertise, test,
and evolve their Team API”
Team Topologies, p.48
62
63. Team API
63
● Code & artifacts owned by the team
● Versioning & testing approach
● Wiki and documentation
● Ways of working
● Roadmap & priorities
● Communication preferences (when/how)
70. 70
When used with care, these are the only
four fundamental team topologies
and three core interaction modes
needed to build and run
modern software systems.