Half-Day Tutorial: Agile Metrics – It’s Not About Velocity

When implementing software quality metrics, we 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. Many organizations are myopic on the primary objective of velocity. However, velocity means little without quality. Define quality for your organization with an agile looking glass with intermediate metrics that lead to both quality and velocity. Learn to develop and implement software quality metrics with actions toward improving on these two primary objectives.

Learning Objectives:

  • How to connect your metrics with agile related objectives, to ensure your agile process is on track
  • How to develop a measurement framework that measures not only typical test results such as defects, but processes and functions and their alignment with your agile objectives
  • How to include measurements, metrics, objectives, questions and answers (for your stakeholders) to see if they really want to be agile or are just talking
  • How to use metrics to not only evaluate, but also predict what could go wrong in your agile process

HALF-DAY TUTORIAL MEASUREMENT
Location: Date: April 19, 2016 Time: 8:30 am - 12:00 pm hs_Phil-Lew Philip Lew hs__Stephen_Gohres Steve Gohres