sprint-review

Sprint delivery is scored against commitments by categorizing stories as shipped QA-passed, incomplete, or not started. The process requires docs/backlog.md and docs/qa-report.md to verify status, using git log for the sprint window to ensure only QA-passed work counts as done.

A blameless retrospective is run by guiding the team through Keep / Change / Action Items discussions. Each resulting action item is assigned a clear owner and tracking artifact, preventing inflated success stories by enforcing QA-pass requirements for completion.

Running an agile sprint review requires docs/backlog.md and docs/qa-report.md as input. The tool uses these files to determine story status and applies git log for the sprint window, enforcing that only QA-passed work counts as done.

Sprint review does not count incomplete work as done without QA verification. It prevents inflated success stories by enforcing that only QA-passed work counts as complete, categorizing all other stories as incomplete or not started.

An auditable sprint summary for stakeholders is generated by analyzing sprint outcomes from backlog and QA reports. The summary includes scored delivery against commitments and documented retrospective action items with clear owners.

A structured sprint review prevents inflated success stories by requiring QA-pass for completion. It scores delivery against commitments and guides a blameless retrospective that produces owned, tracked action items rather than unstructured discussion.