scope
noun
Scope defines the boundaries of a project or assignment: which goals, activities and results are included and which are excluded.
The team limits the scope of the first version to signing in, ordering and payment.
Scope clarifies which work belongs to a project. In software development, this includes features to build, intended users, systems to integrate and requirements the result must meet. It also includes explicit limits: what is outside the assignment or reserved for a later phase?
From goal to defined work
A goal describes what an organization wants to achieve. Scope translates that goal into a defined assignment. A customer portal's goal might be to let customers handle more tasks themselves. The scope then determines which actions the first version supports, which data is needed and which existing processes remain unchanged.
These boundaries help with estimates and priorities. They do not need to settle every detail in advance, but must be clear enough to explain decisions about schedules, budgets and quality.
When scope changes
New insights or requirements can emerge during a project. The scope can then be adjusted, often called a scope change. The team discusses which work is added or removed and what this means for time, cost, risk and sequencing.
A change is not automatically a problem. Undiscussed expansion does make a project less predictable. Teams therefore record significant changes and reassess which parts contribute most to the goal.