The last decade has seen massive shifts in software engineering tools, processes, roles, and teams as developers seek to streamline and automate processes to improve the speed of software releases and facilitate continuous delivery. Teams (especially those scaling up) are looking for ways to boost productivity but prevent an influx of burnout, technical debt, and organizational instability. As many organizations shift from monoliths to microservices, teams are looking for ways to maximize efficiency and reduce pain points. One way forward, especially as organizations scale is to change the configuration and function of teams.
Seminal texts such as Matthew Skelton and Manuel Pais’ Team Topologies offer a ‘how to’ in organizational design and team interaction, especially for software development teams. But it’s not only about improving team configuration for optimal value but also the tools used by these teams.
