Code Walkthrough is a form of peer review in which a programmer leads the review process and the other team members ask questions and spot possible errors against development standards and other issues.
The meeting is usually led by the author of the document under review and attended by other members of the team.
Review sessions may be formal or informal.
Before the walkthrough meeting, the preparation by reviewers and then a review report with a list of findings.
The scribe, who is not the author, marks the minutes of meeting and note down all the defects/issues so that it can be tracked to closure.
The main purpose of walkthrough is to enable learning about the content of the document under review to help team members gain an understanding of the content of the document and also to find defects.