Jump to content

Bug-driven development

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by John.a.honsberger (talk | contribs) at 04:17, 14 April 2018 ("A high number of companies which try to adopt agile development end up doing bug-driven development." is not a supportable claim In fact, articles about agile methods that highly prize testing are found in Wikipedia.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Bug-driven development is software development methodology where incremental development is triggered by raising bugs on existing program or software prototype. Most organizations which follow this philosophy do not adopt it consciously but it comes into practice after degeneration of existing practice or initially adopted development paradigm.

Bug-driven development is a facetious term that describes a state in which high volumes of computer code are written with little regard for unit testing by the programmers. It is a play on the term Test Driven Development in which the focus is on writing tests first and thereby delivering smaller anounts of code with high value and quality.

Extreme programming (XP) is an agile software development methodology which is intended to be the antithesis of Bug-driven development.

See also