Keynote: Building Bridges with Platforms: The Role of the Platform Engineer
summary
Argues that platform teams must act like hubs connecting dev, ops, security, product and vendors and offers a concrete maturity model with five aspects — investment, adoption, interfaces, operations, measurement — refined by ~50–60 contributors and aiming for L3 “platform as product.” Recommends metrics (DORA, DevX/SPACE, time‑to‑first‑commit, MAU, surveys), cites a real case where a self‑maintained viz tool serves 5–6 teams, and recommends Platform Engineering Maturity Model, GitOps repo as single source of truth, Backstage portal and Argo for visibility.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:36Building Bridges with Platforms
- 8:01Investment and Measurement
- 14:05Adoption Interfaces
- 18:37Operations
- 21:30Maturity Model
- 24:26Call to Action
- 25:31Platform Evaluation Model
related talks
32mPlatform Engineering Is Not About Tech
41mPlatform Engineering for Developers, Architects & the Rest of Us
39mPlatform Engineering as a (Community) Service
01h 02mKeynote: The Socio-technical Elements that Make Good Platforms
33mThe Platform Engineering Journey
46mOrganizational Sustainability with Platform Engineering
43mPlatform as a Product: Mindset, milestones, metrics
44mPlatform Engineering is All About Product