Scope Creep occurs when stakeholders continuously add features, deliverables, or requirements after project initiation, often incrementally and without formal change control. This phenomenon erodes project margins, delays delivery, strains resources, and frequently leads to project failure. A classic example is software development projects where users request 'just one more feature' repeatedly, pushing timelines from six months to two years. Effective scope management requires documented baselines, formal change request processes, impact assessment of proposed changes, and stakeholder education on cost-benefit tradeoffs. Project managers must balance customer satisfaction with disciplined scope governance to prevent uncontrolled expansion.