Team Topologies

Building software at Prima's scale takes quite a few people, certainly more than we can fit inside a single team!

So, how do we choose where to draw the lines in a way that minimizes overhead and enables fast flow of value?

There's no single, immutable, perfect solution to that problem. Over the years, Prima has experimented with multiple approaches. Currently a large influence in how it models its teams is Matthew Skelton's and Manuel Pais' Team Topologies approach.

Some key concepts identified by Team Topologies:

• 6 patterns, such as four team types (stream-aligned, platform, enabling, complicated subsystem) and three collaboration modes (collaboration, X-as-a-service, facilitating).
• 9 principles, for example "Focus on Flow, Not Structure", and "High Trust Is Non-Negotiable".

All in all, and especially considering how relevant this approach is to Prima, it's a good idea to learn a bit about Team Topologies.