Scope Mgmt Processes

Question 1

Collect Requirements

Answer 1

(5.1 PLAN) Defining and documenting stakeholders’ needs to meet the project objectives.

What do the stakeholders require to meet the project objectives? In this process you take the high-level requirements from the project charter and produce a detailed list of requirements.

Question 2

Define Scope

Answer 2

(5.2 PLAN) Developing a detailed description of the project and product.

The purpose of this process is to create a project scope statement, which puts everybody on the “same page”. This project scope statement creates a detailed description of the deliverables of the project and the work required to create them. This is where the rubber meets the road, so to speak.

Question 3

Create WBS

Answer 3

(5.3 PLAN) Subdivides project deliverables and project work into smaller, more manageable components.

The previous process of “Define Scope” gives the final address of the destination, but the “Create WBS” breaks things down like the GPS system in your car which can give you specific instructions like “turn left here”, “go straight 2.0 miles”, etc. that, if followed, will get you to your destination.

Question 4

Verify Scope

Answer 4

(5.4 M&C) Formalizing acceptance of the project deliverables with the customer.

Verifying the scope means taking a deliverable and asking the customer and/or sponsor to review to make sure it conforms to the customer’s expectations of the scope.

Question 5

Control Scope

Answer 5

(5.5 M&C) Monitoring status of the project and product scope and managing changes to the scope baseline.

Control scope means to monitor the status of the project and product scope to see whether the project is proceeding according to plan. What happens if the scope is deviating from what was in the plan? Then changes are suggested to either get it back to the original plan or to adjust the plan accordingly.