Today, we premiere the second and final episode in our two-part series with DevOps experts Matthew Skelton and Manuel Pais, authors of the new book Team Topologies: Organizing Business and Technology Teams for Fast Flow. If you haven’t listened to the first episode, I highly recommend checking it out.
In episode 2 we discuss strategies for reducing the cognitive load on a team, how to build organizational trust to allow for fast change, and the theory behind reversing Conway’s Law to produce sustainable system architecture.
Also be sure to check out the Team Topologies Academy for more insights and custom-built courses.
Listen to the full episode
Episode Highlights Include:
What is “Conway’s Law” and its relation to system architecture
Reducing cognitive load to improve productivity
How a high degree of trust allows for fast change
The optimal number of people to put on a team
Patterns to help teams discover success
Flow efficiency is the 5th key metric
If you haven't already heard, Dev Interrupted is partnering with Dzone to host INTERACT: An interactive, community-driven, digital conference on September 30th - by engineering leaders, for engineering leaders. 1 day, 10 speakers, 100s of engineers and engineering leaders, all free.
Register Now
Join the Dev Interrupted Server
With over 1500 members, the Dev Interrupted Discord Community is the best place for Engineering Leaders to engage in daily conversation. No sales people allowed. Join the community >>
*Originally published at [https://devinterrupted.com]
Top comments (2)
Trust on teams is everything and will improve a lot more than just flow efficiency.
The bit about team size, be it a dev team or a football team, is interesting. Makes sense that the optimal size of a team is under 15 people.