Other Sellers on Amazon
Enter your mobile phone or email address
By pressing ‘Send link’, you agree to Amazon's Conditions of Use.
You consent to receive an automated text message from or on behalf of Amazon about the Kindle App at your mobile number above. Consent is not a condition of any purchase. Message and data rates may apply.
Follow the Authors
Team Topologies: Organizing Business and Technology Teams for Fast Flow Paperback – Illustrated, 7 September 2019
Enhance your purchase
Frequently bought together
"I have found Matthew and Manuel's work on patterns and language to be incredibly valuable in both shaping strategies to transform team contexts over time across our organization, as well as in helping business and technology leadership connect with the topics of flow and continuous delivery."--Richard James
"The high performing team is the core generator of value in the modern digital economy. But cultivating and scaling an adaptive ecosystem of such teams is a too-often elusive goal. In this book, Skelton and Pais provide 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 and Global DevOps Lead, Forrester Research
"DevOps is great, but how do real-world organizations actually structure themselves to do it? You can't just put everyone on a single, silo-less team, all sitting together in one giant open-plan office and going out to lunch or playing foosball together. Team Topologies provides a practical set of templates for addressing the key DevOps question that other guides leave as an exercise for the student."--Jeff Sussna, Founder & CEO, Sussna Associates, and Author of Designing Delivery
"DevOps Topologies is an outstanding resource for all technical leaders pushing for modern approaches to effective partnerships between Development and Operations. It goes beyond high level explanations of DevOps offering that there are many flavors that a company may choose to adopt based on a few factors including maturity, size and product landscape. At Condé Nast International, this resource was crucial in understanding our current DevOps state and in defining the vision for our aspirational DevOps operating model. We were able to navigate around the pitfalls and organizational anti-patterns as excellently described in the models. The models themselves proved extremely useful artifacts in aligning both stakeholders and teams directly involved. Lastly, I introduced a new function to the business which hadn't existed before: Site Reliability Engineering. The DevOps Topologies resource was a primary resource in firstly convincing myself that we had matured and grown to a point to justify SRE, but also in articulating to the business stakeholders the strategy for our new DevOps model. I am extremely pleased that Matthew and Manuel are growing on the success of the DevOps Topologies website and turning their further learnings into the far-reaching Team Topologies book for organization design."--Crystal Hirschorn, VP of Engineering, Global Strategy and Operations at Condé Nast
"I've long enjoyed learning from Matthew's and Manuel's work, and have been recommending their content to clients and peers for several years (in particular, DevOpsTopologies.com). It's great to see that their wisdom for organizing teams has been collated into a single book, because as the cliché goes, the hard stuff when working in an organization is always in relation to the 'soft' skills (and people and teams). If you're looking for an analysis of the challenges with the traditional ways of working, and also some practical guidance on mitigation strategies (e.g., new interaction modes, reducing cognitive load, and creating appropriate 'Team APIs'), then this is the book for you!"--Daniel Bryant, Technical Consultant/Advisor and News Manager at InfoQ
"Matthew Skelton and Manuel Pais say 'Team Topologies is meant to be a functional book'--and it is. It's well constructed and signposted, based in sound thinking, and challenges readers to assume, like them, that an organization is a socio-technical system or ecosystem. From this assumption comes practical suggestions, no prescriptions, and skill in explaining an approach that provides for effective tech/human organization design. For anyone in the tech/organization design field, [Team Topologies is] well worth reading."--Dr. Naomi Stanford, Organization Design Practitioner, Teacher, and Author
"Team Topologies makes for a fascinating read as it explores the symbiotic relationship between teams and the IT architecture they support. It goes beyond the common approach of static org charts or self-organizing chaos and shows how to evolve the people system and IT system together."--Mirco Hering, Global DevOps Lead Accenture and Author of DevOps for the Modern Enterprise
"There is nothing more fundamental to management than how you structure your organization and what behaviors you encourage. Despite this, few have attempted to catalog and analyze the organizational design patterns of IT organizations going through Digital, DevOps, and SRE transformations. Skelton and Pais have not only accepted this bold challenge, but they've also hit the mark by creating an indispensable and unique resource."--Damon Edwards, Co-Founder of Rundeck
"When your teams encounter friction and bottlenecks it can be tempting to throw more people, tooling, and process at the problem. Your solution likely lies in a new team topology. But what should that look like? Team Topologies provides a much-needed framework for evaluating and optimizing team organization for increased flow. Teams that have the right size, the right boundaries, and the right level of communication are poised to deliver value to the company and satisfaction to the team members. Team Topologies combines a methodical approach with real-world case studies to unlock the full potential of your tech teams."--Greg Burrell, Senior Reliability Engineer at Netflix
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
"Teams are the fundamental building block of organizations, how those teams work and the system they operate in are the difference between average and high performance. I believe this book is a deep well of information for how you can optimize your organization's system for your current context."--Jeremy Brown, Director, Red Hap Open Innovation Labs EMEA
"The Team Topologies book by Matthew Skelton and Manuel Pais is unique. It is going to have a big influence across tech companies. We need a structured and methodical approach to shaping teams for continuous delivery instead of copying a few Spotify rituals. This is the book."--Nick Tune, API Platform Lead, Navico
About the Author
- Publisher : It Revolution Press; Illustrated edition (7 September 2019)
- Language : English
- Paperback : 240 pages
- ISBN-10 : 1942788819
- ISBN-13 : 978-1942788812
- Dimensions : 15.47 x 1.52 x 22.5 cm
- Best Sellers Rank: 19,205 in Books (See Top 100 in Books)
- Customer Reviews:
Review this product
Top reviews from other countries
This collection of evidence and advice is perfectly paced, interesting, and has a lovely non-dry style that keeps you engaged. It explains an awful lot about the basics and more interesting personal interaction of Team Management that are not taught, and managers are expected to gain - experience says they often don't and wing it.
If, like myself, you have had the great fortune in the past of leading a true agile environment, and then the misfortune to have to change job to non-agile environment with a futile management team then this book will help you re-evaluate and realise you were not mad. If after presenting this information to that management then I leave you with the only option you have: GET OUT!
What's more, they do a great job of citing other important works on the topic so that the reader can follow ideas back to their source: Melvin Conway, James Lewis, Daniel Pink, Evan Bottcher, Michael Nygard, Nicole Forsgren, Jez Humble, Gene Kim, Allan Kelly, John Roberts, Don Reinertsen and many more are liberally quoted throughout the text. That makes this book a great summary work on a topic of vital importance to any software organisation of any size - how do we best divide the work so that teams have the best possible chance of success?
I did feel however the overall content of the book could have been written in 40 pages, a lot of repetition and use of academic language when a simpler conversation style would have sufficed. It led to cognitive overload which is ironic