Which of the following describes the term "scope creep"?

The term "scope creep" is accurately described as the addition of new features or changes in project requirements without proper control and approval. It typically occurs when the project goals expand beyond the initial plan, often leading to increased costs, extended timelines, and potential project failure. This happens when stakeholders or team members continuously add or change features, expecting that the project can absorb these changes without any adjustments to the timeline or budget.

Proper project management practices dictate that changes to the scope should go through a formal change control process. This helps to ensure that all stakeholders are aware of adjustments and the implications they might have on the project. By recognizing scope creep, project managers can take corrective action, such as reinforcing the original project scope or negotiating necessary adjustments with stakeholders, ensuring that the project remains aligned with its intended objectives.

In contrast, concepts like complete documentation of project requirements focus on clarity and agreement at the outset, while reducing project deadlines indicates a shift in timeline pressure rather than scope consideration. Assessing risks related to project size is important for management but does not directly relate to the issue of uncontrolled changes in project requirements, which is the crux of scope creep.