Be the first to like this
For effective, modern, cloud-connected software systems we need to organize our teams in certain ways. Taking account of Conway's Law, we look to match the team structures to the required software architecture, enabling or restricting communication and collaboration for the best outcomes.
This talk will cover 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. The talk is based on the forthcoming 2019 book Team Topologies and first-hand experience helping companies around the world with the design of their technology teams.
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
Bio: Matthew Skelton is the Founder and Head of Consulting at Conflux. He has been building, deploying, and operating commercial software systems since 1998. As Head of Consulting at Conflux, he specialises in Continuous Delivery, operability and organisation dynamics for software in manufacturing, ecommerce, and online services, including cloud, IoT, and embedded software.
Recognised by TechBeacon in 2018 as one of the top 100 people to follow in DevOps, Matthew curates the well-known DevOps team topologies patterns at devopstopologies.com and is co-author of the books Continuous Delivery with Windows and .NET (O’Reilly, 2016), Team Guide to Software Operability (Skelton Thatcher Publications, 2016), and Team Topologies (IT Revolution Press, 2019).
Matthew founded Conflux in 2017 to offer training and consulting to organisations building and running software systems.
From a talk at Agile Yorkshire on 20 March 2019 http://www.agileyorkshire.org/event-announcements/wed20thmarch-andybutcherautonomyandchoreography-usingconwayslawtotacklethecompanyscalingproblem