Nuances around centralized platform teams


The popularity of centralized platform teams is rising. The latest Puppet State of DevOps Report shows that 63% of the respondents have at least one internal platform. Platforms are vital enablers for a more DevOps way of working as they provide self-service capabilities that development teams can autonomously utilize.

The definition of a “platform” isn’t set in stone though. Many organizations still struggle to put together a platform team that is really able to add value to the development teams. It’s a challenge to build a team with the proper mindset and an organization that supports that team in the right way. The biggest challenges aren’t technical: it’s the organizational and cultural challenges that must be tackled to ensure such a team’s effectiveness.

A certain pragmatism is required when implementing a platform team in an organization. A platform team is known to provide centralized capabilities to its development teams. But as with everything, in practice it’s not so clear what those capabilities are, which capabilities to take ownership of and who makes the decisions. In this post I’ll share some nuances around the practicalities of building centralized platform teams.

Read more on Sander’s blog