Organizing Business and Technology Teams for Fast Flow
Paperback, 240 pages
English language
Published Nov. 20, 2019
Effective software teams are essential for any organization to deliver value continuously and sustainably. But how do you build the best team organization for your specific goals, culture, and needs?
Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns. It is a model that treats teams as the fundamental means of delivery, where team structures and communication pathways are able to evolve with technological and organizational maturity.
In Team Topologies, IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and evolve the right team patterns for their organization, making sure to keep the software healthy and optimize value streams.
Team Topologies is a major step forward in organizational design for software, presenting a well-defined way for teams to interact and interrelate …
Effective software teams are essential for any organization to deliver value continuously and sustainably. But how do you build the best team organization for your specific goals, culture, and needs?
Team Topologies is a practical, step-by-step, adaptive model for organizational design and team interaction based on four fundamental team types and three team interaction patterns. It is a model that treats teams as the fundamental means of delivery, where team structures and communication pathways are able to evolve with technological and organizational maturity.
In Team Topologies, IT consultants Matthew Skelton and Manuel Pais share secrets of successful team patterns and interactions to help readers choose and evolve the right team patterns for their organization, making sure to keep the software healthy and optimize value streams.
Team Topologies is a major step forward in organizational design for software, presenting a well-defined way for teams to interact and interrelate that helps make the resulting software architecture clearer and more sustainable, turning inter-team problems into valuable signals for the self-steering organization.
Book with a simple, useful and actionable message: design software architectures and team interactions together, since they are similar forces. And a nice and simple model of four team types.
For me the most important notion was that teams have to be dynamic but stable (systems, anyone?) and a nice classification of teams that will allow me to work out a said dynamic for my R&D heavy customers.
Stream-aligned team: aligned to a flow of work from (usually) a segment of the business domain
Enabling team: helps a Stream-aligned team to overcome obstacles. Also detects missing capabilities.
Complicated Subsystem team: where significant mathematics/calculation/technical expertise is needed.
Platform team: a grouping of other team types that provide a compelling internal product to accelerate delivery by Stream-aligned teams
