When implementing software quality metrics, we need to first understand the purpose of the metric, who will be using it, and what decisions will be made based on it. Will the metric illustrate the level of quality in software products, or drive towards a specific objective? QA managers typically want to deliver productivity metrics to management 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. Many organizations are myopic on the objective of velocity. However, velocity means little without quality. You need to define quality for your organization through an agile looking glass with intermediate metrics that lead to both quality and velocity objectives. Join this tutorial to learn how to develop and implement software metrics with actions toward improving both quality and velocity. You will gain insight on how to develop and use metrics within an Agile framework that can be used throughout your development and QA organization. More importantly, you will be able to answer the key questions of your stakeholders and get them to stand up straight and pay attention to software quality.
Module 1: Back to Basics
Module 2: Developing and Connecting the Framework for your Agile Process
Module 3: Applying Metrics within a Agile Quality Model