Review kit

Make the scope decision while it still matters.

A tool-neutral agenda for the current sprint, plus a plain-text template your team can edit, copy, download, or print. No app installation, login, or email is needed to download the template.

Download one-page agenda (.pdf)Download decision template (.md)Open app quick start

10-minute native Jira agenda

Turn a changed sprint into a concrete decision.

This meeting works with native Jira alone. It does not assume a complete original baseline snapshot is available.

0:00–1:00 — Set the frame
Name the project and active sprint. State the question: which work changed, what evidence do we have, and what decision is needed now?
1:00–3:00 — Read the current sprint
Open the Scrum board and, where it is available, its Sprint report for the active sprint. Review the work currently shown; this is not proof of a complete original baseline.
3:00–5:00 — Review additions
Review Jira’s added-after-start marker when your board or report provides one. For each item, capture the issue key and the evidence source rather than guessing from the present board alone.
5:00–7:00 — Cross-check removals
When a removal matters to the decision, open the issue history and check the sprint-field change. Record the issue key, source, and time. Native Jira does not promise a full removed-scope snapshot.
7:00–9:00 — Write the decision
List each decision in Confluence, a Jira comment, or the template below. Record who owns the follow-up and the reason for the outcome.
9:00–10:00 — Apply and record
An authorized user moves an agreed item back to the backlog in Jira when that is the decision, then records the reason and timestamp in the team record.

Optional app method

Use Sprint Scope Guard when it is installed.

The app provides a separate current-sprint view: remaining pre-start work, items added after start, and removals made through its own actions. It supports authorized approvals, returns to backlog, scope swaps, and CSV, JSON, or Markdown exports.

Keep the same decision record

Whether the evidence came from the app or native Jira history, record its source and time. The app improves the review of current scope; it does not turn the record into a historical original-commitment snapshot.

Read the app quick start

Editable template

Copy this into your team notes.

The downloadable version is plain Markdown. Copy works locally in your browser; if the browser blocks clipboard access, select the text manually. Use your browser’s print command for a paper-friendly version.

# Sprint scope decision

Date: [YYYY-MM-DD]
Sprint: [Sprint name]
Project: [PROJECT_KEY]
Facilitator: [Name]

## Evidence and scope
- Original baseline: [complete / incomplete / unavailable — do not assume]
- Added after sprint start: [issue keys / app, native Jira history, or unknown / time / none known]
- Removed work: [issue keys / app, native Jira history, or unknown / time / none known]
- Remaining current work: [story points or ticket count / source]

## Decision
| Issue | Decision | Owner | Reason | Evidence source | Follow-up |
| --- | --- | --- | --- | --- | --- |
| [KEY] | Keep / Move to backlog / Swap / Follow up | [Name] | [Brief reason] | App / native history / unknown | [Date or none] |

## Notes
[Risks, dependencies, or agreements raised in the review.]

## Confirmed by
[Names / Jira comment or Confluence link]

Download .md

Use the right place

Native Jira and Sprint Scope Guard work together.

Use native Jira for

Opening the Scrum board, its active Sprint report where available, and issue history.
Backlog ordering, assignment, status transitions, comments, links, and moving agreed work back to the backlog.
Recording a decision in a Jira comment or Confluence after the meeting.

Use Sprint Scope Guard for

Separating remaining pre-start work from additions after the sprint starts.
Recording in-app approvals and removals made through its authorized scope actions.
Current-sprint exports and its three project-key JQL functions.

Before acting: confirm the current Jira project, the issue, the evidence source, and the decision. A scope action changes Jira only when an authorized user chooses it.