|
Software
Inspection
(2 Day workshop)
About Software Inspection
Inspection
is well known from literature as the most cost-effective way to
improve the quality of any document. Productivity improvements in
the order of magnitude of doubling productivity have
been reported as a direct result of introducing Inspections. Inspection
applies to anything in written form, including engineering drawings,
proposals, contracts and other management documents, as well as
all software related documents as requirements, designs, source
code listings, test-plans, test-scripts and user-documentation.
The
benefits of using Inspection
- Early removal of major defects
- Enabling numeric quality
assessment of any technical
document
- Process improvement
- Staff training on the job
- Gradual productivity improvement
Tom Gilbs version of Inspection
is a substantial extension and improvement over the original inspection
method of Michael Fagan (early 70s). The Inspection Method
is participant friendly and focuses both on identifying defects
AND on improving the engineering process. The inspection method
is suitable for supporting projects and organizations at any of
the five levels of the Software Capability Maturity Model®
(CMM®).
In a Survey by QAI, Peer Reviews/Inspections was the most quoted
Best Practice in high maturity companies.
Aims
of the Inspection Course
This course gives
a thorough overview of the Advanced Software Inspection method,
developed by Tom Gilb, his colleagues and clients in the past 23
years. The material covered teaches to the level of Inspection Team
Leader (Moderator). The aim is to provide you with sufficient information
to enable you to organize and run effective inspections and to implement
the inspection method in your organization.
Structure
and Schedule of the Course
The course is composed
of lectures and exercises (see below). The exercises will be carried
out in small teams. Inspections are carried out on real (non confidential)
documents from the participants. The number of participants is limited
to allow maximum opportunity to ask questions and raise issues.
|
Day
1
|
Day
2
|
Day
3
|
Theory
- Overview of main ideas
- Differences from conventional
inspections
- The planning phase
- Making the master plan
- Entry and exit criteria
- Rules, checklists and
procedures
- kickoff meeting
Exercise
- Produce inspection
master plan
|
- Discussion of Master
Plans
Theory:
Exercise:
- Checking of real documents
Theory:
- Logging
- Avoiding discussion
- Double checking to
find more
major issues
- How to answer questions
Exercise:
- Evaluate and hold Logging
Meeting
- Discussion of decisions
and
experiences
|
Theory:
- Discussion and questions
- The Data Summary form
Exercise:
- Completing the Data
Summary
- Discussion of completed
forms
Theory:
- Process Brainstorming
- Editing
- Edit Checking (Follow-up)
- The Exit process
Exercise:
- Second Inspection cycle,
including process brainstorming
Theory:
- Implementing Inspection
- Creating more inspectable
documentation
- Inspection Economics
- Final Discussion and
Summary
|
Course
Materials
You will receive a binder with
copies of all slides presented by Tom Gilb during the workshop.
Furthermore,you will receive an electronic copy of the world famous
book Software Inspection, written by Tom Gilb and Dorothy
Graham.
|