Scope

A project’s Scope defines the perimeter of what the project must deliver: included features, expected deliverables, constraints, and boundaries agreed with stakeholders. Everything inside the scope gets done; everything outside does not.

How it works #

Scope is defined in the early project phases through documents like the Statement of Work or Project Charter. Any subsequent change request must go through a formal change management process to evaluate its impact on timeline, budget, and resources.

Why it matters #

Scope creep — the uncontrolled expansion of requirements — is among the leading causes of IT project failure. Every feature added without reassessing timeline and budget erodes available resources. An effective PM knows how to say “yes, and to include this we need to remove that” — not simply “no.”

When to use it #

In every project phase: in planning to define boundaries, during execution to evaluate change requests, in stakeholder negotiations to redirect expectations. Clarity on scope is the foundation of every project decision.