Public talks from Matthew, Manuel and Valued Practitioners

In this talk, we’ll explore how the patterns and principles from Team Topologies promote true business agility through a rapid flow of software change, fast feedback from running systems, a strong drive for loose coupling, and an awareness of sociotechnical mirroring. Combined with a product mindset and techniques from Domain-driven Design, the Team Topologies approach is helping organizations around the world to adapt to the “new normal” and achieve true business agility.

In this talk, [Matthew Skelton] [Manuel Pais], co-author of the book Team Topologies, explains why the platform-as-product approach can be a game-changer for organisations building and running software-enabled products and services.

Organization architecture and software system architecture need to be co-designed to avoid friction from Conway's Law. Based on ideas in the book Team Topologies, this talk by co-author Matthew Skelton explains how and why to bring together HR and Engineering to shape team boundaries and interactions for effective software delivery.

By re-thinking our team structures and how they interact with security teams we can find effective, team-oriented ways to beat the negative effects of that 1:100 ratio. This is what we did with DevOps, right? The DevOps topologies catalog compared and contrast different team organization models to enable sharing of knowledge and responsibilities between dev and ops.

Remote-first work is the "new normal" for companies around the world. There is no shortage of advice on how individual teams can bond and work effectively remotely.

However, there is not much on how to address remote interactions between different teams that need to collaborate remotely, as part of the same value stream. Moving from the physical to the online world can further expose pre-existing interaction problems, increase wait times and slow down delivery and possibly response to incidents.

Based on the ideas from Team Topologies, here are some useful approaches to clarify and evolve inter-team interactions and communication in this remote-first world.

This talk covers the basics of organization design using Team Topologies, exploring a selection of key team types, and how and when to use them in order to make the development and operation of your software systems as effective as possible. Key takeaways: 1. Why using the “Spotify Model” of team design is not enough 2. The four fundamental team topologies needed for modern software delivery 3. The three team interaction modes that enable fast flow and rapid learning 4. How to address Conway’s Law, cognitive load, and team evolution with Team Topologies

DOES19 London — The “monoliths vs microservices” debate often focuses on technological aspects, ignoring strategy and team dynamics. Instead of technology, smart-thinking organizations are beginning with team cognitive load as the guiding principle for modern software. In this talk, we explain how and why, illustrated by real case studies.