PK0-003 · Question #173
A project starts out as a small three month project. One month into the project, a stakeholder asks the team for additional functionality, which is estimated to take an additional three weeks. The pro
The correct answer is D. Scope creep. When a project manager implements additional functionality requested by a stakeholder without formal approval, it is known as scope creep.
Question
A project starts out as a small three month project. One month into the project, a stakeholder asks the team for additional functionality, which is estimated to take an additional three weeks. The project manager implements the functionality while waiting for approval. This is known as which of the following?
Options
- AChange request
- BRisk
- CResource constraint
- DScope creep
How the community answered
(51 responses)- A10% (5)
- B6% (3)
- C4% (2)
- D80% (41)
Why each option
When a project manager implements additional functionality requested by a stakeholder without formal approval, it is known as scope creep.
A change request is a formal document used to propose and track changes to the project scope, schedule, or budget, which was not done here prior to implementation.
A risk is an uncertain event or condition that, if it occurs, has a positive or negative effect on a project's objectives, but the implementation of unapproved features is a current issue, not an uncertain future event.
A resource constraint is a limitation on the availability of resources (e.g., people, equipment, materials), which is not the primary issue described in the scenario.
Scope creep refers to the uncontrolled expansion of a project's scope without proper approval or changes to the project plan, often due to informal requests and implementation. In this scenario, the project manager added functionality before approval, directly leading to an unmanaged increase in project work.
Concept tested: Project scope management, scope creep identification
Topics
Community Discussion
No community discussion yet for this question.