[Mush Honda] Metrics & Reports from Test Teams (QA)

11

Click here to load reader

description

As a part of testing management in a project, test leads are often requested to provide reports and measurements of progress being made by their team. Most of them limit their reports to templates found on the Internet or by simply providing number crunching metrics requested by the project stakeholders. The intent of this presentation is to highlight key goals and reasons and for collecting and reporting information from a tester’s perspective. Attend this presentation to understand the purpose of metrics and how to establish test-centric metrics and to learn a typical metric lifecycle that will enable to you provide insightful progress of your activities in the right context of the project.

Transcript of [Mush Honda] Metrics & Reports from Test Teams (QA)

Page 1: [Mush Honda] Metrics & Reports from Test Teams (QA)

Metrics & Reports from Test Teams (QA)

STC JULY 2014

MUSH HONDA

Page 2: [Mush Honda] Metrics & Reports from Test Teams (QA)

Agenda

• What is a Report?

• What are Metrics?

• Reasons for Collecting Data

• The Metrics Lifecycle

• How do we establish Metrics?

• Examples

2

Page 3: [Mush Honda] Metrics & Reports from Test Teams (QA)

Definition of Report

Wikipedia: A report or account is any informational work (usually of writing, speech, television, or film) made with the specific intention of relaying information or recounting certain events in a widely presentable form.

Verb: 1. give a spoken or written account of something that one has observed, heard, done, or investigated

3

Page 4: [Mush Honda] Metrics & Reports from Test Teams (QA)

Definition of Metrics

(Software) Metrics

Continuous measurement-

based technique

Applied to s/w development

process & products

Supply timely & meaningful Information

To Improve process & products

4

- Paul Goodman (founder member of ESPI)

Page 5: [Mush Honda] Metrics & Reports from Test Teams (QA)

Data Collection & Reporting

• Major reasons:

– Understand Process, Product and Service

– Evaluate Process, Product & Service

– Control Process with Triggers

– Predict future values of Project attributes

• Goals:

– Establish Baseline

– Examine Task & Process Relationships

– Target Improvement efforts

– Improve project estimation

5

Page 6: [Mush Honda] Metrics & Reports from Test Teams (QA)

• Daily

• Weekly

• Monthly

• Quarterly

• By Sprint

• By Release

• By Product Feature / User Story

6

Typical Report Frequency

Reports Help understand:

Schedule Information

Level of Product Quality

Team Challenges & Mitigation Options

Page 7: [Mush Honda] Metrics & Reports from Test Teams (QA)

Metrics Lifecycle

Define & Prioritize

Identify Data to Capture

Communicate to Team(s)

Capture & Verify Data

Analyze & Process Data

Report & Revise Metric

7

Page 8: [Mush Honda] Metrics & Reports from Test Teams (QA)

Establishing Metrics

Standard Metrics

Schedule

Productivity

Product Quality

Semi-Custom Metrics

SDLC based

Scope / Team Size based granularity

Client Success Factors

Client Objectives driven Combination of Process

& Product Quality

8

Page 9: [Mush Honda] Metrics & Reports from Test Teams (QA)

Example: Daily Report

9

Page 10: [Mush Honda] Metrics & Reports from Test Teams (QA)

Example: Monthly Report

10

Page 11: [Mush Honda] Metrics & Reports from Test Teams (QA)

© 2014 HCMC Software Testing Club

Thank You