Stop Writing Defect Records

There is a case for not writing up defects at all. I had a team that adopted continuous integration aggressively. After 6 months of effort, it went from two or three multihour builds a week to multiple builds daily, each build taking less than 30 minutes. (Even 30 minutes may seem long to some, but for many large enterprise code bases, this is relatively fast.) Builds were made continually as new code was checked into the source control system. If the build, the automated unit testing, and the static code analysis were completed without error, the build verification tests ran. Upon successful completion of that testing, the build was deployed to test servers where longer running test suites were started. At the same ...

Get Being Agile: Eleven Breakthrough Techniques to Keep You from “Waterfalling Backward” now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.