Agile, Craftsmanship, DevOps and other monsters [...]
summary
Argues that vague manifestos breed misconceptions and that useful specifics are technical practices, metrics and feedback loops rather than buzzwords. Calls out common anti-patterns: swapping labels for process without changing behavior, renaming ops to DevOps, or treating automation as culture. Recommends concrete techniques — 12 principles awareness, TDD SOLID BDD for code quality, CI tooling like Jenkins and cautious use of Kubernetes — plus measuring changes, baby steps, shared responsibility, continuous improvement; admits failures and emphasizes verifiable results.
AI-written summary · about
chapters (11)
- 0:00Start
- 4:03The Principles behind the Agile Manifesto
- 10:46The Difference between the Working Software and Well-Crafted Software
- 12:29Medicine Analogy
- 13:37Steadily Adding Value
- 13:58First Agile Project
- 15:03Community of Professionals
- 21:09Devops
- 21:58What Is Devops
- 27:19Apply the Change
- 36:01What Is the Next Step in the Evolution
related talks
51mElemental devops
53mDevOps and Agility with Visual Studio, Azure and Scrum
31mAgility, Craftsmanship and Cargo Cult: What's the Link?
38mPolyglot Agile
26mManifesto for a Product Mindset in Agile Development
27mThe curious case of the DevOps engineer and other things ...
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
46mArchitecture & DevOps