Back to the Playbook
BuildProgressBU-06

Run sprint review

Show what actually shipped against the sprint goal, collect stakeholder feedback and turn it into decisions and evidence instead of loose notes.

Product statusAssisted workflowThe review itself is human. Teklens prepares the summary and records the decisions; the Meeting bot for live capture is in beta.

Context in4 required inputsSprint goal and scope · Completed and unfinished stories · Merged changes
TransformationProduct Manager + Product AgentAtlassian · Code Analysis · Local Files
OutcomeSprint review summary with shipped scope, feedback, decisions and follow-ups.Artifact: Jira story

Owner

Product Manager

Human-led

Participants · Agents

EngineerDesignerHead of ProductProduct Agent

Trigger

ScheduledEnd of a sprint.

Required context

JiraSprint goal and scopeJiraCompleted and unfinished storiesCodeMerged changesFilesDemo environment or recording

Optional context

Product BrainSuccess metricsCustomer evidenceCustomer evidenceJiraOpen bugs

Skills

AtlassianCode AnalysisLocal Files

Activity steps

  1. 1Prepare the review summary: goal, shipped, not shipped, and why.
  2. 2Demo the shipped increments.
  3. 3Capture feedback, questions and decisions.
  4. 4Turn accepted feedback into backlog items or decisions with an owner.

Output

Sprint review summary with shipped scope, feedback, decisions and follow-ups.

Artifacts

Updates: Jira story, Decision record

What good looks like

  • Shipped means merged and verified, not «done» in Jira.
  • Feedback is attributed and linked to the story it concerns.
  • Every decision has an owner.
  • Unfinished work has a stated reason and a next step.

Quality gate

The product owner confirms which feedback becomes backlog.

Destination

JiraProduct Brain

Usually next

People and agents work from the same Product Brain. The owner stays accountable. Assigned agents prepare and check. A named person approves at the gate.

Show us exactly how product work happens today.

Thirty minutes with a founder. We compare your process with the Playbook and pick the first Activity to run on your Jira and your repo.