Developers built a hardcoded 5-dish stub when the canteen CSV slipped, protecting the Sprint Goal.
Late CSV code was merged straight to main without peer review, breaking login for 20 minutes.
Slides show a tidy menu screen, yet real CSV import still fails two Given/When/Then criteria.
Ask: Which problem belongs to the product decision, and which belongs to how the team worked?
Story firstSprint Review is the outward product loop: the Scrum Team and Stakeholders inspect the working Increment and produce an adapted Product Backlog. Sprint Retrospective is the team-only process loop held after the Review: the team inspects workflow facts and agrees one owned process change for the next Sprint.
Restate the Sprint Goal and which items met Definition of Done.
Run working features against Acceptance Criteria; name gaps openly.
Gather real reactions, environment changes, and missing needs.
Product Owner orders what matters next; incomplete work returns.
Slides-only demos or 90-percent-written code fail the Done gate and return to the Product Backlog. Traceable working Increments connect each User Story and Acceptance Criteria to a live demo, supporting Part B (individual mark out of 10: Submission Evidence 4 plus Live Presentation 6) and Part D Sprint Reviews (8 percent each: Group 40 plus Individual 60, plus a 48-hour Retrospective).
What actually happened in code, merges, handoffs and communication?
Which missing habit, rule, or tool bottleneck allowed the failure?
Select one small, testable practice to run during the next Sprint.
Assign who checks it and the exact day to verify whether it worked.
Evidence-to-Action chain: 1 Fact (observable event) leads to 2 Cause (workflow gap), which defines 3 Specific Behaviour (concrete practice), assigned to 4 Action Owner (teammate responsible for execution), and verified at 5 Review Point (exact check day in the next Sprint).
| Item or Input | Observed Friday 16:00 Evidence | Decision |
|---|---|---|
| Pass Story 1: Pick-up slot (5 pts) |
Runs live on test phone; passes all Given/When/Then checks; peer-reviewed. | Done? |
| Stub · 2 fails Story 2: Canteen menu (3 pts) |
Runs only on Day 4 5-dish stub; CSV fails empty-category and sold-out checks. | Done or return? |
| New request Stakeholder feedback |
Canteen manager asks: “Build dark mode theme in Sprint 2.” | Auto-add or order? |
| Incident Friday 15:30 merge |
Unreviewed CSV push broke login on main for 20 minutes. |
Which meeting fixes? |
main.Demo works with the Day 4 5-dish stub, but real CSV import fails two Acceptance Criteria and lacked peer review.
The canteen manager asks for dark mode, while allergen labels and reliable CSV import remain unfinished.
Collect student answers orally first, then reveal the model Sprint Review decisions.
Ask pairs how to turn the Friday 15:30 incident into an owned rule before revealing the 5-link rewrite.
main login for 20 minutes before Review.main.Story 2 runs only on the Day 4 stub (2 CSV checks fail). Stakeholder asks: “Add Order Rating next.”
“Some teammates started coding too late on Thursday.”
Sprint Review inspects working output with Stakeholders to drive Backlog Adaptation.
Incomplete stories return to the Product Backlog; slides never substitute for Definition of Done.
Sprint Retrospective uses Blameless Analysis inside Psychological Safety to assign one change with an Action Owner and Review Point.