Modernization/Transformation
summary
Claims that automating the pipeline — with static and dynamic security testing, automated regression/stress runs and a software factory — drives measurable gains: fewer failures, higher customer satisfaction and faster time to market. Cites metrics to watch like mean time to repair (MTTR), defect density and team velocity, and points to real scale (clients doing hundreds of deployments daily and thousands monthly). Describes autonomous teams, scrum-of-scrums and distributed Agile as the organizational change that makes it work.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:11What is DevSecOps
- 5:05Business drivers for DevSecOps
- 9:20DevSecOps stages and methods
- 11:30DevSecOps culture and practices
- 14:41DevSecOps transformation approach
- 18:19Agile and DevSecOps interlock
- 21:32Autonomous teams in DevSecOps
- 22:37Distributed teams in complex environments
- 23:19Closing remarks
related talks
27mStandard Classification: Automate Security, Don't Tell Your Boss
27mTransforming Traditional Enterprise Software Development Processes
53mTransforming testing methodologies: From manual to robust strategies
28mThe path to agile DevSecOps – a holistic approach of automation, orchestration and correlation
47mWhere the Security Rubber Meets the DevOps Road
34mThe Road More Traveled: Putting Transformation Back on the Rails
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
27mExploring a DevOps Transformation Like a Tester