Continuous Improvement and Product Quality
Core Concepts
Continuous improvement (kaizen) is a cornerstone of Agile and Lean. Practices include retrospectives, process tailoring, and technical excellence (XP practices like TDD, pair programming, continuous integration). Product quality is ensured through the definition of done, acceptance criteria, and automated testing. Candidates must understand the difference between quality assurance (preventive) and quality control (detective). Agile emphasizes building quality in rather than inspecting it at the end.
Traps
A common trap is choosing inspection over prevention. For example, if a question asks how to improve quality, the best answer is often to adopt TDD or code reviews, not to add more testers at the end. Another trap is treating retrospectives as a one-time event or skipping them under pressure-they are essential for improvement. Also, beware of answers that sacrifice technical debt for speed without addressing it.
Worked Example
A team has a high defect rate. Instead of adding a testing phase, they implement test-driven development (TDD) and continuous integration, which reduces defects by catching issues early. This demonstrates continuous improvement and building quality in.
Rule of Thumb
Quality is built in, not tested in; use retrospectives to drive continuous improvement.