Project Scope

Correct Answer: Scope creep

The phenomenon described in the question is called 'Scope creep'. This is the correct answer because:

Scope creep refers to the gradual expansion of a project's scope beyond its original boundaries, often through the addition of small, unplanned features or changes. This perfectly matches the situation described in the question where team members are frequently adding small features that were not originally planned.

Scope creep can lead to project delays, increased costs, and potential failure to meet the original project objectives if not managed properly.

The other options are incorrect:

'Progressive elaboration' is a project management concept where planning is done in stages as more detailed information becomes available. It doesn't specifically refer to uncontrolled additions to the project scope.

'Scope expansion through iterative development' is not a standard project management term. While iterative development can involve scope changes, it typically does so in a planned, controlled manner, unlike the scenario described.

'Requirements evolution' suggests a more formal process of updating project requirements. While this can happen in projects, it doesn't accurately describe the unplanned, gradual expansion mentioned in the question.

Scope creep is a common challenge in project management, and recognizing it is crucial for maintaining project boundaries and ensuring successful project delivery.

Correct Answer: Scope Baseline

The approved version of the scope statement, work breakdown structure (WBS), and its associated WBS dictionary used as a basis for comparison throughout the project is called the **Scope Baseline**. The scope baseline is a component of the project management plan and is crucial for measuring project performance and progress. It allows the project team to compare actual outcomes with planned objectives and manage changes through formal control procedures.

Correct Answer: Evaluate the impact and submit a formal change request

The most appropriate action for the project manager is to evaluate the impact and submit a formal change request. This approach aligns with best project management practices for several reasons: 1. Scope Management: The enhancement is not part of the original scope. Proper scope management requires formal processes to handle changes. 2. Impact Assessment: Evaluating the impact allows the project manager to understand how the change affects time, cost, resources, and quality. 3. Change Control: Submitting a formal change request ensures that the proposed enhancement goes through the established change control process. 4. Stakeholder Approval: This method allows stakeholders to review and approve the change, maintaining transparency and proper governance. 5. Documentation: It provides a documented trail of the decision-making process. The other options are not appropriate because: Implementing the enhancement immediately bypasses proper change control procedures and could lead to scope creep. Consulting with the team alone is insufficient, as it doesn't involve key stakeholders or follow formal processes. Proceeding with the enhancement and informing stakeholders later violates project management principles of transparency and stakeholder engagement. By evaluating the impact and submitting a formal change request, the project manager ensures that the potential enhancement is properly assessed, approved, and integrated into the project in a controlled manner.