Scope (of a release or product)
- Status
- Review
- Version
- 1.0.1
- Authority
- Not stated
- Applies to
- Core
Definition
Scope is the range of things that can be shaped and designed in a development effort. In practice it is a written statement of what a release includes, what is deferred to a later release and what the product will never do. Only the person who owns the product changes it. The scope of one release is fixed in its release spec, and a change of scope is an owner-level decision.
The first sentence follows the IREB glossary entry for scope of a system development.
Example
“In: capture a note offline; sync when online. Deferred to release 2: photos in notes. Non-goal of the product: shared editing.”
Related
- Scope and minimum viable product — the rules for scope, change requests and the MVP.
- MVP — the first release, defined by what it must learn.
- Vision — where non-goals are first written.
- Release spec — where the scope of one release is fixed.
- Roles and decision rights — why a change of scope is the owner’s.
Sources
- IREB CPRE Glossary — all rights reserved; summarised, not copied. Accessed 2026-11-20.
- Karl Wiegers and Joy Beatty, “Software Requirements”, 3rd edition — all rights reserved; summarised, not copied. Accessed 2026-11-20.