Iteration retrospective

Download Markdown ↓

Inputs and purpose

Use this workflow to prepare: Sprint-health analysis and follow-through plan.

Start with: Sprint history, blockers and retrospective records.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

  1. Compare the work selected for the period with what was completed, carried over or added later. Separate scope changes from execution problems.

  2. Use examples to locate recurring delays, unclear ownership and dependencies. Discuss process causes without turning limited observations into judgments about individuals.

  3. Choose a small number of improvements, each with an owner, trial period and observable result. Preserve practices that are working.

  4. Produce a retrospective brief and follow-through list. Check the next review measures outcomes rather than merely counting completed meetings.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Match workload to people, budget and priorities.

Possible success measures: On-time milestones, utilization, budget variance. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions