Scope of Project

1
2
Validate Scope

3
4
5
 Inputs
•Project Management Plan

•Project Documents

•Verified Deliverables

•Work Performance Data

6
 Project Management Plan
•Contains the scope management plan, Requirement
Management Plan and the scope baseline

•Specifies how formal acceptance of the completed project

deliverables will be obtained

•The scope baseline includes

•The approved version of a scope statement
•Work breakdown structure (WBS), and
•Its associated WBS dictionary

that can be changed only through formal change control

procedures and is used as a basis for comparison

7
 Project Documents
–Lesson Learned Register – Manage Project Knowledge
output

–Quality Reports – Manage Quality output

–Requirement Documentation – Collect Requirement

output

–Requirement Traceability Matrix - Collect Requirement

output
–Requirement Documentation – Business Requirements,
Stakeholder Requirements, Solution Requirements,
Transition and Readiness Requirements, Project
Requirements, Quality Requirements

8
 Verified Deliverables
Verified deliverables are project deliverables that are completed
and checked for correctness through the Control Quality
process – Control Quality

Work Performance Data

Work performance data can include the degree of compliance
with requirements, number of nonconformities, severity of the
nonconformities, or the number of validation cycles performed
in a period of time – Direct and Manage Project Work

9
 Tools
• Inspection

• Group Decision-Making Techniques

10
 Inspection
•Inspection includes activities such as measuring,
examining, and validating to determine whether work and
deliverables meet requirements and product acceptance criteria

•Inspections are sometimes called reviews, product

reviews, audits, and walkthroughs. In some application areas,
these different terms have unique and specific meanings

Group Decision-Making Techniques

• These techniques are used to reach a conclusion when the
validation is performed by the project team and other
stakeholders

11
 Output
•Accepted Deliverables

• Change Requests

• Work Performance Information

• Project Documents Updates

12
 Accepted Deliverables – Close Project or Phase
•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 the Close Project or
Phase process

Change Requests – Perform Integrated Change Control

•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. The change requests are processed for review
and disposition through the Perform Integrated Change Control
process

13
 Work Performance Information - Monitor and Control Project Work
Work performance information includes information about project
progress, such as which deliverables have started, their progress,
which deliverables have finished, or which have been accepted

Project Documents Updates

•Lesson Learned Register - Manage Project Knowledge output

•Requirement Documentation – Collect Requirements
•Requirement Traceability Matrix – Collect Requirements
•Project documents that may be updated as a result of the
Validate Scope process include any documents that define the
product or report status on product completion

•Verified project documents may require approvals from the

customer or sponsor in the form of signatures or signoffs

14
Control Scope

15
16
17
 Inputs
•Project Management Plan

•Project Documents

•Work Performance Data

•Organizational Process Assets

18
 Project Management Plan
•Scope Baseline

•Performance Measurement Baseline

•Scope Management Plan

•Requirements Management Plan

•Change Management Plan

•Configuration Management Plan

19
 Project Documents
• Lesson learned Register – Manage Project Knowledge output
• Requirements Documentation – Collect Requirements
Requirement Documentation should be
– Unambiguous (measurable and testable)
– Traceable
– Complete
– Consistent, and
– Acceptable to key stakeholders
Well-documented requirements make it easier to detect any
deviation in the scope agreed for the project or product

• Requirements Traceability Matrix – Collect Requirements

The requirements traceability matrix helps to detect the impact
of any change or deviation from the scope baseline on the
project objectives

20
 Work Performance Data - Direct and Manage Project Work

•Work performance data can include

–The number of change requests received
–The number of requests accepted or
–The number of deliverables completed, etc

Organizational Process Assets–department/Organization

•Existing formal and informal scope, control-related

policies, procedures, guidelines

•Monitoring and reporting methods and templates to be

used

21
 Tools

•Trend Analysis

•Variance Analysis

22
 Variance Analysis

•Variance analysis is a technique for determining the cause

and degree of difference between the baseline and actual
performance

•Project performance measurements are used to assess the

magnitude of variation from the original scope baseline

•Important aspects of project scope control include

determining the cause and degree of variance relative to the
scope baseline and deciding whether corrective or preventive
action is required

23
 Output

•Work Performance Information

•Change Requests
•Project Management Plan Updates
• Project Documents Updates

24
 Work Performance Information – Monitor and Control
Project Work

•Work performance information produced includes

correlated and contextualized information on how the project
scope is performing compared to the scope baseline

•It can include the categories of the changes received, the

identified scope variances and their causes, how they impact
schedule or cost, and the forecast of the future scope
performance

•This information provides a foundation for making scope

decisions

25
 Change Requests – Perform Integrated Change
Control
•Analysis of scope performance can result in a change
request to the scope baseline or other components of the
project management plan

•Change requests can include preventive or corrective

actions, defect repairs, or enhancement requests

•Change requests are processed for review and disposition

according to the Perform Integrated Change Control process

26
 Project Management Plan Updates

•Scope Management Plan

•Schedule Management Plan
•Performance Baseline (Scope Baseline + Cost Baseline)
•Scope Baseline Updates
If the approved change requests have an effect on the
project scope, then the scope statement, the WBS, and the
WBS dictionary are revised and reissued to reflect the
approved changes through Perform Integrated Change Control
process

•Other Baseline Updates

If the approved change requests have an effect on the
project besides the project scope, then the corresponding cost
baseline and schedule baselines are revised and reissued to
reflect the approved changes

27
 Project Documents Updates

•Requirements documentation – Collect Requirements

•Requirements traceability matrix – Collect Requirements

•Lesson Learned Register – Manage Project Knowledge

28
 Validate and Control Scope Exercise
1. A work breakdown structure numbering system is used for:
A. Methodically estimate cost of elements work breakdown structure.
B. Explain justification of project.
C. Identification of level at which elements are found.
D. Use in project management software.

2. Which is a vital output of Validate Scope process?

A. Complete scope management plan.
B. Acceptance of project deliverables by customer.
C. Better schedule estimates.
D. Project management information system.

3. Which document contains detailed description of work packages?

A. WBS dictionary.
B. Activity list.
C. Project scope statement.
D. Scope management plan.

29
 Validate and Control Scope Exercise
4. Project scope statement is created in which process group?
A. Initiating
B. Planning
C. Executing
D. Monitoring and controlling

5. As a project becomes more complex, the uncertainty in scope:

A. Remains the same.
B. Decreases.
C. Decreases then increases.
D. Increases.

6. Project manager is asked to add work to project scope. The project manager
remembers that sponsor had previously denied funds for this scope. The project
manager should:
A. Inform sponsor of the request.
B. Evaluate impact of adding the scope.
C. Inform the scope cannot be added.
D. Add the work if there is time is available in project schedule.

30
 Validate and Control Scope Exercise
7. For which purpose can a work breakdown structure be used?
A. Communication with the project team.
B. Explaining calendar dares for each work package.
C. Illustrating the functional managers for each team member
D. Show business need for project.

8. During a meeting, a team member recommends a scope increase that is beyond

the scope of project charter. Project manager explains that the team should focus on
finishing all the work and only the work necessary. This is example of:
A. Change management process.
B. Scope management.
C. Quality analysis.
D. Scope decomposition.

9. Validate Scope process is done?

A. At end of project.
B. At beginning of project.
C. At end of each phase of project.
D. During planning processes.

31
 Validate and Control Scope Exercise
10. Advantage of WBS?
A. Avoids work from slipping through the cracks.
B. Not needed.
C. Required only if project includes contracts.
D. Only method to identify risks.

11. What does NOT explain how far to decompose work?

A. Until it reaches a meaningful conclusion.
B. Until it cannot be sensibly subdivided more.
C. Until it can be done by two persons.
D. Until it can be reasonably estimated.

12. A project manager uses to ensure the team members know what work is
incorporated in their work package.
A. Project scope statement.
B. Product scope.
C. WBS dictionary.
D. Schedule.

32
 Validate and Control Scope Exercise
13. You have held periodic meetings with stakeholders. Project is on schedule and
budget, but stakeholders are not pleased. The MOST significant process that could
have avoided this situation is:
A. Monitor and Control Risks.
B. Control Schedule.
C. Define Scope.
D. Control Cost.

14. Important Collect Requirements process output is?

A. Requirement traceability matrix.
B. Project scope statement.
C. Work breakdown structure.
D. Change request.
15. A recommended scope change has been rejected by integrated change control
board. What should project manager do?
A. Obtain reasons for rejection.
B. Ensure next change is approved.
C. Record the change request and the result.
D. Make approval processes more creative and simple.

33
 Validate and Control Scope Exercise
16. Project requirements have been changing. What is MOST likely to occur?
A. Reduce costs.
B. Ensure that customer approves the project scope.
C. How to determine project completion.
D. Always add resources to project.

17. Validate Scope is related to:

A. Control Quality.
B. Sequence Activities.
C. Perform Quality Assurance.
D. Time management.

18. MOST misinterpretation in project scope statement can be due to?

A. Imprecise language.
B. Inadequate pattern, arrangement, and sequential order.
C. Variations work package sizes.
D. Excessive detail.

34
 Validate and Control Scope Exercise
19. Validate Scope process:
A. Promises that deliverable meets specifications, is an input to project
management plan, and an output of Perform Quality Control.
B. Ensures that deliverable is complete on time, make certain customer
acceptance, and explains that deliverable meets specifications.
C. Ensures customer acceptance, deliverable meets specifications, and provides
a chance for difference of opinion.
D. It is an output of Perform Quality Control, happens before Define Scope, and
ensures customer acceptance.

35