Agile Metrics – Not Just Velocity
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, the process, illustrate the level of quality in software products, or drive towards 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.
With agile development methods, we often lose sight that our primary objective is the same: quality. We’ve also added the primary objective of velocity. However, we don’t now how to measure it other than ‘velocity’ itself.
With a agile mindset, define quality for your organization with an agile looking glass. Deliver software quality metrics with actionable objectives toward increasing or improving agile’s two primary objectives, quality and velocity for working software.
You Will Learn:
- Mistakes people make in agile metrics and how to avoid them.
- How to consistently and systematically improve root causes of low velocity.
- How to reduce rework.
- How to analyze your agile process and determine meaningful metrics to present to management.