Rethinking the SDLC
summary
Argues the sixty-year SDLC is obsolete and proposes the Revolution model that maps five concentric roles—architecting (largest), automating development, developing, automating deployment, operating (innermost)—and six recurring production concerns as spokes: testability, securability, reliability, observability, flexibility and scalability. Shows concrete examples: a signup form bug fixed post‑release, a DynamoDB comment‑limit incident temporarily padded then remediated with schema/uniqueness work. Claims the model captures multi‑threaded, nonsequential work in cloud‑native systems.
AI-written summary · about
chapters (9)
- 0:00The evolution of DevOps
- 2:46Rethinking the SDLC
- 7:00Questioning long-held models
- 13:50The revolution model
- 18:27Components of the model
- 20:34Defining roles
- 23:23Production considerations
- 29:50The reality of software
- 32:39Applying the model
related talks
28mRevolutionizing Incident Response
48mDesigning a Secure Software Development Lifecycle with DevOps
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
34mYou only have to change one thing to do the DevOps
27mYour Roadmap to Continuous Delivery and Continuous Testing
14mModern Services Demand a DevOps Culture Beyond Apps
32mTales from the DevOps Transformation Trenches
37mIt’s time to rebuild DevOps