Description
Many organizations experience problems with software delivery because they have an unhelpful model of what software development is really about. An obsession with “feature delivery” ignores human-related and team-related dynamics inherent in modern software development, leading to disengagement from staff, especially when there are high cognitive loads.
The Team Topologies pattern enables teams to address all these points by establishing a team-first approach to software delivery based on four fundamental team types, three patterns of interaction between teams, and ways of turning difficulties in delivery into signals for the self-steering organization.
Output Goal
- Re-structure organization to favor team-first thinking
- Setup enabling team to assist stream-align teams
- Create measurement metrics to evaluate collaboration effectiveness based on cognitive load, domain complexity, boundary size,…
Timeline
- (2022-08-28) - (Thanh) definition of Cognitive Load and why it’s relevant to engineering delivery - https://brain.d.foundation/Engineering/Management/Cognitive+load
- (2022-08-19) - (Thanh) definition of stream-aligned team - https://brain.d.foundation/Engineering/Management/Stream-aligned+team
- (2022-08-15) - (Thanh) definition of enabling team - https://github.com/dwarvesf/brain/pull/67
- (2022-08-14) - [Assess] (Thanh) start Discord thread
- Submit Team Topologies note - https://github.com/dwarvesf/brain/pull/65
- Submit Team First Thinking note - https://github.com/dwarvesf/brain/pull/66