Project Management basics - 5.5 Validate Scope Flashcards
Which of the following is true about the Validate Scope process?
a. It is the process of formalizing acceptance of the completed project deliverables.
b. It occurs primarily when revisions or changes are made to project scope.
c. It is primarily concerned with correctness of the deliverables, whereas quality control is primarily concerned with acceptance of the deliverables and meeting the quality requirements.
d. It is not necessary if the project completes on time and within budget.
a. It is the process of formalizing acceptance of the completed project deliverables.
Validate Scope is the process of formalizing acceptance of the completed project deliverables. The key benefit of this process is that it brings objectivity to the acceptance process and increases the probability of final product, service, or result acceptance by validating each deliverable. This process is performed periodically throughout the project as needed.
See Section 5.5 Validate Scope
Which of the following is a tool or technique for Validate Scope process?
a. Expert judgment
b. Inspection
c. Product analysis
d. Variance analysis
b. Inspection
Tools & Techniques;
- Inspection
- and decision making (Voting).
See Figure 5-15 on Validate Scope: Inputs, Tools & Techniques.
Which of the following are deliverables that are completed and checked for correctness through the Control Quality process?
a. Verified deliverables
b. Accepted deliverables
c. Endorsed deliverables
d. Authorized deliverables
a. Verified deliverables
Verified deliverables are project deliverables that are completed and checked for correctness through the Control Quality process.
See Section 5.5.1.3 Verified Deliverables
Which of the following are deliverables that are formally signed off and approved by the authorized stakeholder?
a. Accepted deliverables
b. Endorsed deliverables
c. Verified deliverables
d. Authorized deliverables
a. Accepted deliverables
Deliverables that meet the acceptance criteria are formally signed off and approved by the customer or sponsor. Formal documentation received from the customer or sponsor acknowledging formal stakeholder acceptance of the project´s deliverables is forwarded to Close Project or Phase process (Section 4.7). See Section 5.5.3.1 Accepted Deliverables
Which of the following is an output for the Validate Scope process?
a. Accepted deliverables
b. Validated deliverables
c. Approved change requests
d. Scope baseline
a. Accepted deliverables
Outputs:
- Accepted deliverables;
- work performance information;
- change requests;
- And project document updates ( lessons learned, register, Requirements documentation, Requirements traceability matrix).
See Figure 5-15 on Validate Scope: Inputs, Tools & Techniques, and Outputs in traceability matrix).
Which project assets are considered appropriate input(s) for the Validate Scope process?
- Project documents ( Lessons Learned Register, Quality Reports, Requirement Documentation, Requirements Traceability Matrix)
- Verified deliverables.
- Project Management Plan ( Scope Management Plan, Requirements Management Plan, Scope Baseline).
- Work performance data.
Which project assets are considered appropriate output(s) for the Validate Scope process?
- Accepted deliverables
- Project Documents Updates ( Lessons Learned Register, Requirement Documentation, Requirements Traceability Matrix).
- Work performance information.
Change requests
Which of the following is a tool or technique for the Validate Scope Process?
a. Inspection
b. Product analysis
c. Expert judgment
d. Variance analysis
a. Inspection
Tools & Techniques: Inspection and decision making (Voting)
See Figure 5-15 on Validate Scope: Inputs, Tools & Techniques, and Outputs.
Which of the following is an input for the Validate Scope process?
a. Project charter
b. Verified deliverables
c. Quality metrics
d. Stakeholder register
b. Verified deliverables
Inputs:
- Project management plan (scope management plan, requirements management plan, scope baseline);
- Project documents ( lessons learned register, quality reports, requirements documentation, requirements traceability matrix);
- Verified deliverables; and work performance data.
See Figure 5-15 on Validate Scope: Inputs, Tools & Techniques, and Outputs
Which of the following are the basis for performing the validation and for final acceptance of the deliverables by the customer or sponsor?
a. Accepted deliverables as well as the requirements management plan.
b. Requirements documentation or the scope baseline as well as work performance data from other processes
c. Acceptance criteria that has been formally signed off and approved by the customer or sponsor
d. Inspection of accepted deliverables against requirements documentation
b. Requirements documentation or the scope baseline as well as work performance data from other processes?
In the Validate Scope process, the outputs obtained as a result of the Planning processes in the Project Scope Management Knowledge Area, such as the requirements documentation or the scope baseline, as well as the work performance data obtained from the Execution processes in other Knowledge Areas, are the basis for performing the validation and for final acceptance.
See Section 5.5 Validate Scope
The completed deliverables that have not been formally accepted are documented, along with the reasons for non-acceptance of those deliverables. Those deliverables may require what?
a. Change request for defect repair
b. Update to lessons learned register
c. Document in the issue log to be monitored
d. Update to requirements documentation.
a. Change request for defect repair
The completed deliverables that have not been formally accepted are documented, along with the reasons for non-acceptance of those deliverables. Those deliverables may require a change request for defect repair.
See Section 5.5.3.3 Change Request
