The Community for Technology Leaders
RSS Icon
Issue No.06 - Nov.-Dec. (2012 vol.29)
pp: 28-33
Raja Bavani , Mindtree
Agile teams create business value by responding to changing business environments and delivering working software at regular intervals. While doing so, they make design tradeoffs to satisfy business needs such as meeting a release schedule. Technical debt is the result of such decisions or tradeoffs. When this happens, agile teams must pay off the accumulated debt by improving designs during subsequent iterations in order to improve maintainability. This must happen in a systematic way so that technical debt does not swell up and damage the project. Accomplishing this is one of the major challenges in distributed agile projects. The scope of technical debt in software projects is spread across all areas including architecture, design, code, and test scripts.
Interviews, Software quality, Software measurements, Software maintenance, Investments, Ethics, technical debt, agile, agile software development, agile testing, distributed agile
Raja Bavani, "Distributed Agile, Agile Testing, and Technical Debt", IEEE Software, vol.29, no. 6, pp. 28-33, Nov.-Dec. 2012, doi:10.1109/MS.2012.155
1. J. Rothman, "Do You Have Feature-itis?," blog, 22 June 2011;
2. J. Highsmith, "The Financial Implications of Technical Debt," blog, 19 Oct. 2010;
3. I. Gat, "Technical Debt," Cutter IT J., vol 23, no. 10, 2010, pp. 3–6.
4. M. Fowler, "Technical Debt Quadrant,"14 Oct. 2009;
34 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool