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.

In the new remote-first and hybrid workplace, many organizations are struggling to catch up with new tooling and ways of working. Many are discovering for the first time that the physical office was covering up poorly defined teams and poorly defined areas of focus, threatening their DevOps transformation efforts and the overall health and success of their business.

Matthew Skelton and Manuel Pais, coauthors of the highly successful Team Topologies, provide proven patterns for a successful remote-first approach to teams. Using simple tools for dependency tracking and patterns from Team Topologies, such as the Team API, organizations will find that well-defined team interactions are key to effective IT delivery in the remote-first world.

This workbook explores several aspects of team-first remote work, including:

•How the new “remote-first” world is highlighting existing poor team interactions within organizations.

•Why organizations should use the Team API pattern to define and communicate the focus of teams.

•How organizations can track and remove team-level dependencies.

•How and why organizations should design inter-team communications consciously.

•How and why organizations can use the three team interaction modes from Team Topologies (collaboration, x-as-a-service, and facilitating) to help.

The ideas and patterns presented here will help your organization become more effective with a team-based, remote-first approach to building and running software systems.

Internal tech conferences can make a significant impact on an organisation's level of sharing, learning, and communication by accelerating multi-team learning across technology departments. The pace of change in IT means that cross-department learning is essential, and many organisations have found that an internal tech conference is an excellent way to achieve this.

This book provides practical advice on how to prepare, run and follow-up on an internal tech conference, together with case studies from several organisations showing the approaches in common and the adaptations for each situation.

This book is for people involved in technology leadership in some form: people in "official" positions of leadership (CIO, CTO, Head of Engineering, IT Operations Manager, etc.) and those in more informal technology leadership positions, such as team leaders, senior engineers, and people who simply like to lead by example.