Run a sprint review that changes the next plan

Review accepted outcomes, incomplete work and new evidence so the next sprint reflects what was actually learned.

Keep delivery acceptance separate from a retrospective about team process.

Request TeamBoostAI access Get the work brief Task table (.csv)

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

A report that leads to a decision

Illustrative manager memo

Illustrative case: date filtering was accepted, a formatting enhancement remains incomplete, and support feedback reveals confusion about timezone labels.

Accepted outcome: Review owner: The review links acceptance evidence for date filtering.
Incomplete work: Task owner: The formatting remainder and its current relevance are summarized without calling it done.
Next planning decision: Product lead: The team chooses a timezone clarification task or documents why it is deferred.

Decision to make: Choose whether timezone clarity should precede finishing optional formatting in the next plan.

Illustrative sprint review memo

Invented planning text. Adapt it to your evidence and confirmed owners.

Accepted: date filtering passed the agreed boundary-date review. Acceptance evidence belongs in the task record.
Not accepted: optional formatting remains unfinished; reconsider its value before carry-over.
New evidence: support reports that timezone wording is unclear.
Decision requested: should timezone clarification precede optional formatting?
Next action: product lead records the priority choice; the sprint coordinator plans only the chosen remainder.

Put the outline to work

Show the accepted outcome with the evidence used for acceptance.
Classify unfinished work before carrying it into another sprint.
Record one next-plan decision for each material new finding.

Questions about this workflow

Is this the same as a retrospective?

No. This review decides what was delivered and what to plan next. A retrospective examines how the team worked.

Do we need to demonstrate every task?

Focus on outcomes and material changes. Link task-level evidence where needed rather than giving every small task equal presentation time.

Does this create tasks in the product?

No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.

From a useful outline to team work

Explore TeamBoostAI for your team

Use the demonstrated outcome and reviewer decision to explain the next status of the corresponding TeamBoostAI work. Confirm the workflows available in your account before adopting this outline.

Request TeamBoostAI access