What is a Structured Walkthrough?
Structured Walkthroughs
A structured walkthrough is a static testing technique performed in an organized manner between a group of peers to review and discuss the technical aspects of the software development process. 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 errors and not to correct errors.
Objective
The main objective of a structured walkthrough is to find defects to improve the quality of the product. When the walkthrough is finished, the author of the output is responsible for fixing the issues.
Participants
The participants are as follows:
- Author: The Author of the work product or 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 work product 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.
Benefits
Some of the benefits are as follows:
- Cost Savings: Walkthrough saves time and money as defects are found and rectified very early in the lifecycle.
- Feedback: Provides a structured approach to feedback, making it easier to identify and resolve issues. This provides value-added comments from reviewers with different technical backgrounds and experiences.
- Knowledge Sharing: To promote understanding among team members and facilitate collaboration.