A scope is a set of requirements the client agrees to together, such as Phase 1 or a release. Open Product → Requirements and choose Scopes at the top of the page. Set a requirement’s scope in the Scope column of the requirements table.
Create and edit a scope
Choose New scope, name it and optionally describe it. Use the ⋯ menu on a scope to edit it, reopen it or delete it. Deleting a scope keeps its requirements, with no scope. A scope that has been signed off can’t be deleted, so its sign-off history and proof are never lost. Not in scope holds requirements removed from the plan and can’t be deleted. Only delivery scopes can be signed off.
Sign off a scope
When the client agrees to a scope, select it and choose Sign off:
- Add the proof of sign-off. Any file works: the client’s email, a signed document, meeting minutes or a screenshot. At least one file is required.
- Optionally add a note, such as who approved it and where.
- Choose Sign off scope.
Signing off saves the current version of every requirement in the scope. The scope shows Signed off, and its Sign-offs list records who signed it off, when, the note and the proof files.
After sign-off
Requirements can still be edited. A signed-off version is never changed: the next edit starts a new version, so you can always see what was agreed. A signed-off requirement can’t be deleted; move it to Not in scope instead.
| Label | Meaning |
|---|---|
| Signed off | Nothing changed since the last sign-off. |
| Changed since sign-off | A requirement was edited, added or taken out since. |
| Changed | On a requirement in the scope: edited since the sign-off. |
| Added | Put in the scope after the sign-off. |
| Taken out | Signed off with the scope, then moved out of it. |
A requirement’s page shows Signed off or Changed since sign-off next to its status; point at it to see which version was signed off. Its History marks each version that was signed off, with the changes made since.
When the client agrees to the changes, choose Sign off again to record a new sign-off. Each sign-off is kept. Reopen marks a signed-off scope as open for changes without recording a new sign-off.