What does the term "requirements creep" refer to?

The term "requirements creep" refers to uncontrolled changes or growth in project scope, which is accurately captured by the first choice. This phenomenon typically occurs when new requirements are added after the project has already started, often without proper review or impact assessment. It can lead to confusion, increased costs, and delayed timelines as teams struggle to manage these evolving requirements, which may not have been part of the initial planning or documentation.

Managing requirements creep is a critical aspect of effective systems acquisition and project management. It highlights the importance of having a defined scope and a structured change control process to evaluate and incorporate new requirements systematically. Without this control, projects can veer off course, leading to potential project failure or significant overspending. Understanding this concept is essential for anyone involved in systems acquisition, as it underscores the balance between stakeholder needs and project discipline.