Project Management Project Scope and WBS Questions and Answers — Questions and Answers
Question 1: A project manager is overseeing the development of a new software application. During a team meeting, a developer suggests adding a new feature that was not in the original requirements, believing it will significantly impress the client. This addition is done without any formal change request or impact analysis on the schedule and budget. This is an example of:
- Scope creep
- Gold plating (Correct answer)
- Value engineering
- Contingency planning
Correct answer: Gold plating
Gold plating is the practice of adding extra features or functions to a project's scope that were not originally requested by the client, often without their approval. [10, 19] This is distinct from scope creep, which is typically driven by uncontrolled changes requested by the client or stakeholders. [3, 16]
Question 2: Which of the following BEST describes the purpose of the Work Breakdown Structure (WBS) Dictionary?
- To provide a graphical, hierarchical view of the project deliverables.
- To authorize the project and provide the project manager with the authority to apply organizational resources.
- To provide detailed information about each component in the WBS, such as work package descriptions, acceptance criteria, and required resources. (Correct answer)
- To track the status of project deliverables and manage changes to the scope baseline.
Correct answer: To provide detailed information about each component in the WBS, such as work package descriptions, acceptance criteria, and required resources.
The WBS Dictionary is a document that provides detailed information for each component in the WBS. [6, 11] This includes a description of the work, deliverables, acceptance criteria, milestones, and resource requirements, adding necessary context to the visual WBS chart. [15, 17]
Question 3: A project team has just completed a major deliverable. The project manager now needs to obtain formal acceptance of this deliverable from the customer. Which process should the project manager initiate?
- Control Quality
- Perform Integrated Change Control
- Control Scope
- Validate Scope (Correct answer)
Correct answer: Validate Scope
The Validate Scope process is the process of formalizing acceptance of the completed project deliverables. [1] This process involves meeting with the customer or stakeholder to gain their formal sign-off, confirming that the deliverable meets their needs and acceptance criteria. [12, 21] Control Quality, on the other hand, focuses on verifying that the deliverable meets the specified quality standards, and it is typically performed before Validate Scope.
Question 4: The '100% Rule' is a fundamental principle in creating a Work Breakdown Structure (WBS). What does this rule signify?
- All work packages must be 100% complete before the project can be considered finished.
- The project team must be 100% confident in the cost and schedule estimates for each work package.
- The total of the work at the lower levels must roll up to 100% of the work represented by the parent level, and the entire WBS must capture 100% of the project's scope. (Correct answer)
- At least 100 stakeholders must approve the WBS before the project planning can proceed.
Correct answer: The total of the work at the lower levels must roll up to 100% of the work represented by the parent level, and the entire WBS must capture 100% of the project's scope.
The 100% rule states that the WBS must include 100% of the work defined by the project scope and capture all deliverables – internal, external, and interim – in terms of the work to be completed, including project management. [14] The sum of the work at the 'child' level must equal 100% of the work represented by the 'parent'. [14]
Question 5: What is the primary distinction between the Project Charter and the Project Scope Statement?
- The Project Charter is created during the planning phase, while the Project Scope Statement is created during the initiation phase.
- The Project Charter provides a detailed description of the project deliverables, while the Project Scope Statement authorizes the project.
- The Project Charter is a high-level document that authorizes the project's existence, while the Project Scope Statement provides a detailed description of the project's scope, deliverables, and boundaries. (Correct answer)
- The Project Scope Statement is created by the project sponsor, while the Project Charter is created by the project manager and the team.
Correct answer: The Project Charter is a high-level document that authorizes the project's existence, while the Project Scope Statement provides a detailed description of the project's scope, deliverables, and boundaries.
The Project Charter is developed during the project initiation phase to formally authorize the project and provide the project manager with authority. [9, 23] It contains high-level information. The Project Scope Statement is created later, during the planning phase, and it describes in detail the project's deliverables and the work required to create them. [22, 29]
Question 6: During the execution of a construction project, the client continuously requests small changes to the building layout that were not part of the original approved plan. The project manager fails to implement a formal change control process, leading to budget overruns and schedule delays. This situation is a classic example of:
- Risk mitigation
- Resource leveling
- Gold plating
- Scope creep (Correct answer)
Correct answer: Scope creep
Scope creep refers to the uncontrolled expansion or growth of a project's scope without adjustments to time, cost, or resources. [3, 10] It often occurs when changes are not properly managed through a formal change control process. [16]
