Organizations worldwide are crippled by slow flow, tangled delivery, and teams waiting on other teams. The cost is $billions per year.
📢 I am thrilled to offer an expert checkup on your adoption of Team Topologies directly with me.
The 2x 3-hour online review session covers all aspects of success factors for adoption of Team Topologies based on over 20 years of leadership, consulting, and practitioner insights.
It feels that stream-aligned teams and the fluid teams is a big conflict? And I'm wondering what kind of tradeoffs you've found when working with one or the other?
For example, how do devs build deep domain expertise in fluid teams?
Or if you do TeamToplogies, does it always mean that you might need to rework your architecture so teams can work on value and not just on individual components?
@tcoopman I listened to a podcast on FaST recently and it was super illuminating. FaST is essentially trying to optimize for developer engagement, not continuous care of services.
Published: A Cost-Savings Case for Team Topologies
Recently, I was involved in an unusual technology due diligence. We were asked how the technology organisation can save on costs. After some analysis and many interviews, we suggested a Team Topologies approach to organising teams that came with an impressive estimated cost reduction.
📢 I have decided to make the core operation of Team Topologies non-profit. TT authors Manuel Pais and I are committed to the core mission : "...to make work more humane and more effective for everyone ..." and means I will not be able to profit personally from core TT activities. 💵🚫
More details over the coming weeks as changes happen...
I've got exciting news! 🤩 I’m developing an online course on "Effectively Manage Team Cognitive Load." Targeted at managers, senior managers, executives, agile coaches, and software architects. Or anyone responsible to shape org structures, processes or software.