Review meeting checklist
The goal of the review meeting is to agree on all the requirements in the feature specification so that detailed testing is possible and the development team knows exactly what to deliver. To achieve that, before you let everyone go at the end of the meeting, make sure you have covered all the following points:
- Has the team agreed to all the requirements in the feature specification?
- What questions are outstanding? Who will answer them, and who will check they’ve been answered?
- Have you asked the developers for any code paths they had to add to cover special cases?
- Are there any configuration options that aren’t listed in the specification?
- Has the team agreed to all the cases where you proposed a requirement or behavior? (That includes any requirements you wrote aiming to be precisely wrong rather than vaguely right.)
- Have you prioritized different areas of the specification? Which sections should you test first? ...
