Platform Adoption Strategies: Critical Roles When Investing...
Panelat Platform Engineering Day NA 2024 · on Tuesday, 2024-11-12· at 17:00· Salt Palace | Level 1 | Grand Ballroom G·
summary
Panel argues platforms must cut developer overload and tie directly to business KPIs: link number of new features to ARR, map reduced downtime to customer retention, and reduce customer acquisition cost by speeding feature delivery. Recommended roles are a product manager, SREs, exec sponsor and compliance/risk owners. Use policy as code (examples cited include OPA), build a backlog and visibility into releases, and treat the effort as platform as product. Resources include four reference examples in the Cloud Native Maturity Model.
AI-written summary · about
chapters (8)
- 0:00Platform adoption strategies
- 2:28Why behind platform adoption
- 5:37Business value and benefits
- 9:09Platform project risks
- 12:26Critical roles for success
- 13:49Platform as product
- 17:00Measuring platform success
- 20:54Key takeaways
related talks
22mThe challenges of Platform teams
30mPlatform as a Product
27mConveying the Importance of Platform as a Product in the Cloud Native Ecosystem
43mPlatform as a Product: Mindset, milestones, metrics
26mLessons Learned from 7 years of Running Developer Platforms
35mPanel: Navigating the Path to Platform Engineering...
32mAre You Ready for Platform Adoption, or Are You Setting Yourself up for Failure?
44mPlatform Engineering is All About Product