WALKTHROUGHS

Walkthroughs are similar to technical reviews except the producer presents the
material to be reviewed to the review team (via stepping, reading, or 'walking
through' the product). It is the most widely used technique, but the effectiveness is
very sensitive to arguing, selling or attacking of/ about the product. This means that it
is essential that a careful selection of a 'strong' leader to conduct the review is
undertaken.

A walkthrough is a peer review of any stage of the project development product,

where the producer of the material presents it to a group for feedback (both positive
and negative). It is a useful process because, Product defects are detected early in the
development process A group will find defects proportionally faster than a single
person The author is the least likely person to find defects in the product The earlier a
defect is detected, the easier and cheaper it will be to resolve.

Within the project team it helps to:

    Reinforce standards
    Introduce newcomers to techniques
    Ensure comprehension and consistency
    It provides the user with:
        Certification that the project requirements are being met
        An indication of the project progress.

A project is not complete until it has been certified by a walkthrough with the
relevant parties.
 
Attendees' Roles
Who attends a walkthrough will depend on the material being reviewed. The minimal
roles should include:
    • The presenter
    • A moderator
    • A scribe
    • A standards person
    • A user representative
    • Attendees may perform more than one role.

Presenter

Producer of material under review

Before a review:
    • Selects material which can be reviewed in an hour to an hour and a half
    • Selects and contacts walkthrough participants
    • Assigns roles to participants
    • Provides a copy of the material under review at least 24 hours before the review.

During the review:

    • Presents the material under review.

547378226.doc
After the review:
    • Investigates all issues brought up during review
    • Resolves any incidents
    • Communicates resolution to review attendees
    • Files information detailing resolution.

Moderator

During a review:
    • Establishes the ground rules and objectives with attendees
    • Controls the proceedings during a review
    • Opens the floor for questions and discussion
    • Arbitrates discussions

Scribe

During a review:
    • Takes notes of the discussion
    • Reads notes to group at tile end of the review
After a review:
    • Produces a summary of comments made during review
    • Distributes a copy of the summary to review participants an the project manager
    • Files a copy of review proceedings

Standards Person

During a review:
    • Checks for general adherence to standards
    • Checks for maintainability
    • May comment on style
    • Should not be too picky

User Representative

During a review:
    • Ensures the product meets user requirements
    • Gains feedback on progress and quality of the product

All Attendees

Before a review:

    • Examine material distributed by presenter

    • Make a note of at least five positive and five negative points, and any questions

During a review:

    • Do not make any personal comments about the presenter

    • Ask questions
547378226.doc
    • Raise points (both positive and negative)
    • Vote on the acceptability of the project
    • Sign a cover sheet

Walkthroughs are recommended for.

Detailed design Program code Testing documents and methods

547378226.doc