Chapter 5 - Scope Mgmt

Question 1

What are the inputs to control scope?

Answer 1

Project management plan
Project documents (lessons learned register, requirements documentation, requirements traceability matrix)
Work performance data
OPA

Question 2

What is the scope baseline?

Answer 2

The approved version of a scope statement, work breakdown structure (WBS) and its associated WBS dictionary

Question 3

What is the WBS dictionary?

Answer 3

A document that provides detailed deliverable, activity, and scheduling information about each component in the work breakdown structure

Question 4

What is the requirements management plan?

Answer 4

Describes how requirements will be analysed, documented and managed. Part of the project mgmt plan. Output of plan scope mgmt

Question 5

What is the configuration management plan?

Answer 5

Describes how to identify and account for project artefacts under configuration control, and how to report and record changes to them. Part of project mgmt plan. Output of develop project management plan.

Cf change management plan

Question 6

What is a claim (in the context of Control Procurements)?

Answer 6

A contested change; where the buyer and seller cannot reach an agreement on compensation for the change or cannot agree that a change has occurred

Can become a dispute and an appeal

Question 7

What is the project scope?

Answer 7

The project scope is the work the project team will do to deliver the product scope, including planning, coordination etc. These efforts are part of the scope baseline

Question 8

What is an essential component of requirements documentation?

Answer 8

Acceptance criteria

Other things: link to project objectives (in requirements traceability matrix), source, status, owner (similar to risk owner)

Question 9

What is product analysis?

Answer 9

Analysis of the objectives and description of the product as stated by the sponsor to define tangible deliverables. Helps to create the scope statement

Question 10

What is in the project scope statement?

Answer 10

• product scope
• project scope
• deliverables of the project
• acceptance criteria
• what is not part of the project
• assumptions and constraints

Question 11

What are the levels of the WBS?

Answer 11

Typically:
1 (top). Project name
2. Development life cycle
3. High level deliverables
...
N (lowest). Work package

Note: each level is a deliverable (thus, a noun), not an activity. Activities are defined in Define activities process

Question 12

How do you know you have reached the work package level in the WBS?

Answer 12

• can be estimated
• can be completed quickly (small 4-40 hrs, large projects 300)
• can be completed without interruption of need of more information
• may be outsourced

Question 13

What is a control account?

Answer 13

A tool that allows the project manager to collect and analyse work performance data regarding costs, schedule and scope.

• can occur at higher levels in WBS
• each work package can only be assigned to one control account

Aka planning package

Question 14

What are the inputs for the validate scope process?

Answer 14

1. Verified deliverables (from Control Quality)
2. Scope baseline
3. Requirements management plan and requirements traceability matrix
4. Requirements documentation
5. Quality reports
6. Lessons learned
7. Scope management plan
8. Work performance data

Question 15

What is the requirements traceability matrix and what process produces it?

Answer 15

A grid that links product requirements from their origin to the deliverables that satisfy them. Output of the collect requirements process