Agile is a frame of mind, a way of thinking.
But just because you are “agile” doesn’t mean there isn’t a need to track or measure effort. If you’re an organization using an Agile development process, your focus is on two key Agile objectives: quality software (free from defects) and velocity (speed). To effectively achieve those goals requires measurement and accountability.
We have the experience and industry know-how to take the guess work out of your Agile development, with Agile metric methodologies that are proven to set you up for success.
The “what’s” and “why’s” of collecting metrics in an Agile environment
When implementing software quality metrics, you need to first understand the purpose of the metric and who will be using it. Will the metric be used for measuring people or assessing the process? Will it illustrate the level of quality in software products, or drive toward a specific objective? QA managers typically want to deliver productivity metrics, while management may want to see metrics that support customer or user satisfaction or cost related (ROI) initiatives.
Metrics that help you figure out how to go faster or figure out where you are slow can support your Agile objectives. But we also offer experience that shows simply going for speed doesn’t result in quality. Going for quality usually results in greater speed.
We advocate the importance of developing a baseline and key indicators in order to adapt metrics to suit the needs of each client. Just as in Agile development, flexibility, communication and intuitiveness are important to success in Agile metrics.
Contact us to learn more about how to apply our expertise in Agile Metrics to your project.