Tag: Team Topologies
-
The Hidden Costs of Over-Collaboration
In the wake of Agile’s success and the benefits it offers organizations to help them achieve faster delivery, happier customers, and more engaged teams, “Collaboration” has become a buzzword. However, the way I see most teams practice collaboration is not in the sense of collaborating with customers; their focus is on the internal collaboration necessary…
-
Creating Focus Through User Needs Mapping and Core Domain Mapping
A team I’m coaching faced a challenge with the demand for their team’s services far exceeding the amount of work they could deliver. Here’s a look into an ongoing exercise I began with this team to help them get control of their work, and how I combined User Needs Mapping, Core Domain Mapping and Team…
-
Avoiding The Pitfalls of Cross-Functional Super Teams
I’ve previously written about cross-functional teams and what it means for a team to be cross-functional. In that same post, I wrote about Team Topology’s concept of a stream-aligned team. To recap, stream-aligned teams: Suppose autonomous and independent cross-functional teams that own an entire “slice” of a business domain are the ideal way to organize…
-
Revisiting the Guidance on Cross-functional Teams
Like most things with Agile, the idea that teams should be “cross-functional” gets shared almost like an eternal truth, but it’s an old idea that deserves a deeper look. I will explore different perspectives on cross-functional teams and the Three Amigos model, what benefits they’re supposed to provide, and their gaps. I will also review…
Flow Focused 