When does scope creep typically occur in a project?

Scope creep typically occurs when project work begins because this is often the time when stakeholders start to request changes or additional features that were not included in the original project plan. Once a project is in motion, team members might find that they need to make adjustments based on new insights, changing requirements, or stakeholder feedback. This can lead to the addition of tasks or deliverables without proper evaluation of the impact on time, costs, or resources.

During the planning phase and project initiation, the project's scope is being defined and documented, which helps set clear boundaries. While it's possible for discussions around the scope to occur during these stages, the actual onset of scope creep generally happens when execution begins, as that is when the project team is actively working on deliverables and stakeholders become more engaged with the process. Before project launch, the scope should be finalized, so changes at that stage are typically managed through a structured process rather than leading to scope creep.