Agility in Software Engineering - Concepts and Misconceptions
summary
Argues that change, not process or stack, is software’s biggest threat and that disciplined test-driven development (TDD) plus clean code and patterns turns agility from short-lived to sustainable. Shows a greenfield ecommerce built entirely with TDD (commerce) and a three‑year legacy refactor that reaches roughly 100% coverage on nonlegacy code with ~2,800 tests and ~9,000 assertions, CI-run tests run under three minutes on PHP 5.6, enabling predictable two‑week feature delivery and far fewer production bugs. Tools: PHPUnit, CI/CD, ORM bootstrapping, Scrum/Kanban.
AI-written summary · about
chapters (24)
- 0:00Intro
- 2:43A Word about "Agility" ...
- 4:44Short-Lived Agility
- 7:11Your Competition has a Straw ...
- 7:49Typical Coding Workflow
- 10:40The Problem w/ Change
- 12:21Dealing with Change: Goals
- 13:32TDD Workflow
- 15:35TDD vs Typical
- 15:46Agile Stack with TDD
- 16:31Business Value without TDD
- 17:08Beyond TDD
- 20:13Improving Code w/ TDD
- 20:55Challenges with TDD
- 21:12Common Challenges
- 21:29TDD In Action
- 22:24Reviewing TDD Challenges
- 23:21Benefits of TDD
- 27:20Dealing w/Legacy Code: Strategy
- 29:07Refactoring Legacy Code
- 30:33Our Situation
- 33:17Impacts on our Project
- 37:45Impact of TDD on New vs Legacy
- 40:26Review this Talk
