CPSM CSPM Project Integration & Scope Management 5 — Questions and Answers
Question 1: Which of the following is an example of scope creep?
- The client requests a new feature via a formal change request that is approved
- A developer adds a reporting dashboard that was not in the approved scope without notifying the PM (Correct answer)
- The PM updates the WBS to reflect an approved change
- The team completes a deliverable ahead of schedule
Correct answer: A developer adds a reporting dashboard that was not in the approved scope without notifying the PM
Scope creep is the uncontrolled expansion of project scope without proper authorization or change control.
Question 2: The 100% rule in WBS development means:
- Every work package must be 100% complete before the next begins
- The WBS must capture 100% of the work defined in the project scope (Correct answer)
- All team members must contribute equally to the WBS
- The WBS must have exactly 100 work packages
Correct answer: The WBS must capture 100% of the work defined in the project scope
The 100% rule states the WBS must include all work—and only the work—needed to complete the project scope, with nothing omitted or added.
Question 3: What is the BEST way to prevent scope creep on a large software project?
- Refuse all change requests after project planning
- Establish a robust change control process and clearly baseline the scope (Correct answer)
- Limit stakeholder access to the development team
- Complete the project as fast as possible
Correct answer: Establish a robust change control process and clearly baseline the scope
A formal change control process with a clear scope baseline is the most effective preventive measure against scope creep.
Question 4: A PM is developing the project management plan and realizes the risk management plan conflicts with the procurement management plan. This is BEST resolved by:
- Letting the risk manager and procurement lead resolve it independently
- Performing integrated change control to align the subsidiary plans (Correct answer)
- Ignoring the conflict since subsidiary plans operate independently
- Escalating to the PMO for a decision
Correct answer: Performing integrated change control to align the subsidiary plans
Integrated change control ensures all subsidiary plans remain consistent with each other and the overall project management plan.
Question 5: Which output of Collect Requirements directly feeds into the Define Scope process?
- Scope management plan
- Requirements documentation (Correct answer)
- Project charter
- Stakeholder register
Correct answer: Requirements documentation
Requirements documentation, produced during Collect Requirements, serves as a key input to Define Scope for creating the project scope statement.
Question 6: During scope control, a variance analysis shows the project has delivered 10% more functionality than planned. The PM should:
- Accept the extra functionality as a bonus for the client
- Investigate whether the extra work was authorized and submit corrective actions if not (Correct answer)
- Retroactively add it to the WBS
- Credit the team for over-delivering
Correct answer: Investigate whether the extra work was authorized and submit corrective actions if not
Positive scope variances still require investigation—unauthorized extra functionality consumes budget and may cause issues in later phases.
Question 7: The project charter is formally authorized by:
- The project manager
- An entity external to the project, such as a sponsor or senior management (Correct answer)
- The project team during kickoff
- The PMO after planning is complete
Correct answer: An entity external to the project, such as a sponsor or senior management
The project charter must be authorized by someone with sufficient authority outside the project—typically the project sponsor or senior management.
Which of the following is an example of scope creep?