Prompt detail

Sprint Retrospective Evidence

Collection of objective evidence from a sprint or period to guide retrospective questions.

Prompt 08
Analyzed reports
SprintsPlanning AccuracySprint ProgressThroughputPR Cycle TimeIssue Cycle TimeAging IssuesOpen PRsAging BranchesCode ReviewDaily WIPWork Breakdown
Context to provide

Provide Squad-Name and the sprint or retrospective period. Choose issues or story points and mention any theme the retrospective should investigate without presupposing a cause.

Copyable prompt
2,363 characters
ROLE Data-informed retrospective facilitator using MCP DevStats. OBJECTIVE Prepare evidence for a squad retrospective after a sprint or retro period. Show what the data can support, what remains unknown, and which discussion questions fit the signals. Do not decide causes, blame people, assign actions, or propose experiments. ...

How the analysis runs

The retrospective pack establishes a trustworthy period, assembles a small set of objective delivery signals, and translates tensions into questions the team can explore.

  1. 01Scope and inputsEstablish the retrospective scopeConfirm Squad-Name, sprint or date range, planning unit, and data coverage before selecting evidence for the retrospective conversation.View detailsHide details
    Confirm Squad-Name, sprint or date range, planning unit, and data coverage before selecting evidence for the retrospective conversation.
  2. 02Analysis and evidenceAssemble objective sprint evidenceSelect a compact mix of progress, delivery, cycle time, WIP, and aging signals, avoiding duplicate metrics and unsupported narratives.View detailsHide details
    Select a compact mix of progress, delivery, cycle time, WIP, and aging signals, avoiding duplicate metrics and unsupported narratives.
  3. 03Interpretation limitsTurn tensions into retrospective questionsSeparate facts from interpretations and phrase evidence-linked prompts for reflection without prescribing actions or assigning responsibility.View detailsHide details
    Separate facts from interpretations and phrase evidence-linked prompts for reflection without prescribing actions or assigning responsibility.

Expected Output

Markdown · Illustrative example

Sprint Retrospective Evidence — Squad-Name — Sprint 24

Evidence snapshot

DimensionEvidenceLimit
Completion18 of 23 planned issues2 issues lacked planning metadata
PR flow5.7-day cycle time, up from 4.9Comparison covers one prior sprint
Review queue3 PRs older than 5 daysAge does not identify the reason
Stability1 failed change in 12 deploymentsIncident linkage coverage: 92%

Tensions to discuss

  • Completion coverage was high while PR review time increased by 0.8 day.
  • Deployment volume stayed stable, with one covered failed change.

Retrospective questions

  • Where did review waiting time concentrate during the sprint?
  • What shared conditions applied to the two unplanned issues completed mid-sprint?
  • How did incident-linking coverage affect the stability discussion?

Evidence used

  • Sprint Progress — planned and completed work
  • PR Cycle Time — review flow
  • DORA Metrics — stability context

Stop guessing. Start asking.

Connect DevStats MCP to your AI assistant and turn these prompts into instant answers. Copy a prompt and go.

Get a demoStart free trial