#140 – Team Topologies and Dependencies
We think it’s a great ambition to maximize the number of Stream-Aligned Teams. This doesn’t mean that we should totally eliminate every other type of team (which is rarely possible), but that we aim for having more self-sufficient end-to-end value delivery teams, so flow isn’t impeded due to dependencies to other teams.
As described on the previous page, we should remove impediments in the form of dependencies to other teams caused by a lack of competencies. Categorizing the teams according to, e.g., Team Topologies is an excellent beginning, but don’t stop there. While understanding and improving how your different types of teams collaborate across the organization, invest in building the competencies of the Complicated Subsystem Teams and Platform Teams into the Stream-Aligned Teams through Enabler Teams.
Recent Comments