Accurate communication is the key to the success of the bug tracking process. This communication takes the form of timely information flow between customers, QA and Development. Reducing the time spent on tasks that communicate bug information saves money.
Here’s a test: Can you list all the issues your software team is working on now? Can you sort them by severity, priority, features affected, and other criteria such as whether the issue is a bug, customer request, or product enhancement? Can you show the histories of all related comments and actions? Can you distribute this information easily to concerned individuals — showing only the information relevant to them?
Elementool, a leading provider of web-based project management tools for developers, including bug, defect, time-tracking and help desk tools, has announced the release of a bug tracking add-in tool for developers using the Visual Studio.NET 2005 platform. It is available free to Elementool’s community of project management solution subscribers.
Being the new person on a bug tracking team can be very intimidating. The other team members are likely very set in the process and know exactly what they are doing. They are used to working as a team and they understand what is expected of them. Being new, though, does not mean that a person can not fit in on the bug tracking team. All a person needs to do is learn a few beginner tips to using bug tracking software.
Drive quality earlier in the development process with continuous testing.
Large development organizations have increasingly been adopting select agile practices to enable faster development, create more reliable software, and reduce costs. Chief among these practices is providing developers early and frequent feedback from users, from other developers, and especially from the programming, build, and test tools. In the latter category, continuous integration and continuous testing are emerging as valuable techniques for identifying errors early so they can be corrected immediately by the developer who made the code changes.