To print a PDF copy of this article, click here.
It is time that “Technical Debt” assessment and measurement be recognized in defense acquisition and procurement and that its anticipation, avoidance, and elimination be incentivized. Accomplishing this is essential to the sustainability of the defense software industry. Technical Debt enthusiasts are themselves in technical debt regarding its definition. It is time to put a finer edge on this definition and update it. The early, archaic, and somewhat awkward definition, introduced by Ward Cunningham in 1992, is, “Not quite right code which we postpone making right.”