During a requirements walkthrough, the key stakeholders (business stakeholders, project team members, etc.) get together and discuss a requirements document or requirements package step-by-step, in order to finalize the requirements before handing them off to developers. The precise flavor of the walkthrough will vary depending on the audience, the time required for the walkthrough, the volume of requirements, etc. The scheduling of walkthroughs at key points during the project will also vary depending on the nature of the project and the project methodology. However, a formal requirements walkthrough always delivers tremendous value, regardless of the project methodology. Discussing the requirements together helps everyone arrive at a common, consistent understanding, and creates a baseline for evaluating any changes and measuring their impact.