Structured walkthroughs

Structured walkthroughs evolved in the 1970s from Gerry Weinberg's concept of egoless programming

Humans often cannot see errors and deficiencies in their own work, so all work should be checked by someone else

Yourdon's book on structured walkthroughs formalised the procedure, giving advice on:

• the preparatory work required
• participants and their roles
• procedures to follow
• time limits for the review
• essential paperwork for recording the outcome of the review etc

Outcomes

The outcome of a structured walkthrough might be:

• acceptance

or

• provisional acceptance
• a list of errors
• the name of who will check the corrected product

or

• rejection
• a list of errors
• the date and time of the meeting to check the corrected product

Other topics

Comments please to: dwfarthi@glam.ac.uk

© 1999, University of Glamorgan