Code And Fix



Code and fix development is not so much a deliberate strategy as an artifact of schedule pressure on software developers. Without much in the way of a design, programmers immediately begin producing code. At some point, testing begins (often late in the development cycle), and the inevitable bugs must then be fixed before the product can be shipped. Detractors of agile programming methodology claim that it is an apologist acceptance of code and fix, though the setting of periodic goals (iterations or sprints) help differentiate it.

Address defects as they are identified
Delay release until identified issues are resolved

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License