We Adopted DevOps and Are Cloud Native, Now What?
summary
After becoming cloud native the organization focuses on measurable practices: run security threat modeling workshops (3–4 hours, yearly) and well-architected reviews to surface high/medium risks, which improve risk scores; publish a one‑page digital development handbook of must/should items plus a Backstage tech radar and builders library with reference implementations; form a virtual pool of facilitators so teams self-enable; shift ops from cost to value center and enforce multi‑competence autonomous teams. These changes reduce cognitive overload and make governance practical and actionable.
AI-written summary · about
chapters (9)
- 0:00Introduction and context
- 5:40Becoming the CTO mindset
- 7:47Driving engineering excellence
- 10:38Treating operations as value center
- 13:25Enabling teams with purpose
- 18:00Connecting the dots with assessments
- 21:53Building a digital development handbook
- 23:59Using Backstage for clarity
- 26:23The human side of culture
related talks
22mThe Journey to DevOps: What I Learned
30mMoving beyond DevOps with automated cloud-native platforms
30mCloud & DevOPS culture
39mWhat is next for DevOps?
36mPanel Discussion: Leveraging Cloud Native Technology to Transform Your Enterprise
06mLow Growth DevOps
28mImplementing Critical Cybersecurity Controls in a DevOps Environment
46m360 ° DevSecOps Enterprise Adoption