ISV's

A top priority for software companies is agility - getting products to market faster. So extending and enhancing their Java applications in a fast and flexible way is key. However, the quest for speed cannot compromise quality. Software companies must build in quality as they build software, since the cost of finding and fixing bugs downstream is too high - whether it’s measured in dollars, customer satisfaction or brand impact. And in a world that is increasingly global, they have to ensure that development teams distributed across multiple geographies and time zones are combining quality with agility.

ISV’s are using AgitarOne to identify and correct software defects earlier in the development cycle. AgitarOne’s automated JUnit generation capability gives software development teams a fast "safety net" of unit tests that allows them to detect changes in behavior – so developers can enhance and improve existing Java applications with the confidence that they won’t break anything.

And with AgitarOne’s server-based deployment and reporting, it doesn’t matter where developers are located - global distributed development teams can test even more effectively, and have continuous ongoing visibility into unit-level quality metrics.

Here's what they have to say

"We are a very customer-focused company and have always had a strong commitment to providing the highest quality software to our customers. By leveraging Agitar, we are able to empower our developers to verify the quality of their code before it goes to system integration and QA. Agitar will assist webMethods in ensuring the delivery of high-quality code in hand-offs between engineering and QA, and maintaining the lowest possible number of escaped defects."
Kristin Weller
Executive vice president, Product Development
webMethods, Inc.

A leading software vendor for the telecommunications market recently started a project to rewrite one of their main products. The original application had dominated the market, and it was vital that its dominance be maintained – hence a need to deliver quickly, but with very high quality. The team started using JUnit and the Agile "SCRUM" method, but they soon found that the development team's use of JUnit was sporadic. JUnit tests quickly fell out of date, detrimentally impacting code quality. To resolve these problems, the team started using Agitator and the Management Dashboard. They found the Management Dashboard enabled the developers to have better visibility of the parts of the system which were less tested, helping them to focus their efforts on the riskiest areas of the project. After the end of their second sprint, they found that they were developing more code per sprint than before, and that the number of defects found in QA was down 30%.