How can we improve the quality of our code, instead of just finding bugs?

Sorry, flash is not available.

Testing organizations have long been viewed as a place which is responsible for discovering bugs in the developers’ code.  However, it should be the place in an organization that champions practices that result in high quality code – code without bugs in the first place.  Injecting bugs into code, finding and removing them is an inefficient process.  One can consider bugs as coming in two flavors – writing the wrong code and writing the code wrong.  Writing the wrong code means writing code that is not needed by your customers.  To avoid this situation, one needs to build software in small pieces, validating that there is an understanding of what is to be written.  To avoid writing the code wrong, one needs to verify that what was written performs the desired function.

If you are interested in learning how Net Objectives can help you achieve Enterprise Agility through our combination of an assessment, training and coaching, please contact us by clicking here.

For further information on how to address these issues, read The Role of Quality Assurance in Lean-Agile Software Development from our upcoming book Lean-Agile Software Development: Achieving Enterprise Agility.  You can also find several articles and webcasts on this topic on our Lean Resources page.  Note, you will have to register to get at some of this content.