Team Topologies book signing tour - when and where
Team Topologies book published - paperback, ebook, audiobook
Matthew and Manuel will be presenting and signing their book at several events until end of 2019: DevOps Summit in Amsterdam, DOES US in Las Vegas, SQS-Tag in Frankfurt, Jenkins World in Lisbon, and Seacon in London.
Join to receive a signed free copy of the book!
Podcast with Deloitte - Building Great Software Takes Great Teams and Communication
We’re thrilled to announce that the book Team Topologies: Organizing Business and Technology Teams for Fast Flow by Matthew Skelton and Manuel pais has been published by IT Revolution Press and is now available in paperback, Kindle, and audiobook from stores around the world.
Enterprise DevOps Skills Report - how team boundaries affect job roles
I recently joined Mike Kavis of Deloitte on his OnCloud podcast to talk about team communication for effective software delivery. We covered the original DevOps Topologies patterns and how these have been used in industry, and then talked about what’s in the book Team Topologies: well-defined team types, what we mean by a modern platform, team interaction modes, clear responsibility boundaries, DevEx, and using difficulties in team interactions as ‘signals’ to the organization that something is missing or misplaced. We also talked about moving beyond the Spotify model - success in software delivery is not just about team structures but about how teams interact and what kind of relationships they create, sustain, and evolve.
Why we wrote the Team Topologies book
The DevOps Institute has published the Enterprise DevOps Skills Report 2019 covering the in-demand skills for software development in enterprises around the world.
The original DevOps Team Topologies - which ultimately led to our Team Topologies book - are mentioned in the report in the context of different kinds of teams to help make DevOps work.
The book Team Topologies has been 5 or 6 years in the making. How did we (Manuel and I) come to write to book and why?
In our travels around the world helping organizations with software delivery practices, we noticed that organizations needed guidance on how to evolve team interactions. We also saw that in many organizations the boundaries between teams are very unclear: people were asking “why are we spending so much time working with that other team?” or “why is this service so difficult to use?” - very often there was little clarity about the purpose and duration of team-to-team interactions.