Release Scope
Template Library
Release Scope
Define release type, in-scope items, out-of-scope items, disabled capabilities, limits, known limitations, and scope rationale.
ES-110
Scope
Release Boundary
Template purpose
Use this template to define the boundaries of the proposed release.
Project
<Project name>
Document control
| Field |
Value |
| Artifact owner |
<owner> |
| Primary reviewers |
<reviewers> |
| Status |
<draft / in review / accepted / revised> |
| Last updated |
<YYYY-MM-DD> |
| Related Engineering Stage |
ES-110 — Release Readiness |
| Project workspace target |
docs/project-workspace/release/release_scope.md |
Release type
In scope
| Item |
Source |
Evidence |
<item> |
<requirement / work item / release candidate> |
<evidence> |
Out of scope
| Item |
Reason |
Revisit Condition |
<item> |
<reason> |
<condition> |
Disabled capabilities
| Capability |
Disabled How |
Rationale |
Verification |
<capability> |
<configuration / feature flag / exclusion / access rule> |
<rationale> |
<evidence> |
Limited users / context
| Limit |
Rationale |
Enforcement |
<limit> |
<rationale> |
<how enforced> |
Known limitations
| Limitation |
User / Operational Impact |
Communication |
<limitation> |
<impact> |
<communication> |
Scope rationale
Scope risks
| Risk |
Impact |
Mitigation |
<risk> |
<impact> |
<mitigation> |
Review checklist
- [ ] Release type is clear.
- [ ] In-scope and out-of-scope items are explicit.
- [ ] Disabled capabilities are documented and verified.
- [ ] Limited user/context restrictions are enforceable.
- [ ] Known limitations are visible.
- [ ] Scope rationale supports the release decision.