Technical Excellence, You Need It!
summary
Argues that adopting engineering practices—test-driven development, refactoring, continuous design, clean code and automated testing—turns Scrum’s visibility into solvable problems by shortening feedback cycles and reducing debugging. Shows a 1999 continuous-build pipeline example and notes modern DevOps as XP’s logical conclusion. Gives metrics: ~300,000 certified scrum masters vs ~50,000 certified scrum developers, a team that once “killed 1,293 bugs,” and the testing math: three components of complexity 10 needs 1,000 integration tests vs 30 unit tests. Promotes the TDD microcycle: write a test, watch it fail, make it pass, refactor.
AI-written summary · about
chapters (5)
- 0:00Start
- 5:49extreme Programming explained EMBRACE CHANGE
- 25:18Incremental management and planning, without incremental engineering skill, is a recipe for pain
- 37:52Does your team create unit tests?
- 41:18THE SYSTEMS BIBLE
related talks
32mThinking in tests
17mThe Way of The Software Craftsman
42mAgility in Software Engineering - Concepts and Misconceptions
42mTesting in a Continuous Delivery World
34mWhy continuous testing is essential
26mJust doing scrums won’t win the game
44mStrategy for Acing Continuous Testing in DevOps
49mTest Strategy in a SCRUM Environment