A structured walkthrough, a static testing technique performed in an organized manner between a group of peers to review and discuss the technical aspects of software development process. The main objective in a structured walkthrough is to find defects inorder to improve the quality of the product.
Structured walkthroughs are usually NOT used for technical discussions or to discuss the solutions for the issues found. As explained, the aim is to detect error and not to correct errors. When the walkthrough is finished, the author of the output is responsible for fixing the issues.
Saves time and money as defects are found and rectified very early in the lifecycle.
This provides value-added comments from reviewers with different technical backgrounds and experience.
It notifies the project management team about the progress of the development process.
It creates awareness about different development or maintenance methodologies which can provide a professional growth to participants.
Author - The Author of the document under review.
Presenter - The presenter usually develops the agenda for the walkthrough and presents the output being reviewed.
Moderator - The moderator facilitates the walkthrough session, ensures the walkthrough agenda is followed, and encourages all the reviewers to participate.
Reviewers - The reviewers evaluate the document under test to determine if it is technically accurate.
Scribe - The scribe is the recorder of the structured walkthrough outcomes who records the issues identified and any other technical comments, suggestions, and unresolved questions.