Achieving true agility through programmability
summary
Claims that only 4% achieve true agility and that the blocker is architecture not methodology, then lays out a concrete path: treat APIs as foundation, build programmable pipelines (CI/CD, test‑driven deployments), use cloud‑native platforms like Kubernetes and infra‑as‑code tools (Ansible/Puppet/Chef), and shift to a decentralized "cellular enterprise." Measures to track success are flow efficiency plus MTTD/MTTR/MTTRP. Expected results are measurable increases in speed, repeatability and flexibility rather than vague process changes.
AI-written summary · about
chapters (16)
- 0:00Start
- 5:02Agile - Developer Flow
- 9:04The Agile Manifesto
- 9:56Concept started with devices
- 10:16History
- 10:45Programmability in networking
- 11:21Programmability in infrastructure
- 12:17Application Architecture - layered
- 12:57Application Architecture - distributed
- 13:28APIs - Application Programming Interfaces
- 14:11APIs in layered architecture
- 14:24APIs in distributed architecture
- 14:49Pipelines
- 16:14Moving to the Right -
- 16:41Cellular enterprise
- 17:01Measure the success
