inspection moderator training overviewprocessgroup.com/kickoff/inspection-overview2p3d.pdfthe...

150Version 2.3d© Copyright 1991, 1992 S&P Consultants. All rights reserved.© Copyright 1992-2001 The Process Group. All rights reserved.

T H E

PROCESS

GROUP

Inspection Moderator Training Overview

Copyright IntentThe attendee of this class has permission to make multiple copies of these overview slides forthe purpose of conducting briefing sessions internally within his/her organization.

O 1

The Process GroupP.O. Box 700012

Dallas, TX 75370-0012Tel. 972-418-9541 • Fax. 972-618-6283

E-mail: [email protected]: http://www.processgroup.com


T H E

PROCESS

GROUP

What is an Inspection?

Inspection is an efficient and economical method offinding defects (or potential defects) in products andprocesses early in the development cycle.

Introduction

K 3 O 2


T H E

PROCESS

GROUP

Where Can Inspections Help?

• Software product quality unpredictable• Software products contain problems at release time• Software products late to market• Maintenance costs high• Standards not met• Current walkthroughs or reviews not effective

Introduction

O 3


T H E

PROCESS

GROUP

Inspection as a Feedback Mechanism

ProjectStart

Goal

Ideal path towards goal

Inspect

Inspect

Actual path

Inspect

Introduction

O 4


T H E

PROCESS

GROUP

Inspection CharacteristicsHelps implement Continuous Process Improvement

Introduction

Inspect

Formal /InformalProcess

Product

DefectsAnalysis

LessonsLearned

Improve Process

Rework

Causal

PlanDesignCodeRequirementsTest Plan……..……..

O 5


T H E

PROCESS

GROUP

Who Uses Inspections?Managers

TechnicalWriters

Administrators• Document Changes• Processes

• Plans• Policies• Contracts

• Forecast Documents• Balance Sheets• Procedures

• User Guides• Documents

• Code• Test Procedures• Requirements

Engineers

Introduction

K 5 O 6

• Design• Test Cases


T H E

PROCESS

GROUP

Where Inspections Fit In

Requirements DetailedDesign

Design &Prototype

Code ProductTest

Release &Manufacture

Inspect

Rework Errors

Inspect Inspect Inspect Inspect

Example Development Flow

Introduction

Inspection can also be used to verify that a document (or code) is cleanenough to release to the next stage (via 100% inspection or sampling)

K 4 O 7


T H E

PROCESS

GROUP

Background of This Inspection Process

Michael Fagan & colleaguesIBM

Tom Gilb

The Process Group1991-Today

1972

~1975

Evolving Process

Evolving Process

Introduction

C.L. Jones, IBM,1985-90+

O 8


T H E

PROCESS

GROUP

Reviews, Walkthroughs and Inspections

Startactivity

Endactivity

Developidea

Technical reviewor walkthrough ofideas with peers

Rework Rework Rework

Inspectionof productwith peers

Refine idea

Technical reviewor walkthrough ofideas with peers

Introduction

O 9


T H E

PROCESS

GROUP Are your reviews or walkthroughs like this? .....

ScenariosTake this!

My work is perfect!

O 10


T H E

PROCESS

GROUP

Comparison to WalkthroughsFocused on improving theproduct (code, design, etc.).

Focused on improving theproduct and the process used tocreate it.

TYPICAL WALKTHROUGH INSPECTION

Explains logic & flow of product.Finds defects. Examinesalternative solutions. Forum forlearning.

Finds more defects faster.Only defect explanation allowed.Learning occurs through thedefects identified.

Typically 2-7 people.Moderator usually not trained.

3-5 people with optimum known.Moderator trained.

Quality can be variable. Repeatable. Uses entry and exitcriteria for quality control ofprocess.

Preparation not always done. Preparation required.

Personalities can get in the way. Constructive and egoless.

Not always efficient. Can wastetime.

Very efficient.

Summary

O 11


T H E

PROCESS

GROUP

Process Overview

Process OverviewDocuments and DefectsPlanningKickoff MeetingPreparationInvitation Form

High-level Document

StandardCommon-errorsChecklist

Exit Criteria

Low-level Document

Entry Criteria

Inputs

Invitation to Inspection

Inspection StatisticsSummaryDefect Log

Action Item Log

Final Statistics in Database

Outputs

KickoffMeeting5-45 mins.

Preparation15-120 mins.Rework

Follow-up

Planning

DefectLoggingMeeting<=2 hrs.

CausalAnalysisMeeting

30-90 mins.

O 12


T H E

PROCESS

GROUP

Inspection Participants

1. Moderator• Trained• Peer of inspectors• Does not have to be familiar with work being inspected

2. Inspectors• Trained to inspect via inspection process• Technically familiar with work (or type of work) being inspected• Peers of other inspectors

3. Author orDocumentOwner

• Performs as aninspector

• Performsrework

4. Scribe• Captures final defect list

Process OverviewDocuments and DefectsPlanningKickoff MeetingPreparationInvitation Form

O 13


T H E

PROCESS

GROUP

What Makes Inspections Different?• Meeting efficiency is measured• Time investment and savings are

calculated• Product quality is tracked• Root-cause analysis is performed• Statistics provide the team with

essential information for continuousimprovement

• One-page common-errors checklistsare generated to find errors quickly

• One-page standards are generated todefine best practices

• Moderator certification is implementedfor inspection quality control

• They can be applied at any stage ofthe development cycle to finddefects early

• A trained moderator leads eachmeeting

• No discussion is allowed to debateor solve defects

O 14


T H E

PROCESS

GROUP

Selecting What to Inspect(Rules of thumb)

Inspection Use Guidelines - Selecting What to Inspect - Inspections in a Production Environment

For existing code (or documentation):Select the 20% that is,

• The most critical to the program's operation• The most used section in the product• The most costly if defects were to exist• The most error-prone section• The least well known section• The most frequently changed section

For new code (or documentation):Choose >=20%, <=100%

O 15