Team Topologies

image

Team Topologies: Organizing Business and Technology Teams for Fast Flow

Published September 2019 by IT Revolution

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.

image

IT Revolution is the home of some of the most influential and well-respected books for the modern enterprise, including: Accelerate, The Unicorn Project, DevOps Handbook, The Phoenix Project, Project to Product, Making Work Visible, and more.

Translations of Team Topologies: vote for a language

We have many requests for translations of the Team Topologies book. Please vote on our Upvoty page to help prioritize the translations!

"...innovative tools and concepts for structuring the next generation digital operating model. Recommended for CIOs, enterprise architects, and digital product strategists worldwide."

—Charles Betz, Principal Analyst, Forrester Research

"Team Topologies informs and enriches our understanding of organizational architecture…it serves as a pragmatic guide whether forming teams and enabling them to meet their challenges or helping existing teams become more effective at responsive value delivery."

—Ruth Malan, Architecture Consultant at Bredemeyer Consulting

Details

ISBN: 978-1942788812 Paperback: 240 pages Publisher: IT Revolution Press (September 7, 2019) Language: English

Buy now from bookstores worldwide

We’ve partnered with Agile Stationery to offer a set of physical Team Topologies resources - including the book - for worldwide delivery.

image
image

Amazon.cn (CN) - Paperback (高效能团队模式) Amazon.com (US/CA) - Paperback | Kindle Amazon.co.uk (UK/EU) - Paperback | Kindle Amazon.com.br (BR/SA) - Paperback | Kindle Amazon.fr (FR/EU) - Paperback (broché) | Kindle Amazon.es (ES/EU) - Paperback | Kindle Amazon.co.jp (JP) - Hardback | Kindle (チームトポロジ) Barnes & Noble (US/CA) - Paperback | eBook Bertrand (PT/EU) - eBook Book Depository (World) - Paperback DangDang (CN) - Paperback (高效能团队模式) Elephants (HK/CN) - Paperback Fnac.com (FR/EU) - eBook Fnac.pt (PT/EU) - eBook Fnac.es (ES/EU) - eBook JD.com (CN) - Paperback (高效能团队模式) Kobo (World) - eBook OpenTrolley (SG) - Paperback Powell’s (US/CA/World) - Paperback Rakuten (FR) - Broché Thalia (DE/AS/CH) - Paperback Wook (PT/EU) - eBook Wordery (UK/EU/World) - Paperback eBooks (World) - eBook

Note: there are no PDF versions of the book on sale at this time.

image

Errors (Errata)

Here are the known errors (errata) in the Team Topologies book.

Chapter 1, page 5: “negligent” should be “negligible”. Chapter 1, page 32: Dunbar’s Number should be identified as 150, not 15. Chapter 2, page 26: “(See Chapter 9 for more on patterns” should be “(See Chapter 8 for more on patterns Chapter 2, page 29: "(...) you will be able to takeadvantage of the isomorphic force (...)." should be “(...) you will be able to take advantage of the isomorphic force (...).“ Chapter 3, page 49: “desks at guilds, communities of practice (a group of people...)” - missing closing parenthesis at the end of the sentence. Chapter 4, page 75: “Architext” should be “Architect”. Chapter 5, page 85: “ations than either "product" of "feature"“ should be “ations than either "product" or "feature"“. Chapter 7, page 136: “(Care must be taken to not let the number of people exceed Dunbar’s number of fifteen)“ should read “(Care must be taken to not let the number of people exceed the Dunbar trust boundary of fifteen) Chapter 7, page 138: the text should read: “In this case, the team on the left is providing something “as a service” to the team on the right… “ Conclusion, page 185: “team-fist“ should be “team-first” Glossary, page 187: Dunbar’s Number should be identified as 150, not 15.

Thank you to everyone who has reported an error - we really appreciate it!

Have you spotted an error?

If you spot errors in the book, please make a note of the chapter and page number. When you’ve completed the book, send us your list of errors.

References

A full list of references in several formats (BibTeX, CSV, Endnote, Markdown, Refworks, and Zotero) is available on our GitHub repo: