Software debt exists in different ways. Technical debt is widely known, some other forms are competence debt and quality debt. Software debt can cause product maintenance costs to increase and can depress developers. Several solutions exist to manage software debt.
This article contains the testimonies of several project leaders detailing the process used to achieve a low Coverity Scan defect density.
The new release of Application Lifecycle Management (ALM) tool Tasktop supports an ALM synchronization solution that addresses the visibility and traceability needs of the software development teams. Tasktop team announced the release of Tasktop Sync 1.0 version last month. They also recently released Tasktop Dev 2.1 version which builds on Eclipse Indigo release of Mylyn 3.6.
Team Foundation Server 11 has added many features in the area of Application Lifecycle Management. Some of the highlights include support for code reviews, iterations/sprints, resource allocation, third part testing frameworks, and a much more capable dependency graph.
While, zero defects sounds very good to hear, is it really possible or is it an unachievable goal? Many organizations adopt a 'zero defects methodology'. Does it really mean anything?
In this interview filmed during RubyFringe 2008, Luke Francl explains his position towards testing. While supporting unit testing, he thinks testing is not going to reveal all application defects. Development teams should practice code reviews and usability tests which are likely to discover bugs not visible though other methods.
In this talk from RubyFringe, Luke Francl asks: is developer-driven testing really the best way to find software defects? Or is the emphasis on testing and test coverage barking up the wrong tree?