Before they are implemented by the development team, you ask the stakeholders to review and confirm that the project requirements are clear, complete, and accurate. This activity is either performed by having stakeholders individually review and comment on the requirements artifacts and specification documents, or by scheduling and facilitating requirements review meetings with groups of stakeholders. Regardless of the approach, the goal is to validate that your understanding of the requirements are correct and, if not, to update them accordingly.
In this webinar you will learn how to:
• Plan requirements review sessions with end users and stakeholders
• Prepare requirements review packages for delivery to the review team
• Facilitate requirements review sessions or monitor independent reviews
• Collect and selectively incorporate feedback from reviewers
• Secure requirements sign-off or approval from key project stakeholders
Definition of validate & requirements please?
Update:
replace requirements with verify in first post…
Requirements Validation: The activities associated with confirming project requirements with both business and IT stakeholders, including scheduling requirements reviews, preparing review packages, distributing review requests, collecting and incorporating feedback, securing stakeholder approval, and maintaining the review history.
How important is it to get all stakeholders (or at least the customer / users) in a room at the same time for validation — or is it better to use small groups? If small groups, how would you populate the groups (business / technical)?
Requirements reviews can be conducted individually or with end users and stakeholders brought together in a group setting.
Are there sample validation documents you could post? Feedback form, tracking documents, etc.
We have put samples in a white paper available from
http://www.ravenflow.com/rampwhitepaper/paper.php
RT @TopsyRT: Requirements Validation with RAMP http://bit.ly/9wL72Q
Good stuff from RavenFlow #IA #UX #dev #webdev