How to fail a software project fast and efficiently?
summary
A catalogue of concrete anti-patterns that reliably wreck projects: strict silos with line managers and no cross-team contact, written-only requirements that mutate through three translations, developers forbidden from production while still owning bug fixes, and no continuous integration combined with six-month releases and deployments handled by different teams. Perverse metrics like demanding 100% test coverage or counting bugs equally and banning retrospectives actively incentivize corner-cutting; the remedy is to invert these practices and adopt CI, automation, small releases and regular feedback.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:10Organizational division
- 4:49Customer interaction gap
- 8:43Management demotivation
- 13:24Tooling and overtime
- 17:21Testing anti-patterns
- 22:21Architectural complications
- 25:13System design pitfalls
- 27:43Specifications failures
- 30:41Version control anti-patterns
- 32:27Non-functional testing misconceptions
- 37:08Agile and XP anti-patterns
- 39:38Sustainable pace sabotage
related talks
13mTen Ways to Doom Your DevSecOps
07mTen Ways to Doom Your DevOps
53m#NoProjects Beyond Projects - Why Projects Are Wrong & What To Do Instead
32mTales from the DevOps Transformation Trenches
41mContinuous delivery in 10 easy mistakes
29m5 ways to screw up your DevOps Transformation
41mEliminate waste..are we doing it all wrong?
32mSoftware Craftsmanship