Scope definition systematically describes the boundaries, inclusions, and exclusions of a project, product, or system. It specifies goals, requirements, and responsibilities and prevents scope creep through explicit delimitations and control points. It serves as a basis for planning, effort estimation, and risk assessment.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Scope definition bounds an initiative by making its objectives, deliverables, included work, exclusions, and assumptions explicit.
Scope definition is a core project and product management practice. PMI’s PMBOK guidance treats scope as a basis for aligning stakeholders on deliverables and managing changes to the agreed boundary.
Start with the intended outcome and relevant stakeholders. Describe deliverables and acceptance criteria, state what is explicitly out of scope, and record assumptions and constraints. A scope is a checkable working agreement: assess new requests against objectives, effort, risk, and their effect on the agreed boundary.
Scope makes included and excluded work visible and prevents silent expansion.
Concrete outcomes and acceptance criteria make the agreed scope verifiable.
New requests are decided by considering value, effort, risk, and effects on scope.
A clear scope definition creates shared expectations and improves prioritisation and change decisions. It can evolve, but decisions must remain documented; scope is more than a task list.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.