D01 R01 02 Tim Urlaub
summary
A platform engineering maturity model is derived from the CNCF model (50 contributors) into an internal Aldi version that adds clear target properties, an office-hours-backed questionnaire for assessments (programmatic feature drift detector proved premature), and extra governance/security context; teams adopt it across the org within a year, documentation-as-code is used, promptfu and a thin MCP wrapper test agent interactions, and the first actionable metric becomes usage counts of complementary modules rather than vague DORA chasing.
AI-written summary · about
chapters (12)
- 0:00Introduction and platform engineering survey
- 1:12Aldi’s digital transformation and cloud platform
- 3:42CNCF platform definition and maturity model
- 5:27Starting point and challenges at Aldi
- 7:10CNCF platform engineering maturity model
- 10:22Building Aldi’s custom maturity model
- 12:30Five phases of maturity model development
- 15:59Reformulating target properties
- 19:52Adding governance and security aspects
- 21:57One year later: model adoption and lessons
- 24:24Future of platform engineering and AI agents
- 26:28Closing remarks and Q&A start
related talks
27mBeyond K8S - Maturing Your Platform Engineering Initiative
29mIaC Next Steps in Platform Engineering
29mPlatform engineering maturity - Your key to competitive differentiation
31mBuilding better platforms: A capability maturity model for infrastructure engineering
33mCloud Foundry Runtime PMC Overview - Dieu Cao, Pivotal
14mPatterns of Adoptions and Depreciation
29mBackstage Revealed: Bright spots and dark corners
29mKeynote: Building Bridges with Platforms: The Role of the Platform Engineer