Scheduling the meeting
You should send around the feature specification a few days before the meeting to give everyone a chance to review it and submit comments in advance. If there is a critical misunderstanding – an area of functionality not covered or described incorrectly – it can be flagged up without wasting people’s time in the meeting. It works well to have both a written and spoken review. The reviewers can take their time and think through their comments, and then you can rapidly discuss them and reach decisions.
You may need to have multiple test plan reviews. If you have planned out the feature before it has been implemented, there should be a review before implementation begins. After it has been implemented, there should also be a review to catch any necessary changes. Often, not all functionality will be delivered in the first version, so this is the chance to describe the exact behavior in this version and what will be added in the future.
...
