Scope creep refers to the uncontrolled expansion of a project's scope after it has been initiated and the initial requirements have been defined. These additional requirements are introduced without a corresponding adjustment in time, budget, or resources. This phenomenon is a common risk in project management, as it can lead to delays, budget overruns, and a potential failure to meet the original project objectives. The key aspect is the uncontrolled nature of these additions, which bypass formal change control processes.

B. Critical path analysis: This is a project scheduling technique used to determine the longest sequence of tasks, which dictates the minimum time to complete the project.

C. Nice to have: This is a prioritization category for requirements, indicating features that are desirable but not essential for the project's success.

D. Cutting corners: This refers to reducing the quality of work or skipping necessary steps to save time or money, which is contrary to adding requirements.

1. Project Management Institute. (2017). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (6th ed.). Section 5.6 Control Scope

p. 168. The guide defines scope creep as "the uncontrolled expansion to product or project scope without adjustments to time

cost

and resources."

2. Kerzner

H. (2017). Project Management: A Systems Approach to Planning

Scheduling

and Controlling (12th ed.). John Wiley & Sons. In Chapter 12

"The Project Office

" Kerzner discusses scope creep as a primary reason for project failure

emphasizing the need for a formal change control system (p. 412).

3. Levy

M.

& Powell

P. (2005). Strategies for Growth in SMEs: The Role of Information and Information Systems. Elsevier Butterworth-Heinemann. In Chapter 7

"IS Project Management

" the authors describe scope creep as a significant challenge where "the boundaries of the project expand" after initiation

often due to user requests for additional functionality (p. 189).