There’s a lot of buzz about platform engineering and we want to provide some clarity. Some big questions we’re asking: How do you find signal amid all the noise to pragmatically guide your own platform team? What tools and practices should you prioritize now? Which should you wait for? Should you invest in an internal developer portal? How can you secure leadership support for your initiatives? How do you evaluate teams? Should Kubernetes be on your radar? And how can you do all of this while keeping compliance and security top of mind?
Answering most of these questions is why the CNCF created the Platform Maturity Model. This framework was designed to assess and evolve your platform engineering practices, help you understand your team’s maturity, and guide your thinking to ultimately figure out ‘what’s next?’. We want to bridge the gap on how to take those answers, and apply them to an organization that has security as their number one priority.
In this series, we’re taking a step-by-step look at this model and will discuss:
We’ll weave in stories and examples of successes and pitfalls of platform organizations that were used in the research of creating this model as well as talk about the ways in which each dimension can integrate compliance and security.
Finally, we’ll open up Q&A as an opportunity for attendees to seek practical advice on applying the model within their own organizations.
Lead of CNCF Platform Maturity Model
Senior Product Manager at Ona
This website uses cookies to enhance the user experience. Read our cookie policy for more info.