Project Scope Management

Correct Answer: Detailed work breakdown structure

The correct answer is 'Detailed work breakdown structure'.

A Project Charter is a high-level document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It typically includes:

1. High-level project description and objectives
2. Project manager's authority level and responsibilities
3. Key stakeholders and their roles in the project
4. High-level project scope, timelines, and budget

The Project Charter does not include a detailed work breakdown structure (WBS). The WBS is a more granular document that breaks down the project deliverables into smaller, manageable components. It is typically created later in the planning process, after the Project Charter has been approved.

The other options are incorrect because:

- High-level project description and objectives are essential components of a Project Charter, providing an overview of what the project aims to achieve.
- The project manager's authority level and responsibilities are crucial information in a Project Charter, as it defines the PM's role and decision-making power.
- Identifying key stakeholders and their roles is important for establishing clear lines of communication and responsibility within the project.

These elements provide the foundation for the project and are typically included in a Project Charter, while the detailed work breakdown structure is developed separately as part of the project planning process.

Correct Answer: Explain to the client that any changes must go through the formal change control process.

The project manager should explain to the client that any changes must go through the formal change control process. This ensures that all additional requirements are properly documented, evaluated for their impact on scope, schedule, and budget, and approved before implementation. Following the formal process maintains project control and transparency, and addresses the client's concerns professionally. Adding the additional features without following the change control process can lead to scope creep and jeopardize the project's success. Agreeing to include the features while keeping the project schedule and budget on track is unrealistic and may compromise quality. Advising the client that adding unplanned features is not feasible at this stage dismisses the client's concerns and could harm the client relationship.

Correct Answer: Document the addition and get formal acceptance from the client to update the project scope.

The best practice in project management when an unapproved feature is added and the client is pleased with it is to formally document the addition. The project manager should then get formal acceptance from the client and update the project scope to include this new functionality. This ensures that there is a clear, mutual understanding of what the project now entails, maintains the integrity of the agreed-upon scope, and adjusts resource allocations and timelines as necessary. Removing the feature simply because it was not in the original scope can lead to client dissatisfaction, especially since the client is pleased with the feature. Immediately halting the testing of the shopping cart can unnecessarily delay the project and may not align with the client's interests. Seeking approval from senior management before discussing the scope change with the client can introduce unnecessary internal delays and may not be in accordance with the principle of direct communication with the client.