Before the show, you shared something I thought was really interesting. You mentioned that historically, when if a developer switched from one team to another, it was as if they had switched companies in terms of tooling and delivery process. So how did things end up like that? And can you share just concretely why that was? It's a combination of things. There were various teams operating on various products in various geographies. Some of them tended to have particular preferences for doing things a certain way. At some point, we decided to consolidate and move to sort of one provider.
Thomas Khalil, Head of Platform and SRE at Trivago, describes how the teams reporting into him are structured, the tactics they’re using to increase awareness of their work, and how they demonstrate their impact.
Discussion points:
- (1:17) The pillars of the Central Platform organization
- (2:18) The organization’s focus on time to market and efficiency
- (3:09) The differences in developer experience between teams
- (4:37) Deciding whether to consolidate services
- (5:57) How platform, developer experience, observability, and SRE teams interact
- (8:40) How these problems were being tackled previously
- (10:09) A failed attempt at rolling out Backstage
- (13:48) How SRE squads are organized
- (15:39) How to motivate platform teams
- (17:23) Demonstrating the impact of the organization
- (18:42) How the data is collected
- (22:32) How they’re increasing awareness for their work
- (23:42) The DevEx pillar
- (25:46) How the DevEx roadshow will work
- (27:56) How DORA metrics fit into their measurement program
Mentions and links:
Connect with Thomas on LinkedIn