What is a common cause of scope creep in IT projects?

Scope creep in IT projects often arises from uncontrolled changes or continuous growth in project scope without adjustments. This phenomenon occurs when additional tasks, features, or requirements are added to the project without proper evaluation or authorization, which can lead to significant deviations from the original objectives and plans. This uncontrolled change can stem from various factors, such as stakeholder requests, evolving client needs, or miscommunication about project requirements.

When the project scope expands without corresponding adjustments to resources, timelines, or budget, it can negatively impact the project by causing delays, overrun costs, and potential quality issues. Managing scope effectively is crucial, requiring clear communication, robust change management processes, and stakeholder buy-in to ensure that any new requirements are assessed and integrated judiciously.

The other choices relate to project management practices that help control scope and can mitigate the risks of scope creep. For instance, strict adherence to the initial project plan and clear timelines are practices that generally support maintaining the defined scope. Frequent team meetings, while facilitating communication, can help ensure everyone is aligned on project objectives, further preventing scope creep.