| Task: Validate Requirements |
| |
Purpose
| This task is executed to ensure that the requirements that are captured are correct, complete, consistent and represent the
actual needs of the stakeholder(s). This also helps to ensure that requirements are not lost in translation. |
Relationships
| Roles | Primary Performer:
| Additional Performers:
|
| Inputs | Mandatory:
| Optional:
|
| Outputs |
|
Main Description
| Requirements validation is an ongoing process to ensure that stakeholder, solution, and transition requirements align to
the business requirements. It entails checking whether the requirements, as identified, do not contradict the expectations
about the system/solution of various stakeholders, and do not contradict each other. This is performed on all projects
throughout the project Planning phase. When this activity is properly executed, the quality of the requirements can be
improved and costs and risks associated with the project can be controlled. |
Steps
|
Requirement walkthrough
Organize a work group session ensuring that all stakeholders are present.
Define any acronyms at the beginning of the meeting and walk through the entire requirement by vetting with the
Stakeholder(s) that the documented requirement truly satisfies their needs.
Whenever more than one functional group is involved, ensure that any difference in opinion regarding the requirements
that exists among the functional groups has been resolved.
|
Document requested changes
| Capture all the requested changes and update the requirement document to reflect the changes. |
|
Version and Release
Unified Life Cycle (ULC): 5.1, November 3, 2014
Phase Gates: 1.1, May 27, 2014
Process Engineering Process (PEP): 1.1, May 27, 2014
|
|
