Software Development Bug Tracking: "Tool Isn't User Friendly" or "User Isn't Process Friendly"

In this article we describe the implementation of software development bug tracking via WebPT/Continuus, in a development organization of about 200 developers, testers and managers of various ranks. We emphasize the interplay of technology, procedures and human nature, and describe our experiences and lessons on how this interplay affects the continuous quality improvement process. Often times, the implementer hears complaints about the tool not being user-friendly. In some cases, the implementer - committed to the tool - will perceive this as a case of a user being not process-friendly. Both responses may have a high emotional content. Who is right?

[1]  Norman E. Fenton,et al.  A Critique of Software Defect Prediction Models , 1999, IEEE Trans. Software Eng..

[2]  Steve McConnell,et al.  Best Practices: Gauging Software Readiness with Defect Tracking , 1997, IEEE Softw..

[3]  Pedro Sousa,et al.  A software defect report and tracking system in an intranet , 1999, Proceedings of the Third European Conference on Software Maintenance and Reengineering (Cat. No. PR00090).

[4]  S. A. Thomas,et al.  Looking for the human factors in software quality management , 1996, Proceedings 1996 International Conference Software Engineering: Education and Practice.

[5]  Miguel Goulão,et al.  Software Defect Report and Tracking System in the Internet: Controlling the Evolution of Legacy Systems , 1999 .

[6]  C. Wohlin,et al.  Understanding software defect detection in the Personal Software Process , 1998, Proceedings Ninth International Symposium on Software Reliability Engineering (Cat. No.98TB100257).