What does "scope creep" refer to in requirements management?

What does "scope creep" refer to in requirements management?

• A. The process of defining project boundaries
• B. An increase in team size during project execution
• C. The uncontrolled addition of new requirements
• D. A formal change request process

Answer: (C)

In requirements management, "scope creep" specifically refers to the uncontrolled addition of new requirements to a project once it has commenced. This phenomenon occurs when new features, functionalities, or requirements are added without proper evaluation, documentation, or approval processes. The primary issue with scope creep is that it can lead to project delays, increased costs, and can divert resources from the original objectives. Effective requirements management strives to control and minimize scope creep by maintaining a clear scope definition and utilizing formal processes for any changes to requirements. Other concepts mentioned in the context of requirements management have distinct meanings. Defining project boundaries, for example, is essential to prevent scope creep but is more about establishing what is included and excluded in the project rather than the phenomenon itself. Similarly, an increase in team size may affect project dynamics but does not directly relate to the uncontrolled addition of requirements. Lastly, a formal change request process is crucial for managing changes in a structured way, but it is the lack of such a process that typically leads to scope creep.

In requirements management, "scope creep" specifically refers to the uncontrolled addition of new requirements to a project once it has commenced. This phenomenon occurs when new features, functionalities, or requirements are added without proper evaluation, documentation, or approval processes. The primary issue with scope creep is that it can lead to project delays, increased costs, and can divert resources from the original objectives. Effective requirements management strives to control and minimize scope creep by maintaining a clear scope definition and utilizing formal processes for any changes to requirements.

Other concepts mentioned in the context of requirements management have distinct meanings. Defining project boundaries, for example, is essential to prevent scope creep but is more about establishing what is included and excluded in the project rather than the phenomenon itself. Similarly, an increase in team size may affect project dynamics but does not directly relate to the uncontrolled addition of requirements. Lastly, a formal change request process is crucial for managing changes in a structured way, but it is the lack of such a process that typically leads to scope creep.