Intrinsic Quality: Why Testing Takes Time

by Jim Highsmith

This is a continuation of previous Advisors on quality, specifically ones on intrinsic quality (see "Investigating Agile: Inside and Out," 19 June 2008 and "Intrinsic Quality?" 3 July 2008). I want to address a very basic question: why is technical (intrinsic) quality so important? In previous Advisors and in the agile literature, the reduction of technical debt has been widely discussed. Agile pundits pose that continuous, comprehensive (every day, every iteration), automated testing is required to be truly agile. In this article, I'd like to address three very important aspects of why the focus on technical debt and testing are so critical: the impact of code quality on testing time, error location dynamics, and error feedback ratio.

Password Protected Cutter Consortium clients, please log in:


This document is available to Cutter Consortium Resource Center clients only. Retrieve password.
If you would like further information about how to become a client, please contact us at +1 781 648 8700 or sales@cutter.com.
Intrinsic Quality: Why Testing Takes TimeThu Aug 21 08:20:13 CDT 2008