Skip to Main Content
Skip to Navigation
Project Management Orientation

Process of Validating Requirements

If you do not validate the requirements now, it’s likely that sometime during the project a stakeholder will come back and say "I didn’t agree to that" and throw the project off-course.

To validate the requirements you have gathered and documented, distribute your findings to the sponsor, stakeholders, and members of the project team to review.  As with any review cycle, be sure to tell reviewers when you want their comments returned.

After you receive all comments:
  1. Decide what to do about them.  You will decide to implement some and not implement others.
  2. Tell your reviewers your decision about each comment that they made.
  3. Redistribute your requirements document for a second review, and ask the reviewers to approve the document.
  4. Continue this process until you get everyone to approve the requirements document.  A reviewer's approval means that he or she agrees about what the project will deliver.

This approved document is the requirements baseline.

1: Getting Started
2: Define the Project Team
3: Team Management
4: Identify and Validate Requirements
5: Create Decomposition Structures
6: Risk Management
7: Project Estimates
8: Project Schedules
9: Change Management
10: Project Control and Execution
Defining the Project
11: Project Management Review
12: Project Closeout
13: Project Management Tool Suite
14: Self-Assessment and Final Exam
Fast Points
Concepts
Seven Keys
Case Study
WWPMM
Mentor
Check Point
Previous button
Next button
Print button
Help button
Glossary button
Exit course button