CHC5056 Innovative Product Development · Semester 1, Week 8

Sprint Review
and Sprint Retrospective

How do we inspect what we built and improve how we work without turning reviews into slides or blame?
Week 7 planned Sprint 1 and introduced daily steering.At Sprint end, teams must judge what counts as Done and agree one concrete way to work better.
Session45 minutes
Running caseCanteen Pre-order App (fictional)
Followed byWeek 9: Design and Confirmation
Learning outcomes

Four Things You Will Be Able to Do

01
Distinguish Sprint Review and Sprint Retrospective by purpose, participants, evidence and output.
Exit check and
Sprint Reviews (Part D)
02
Evaluate a Sprint Increment against Acceptance Criteria and Definition of Done to make a sign-off and Product Backlog adaptation decision with Stakeholders.
Part B: Group Presentation
and Sprint Reviews (Part D)
03
Analyse a delivery problem using Blameless Analysis inside a psychologically safe Sprint Retrospective and write one testable improvement with an Action Owner and Review Point.
Part D 48-hour
Sprint Retrospective
04
Record observable Review feedback and Retrospective evidence rather than unsupported opinion or personal blame.
Part B Submission Evidence
and Part D Review record
Learning outcomes · 0 to 1 min
Opening and retrieval · Fictional teaching case

Friday 16:00: Polished Slides, Broken Main

Day 4 (Week 7)

Menu stub kept flow alive

Developers built a hardcoded 5-dish stub when the canteen CSV slipped, protecting the Sprint Goal.

Friday 15:30

Unreviewed push broke main

Late CSV code was merged straight to main without peer review, breaking login for 20 minutes.

Friday 16:00

Slick slides, two failed checks

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 first
Fictional teaching case
Opening and retrieval · 1 to 5 min
Two conversations · Product vs process

One Sprint End, Two Different Conversations

Sprint Review focuses on product adaptation; Sprint Retrospective focuses on team process improvement Left card shows Sprint Review: plain anchor is checking working output with outsiders to decide what to build next, taking the working Increment and Stakeholders as inputs and producing an adapted Product Backlog. Right card shows Sprint Retrospective: plain anchor is looking inward at team workflow to pick one concrete fix, taking workflow facts inside the Scrum Team and producing one owned process change. LOOP 01 · PRODUCT (OUTWARD) Sprint Review Check the working product with outsiders, then decide what to build next. INPUTS & PEOPLE Increment + Stakeholders DECISION OUTPUT Adapted Product Backlog HAPPENS FIRST AT SPRINT END LOOP 02 · PROCESS (TEAM-ONLY) Sprint Retrospective Team looks inward at its workflow, then picks one fix for the next Sprint. INPUTS & PEOPLE Team only + Workflow facts DECISION OUTPUT 1 Owned Process Change CLOSES THE SPRINT AFTER REVIEW Rule: Never mix product sign-off with team blame in one meeting.
Text version of the diagram

Sprint 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.

Sprint Review · 5 to 15 min
Sprint Review · Working session · Fictional teaching case

Inside a Sprint Review: Inspect and Adapt

New term · Who joins from outside?
Stakeholder
Anyone outside the Scrum Team who uses, runs, or funds the product (for example, campus students and the canteen manager).
New term · What changes?
Backlog Adaptation
Updating, reordering, or returning unfinished items in the Product Backlog based on what the live demo revealed.
Step 01

Goal & Scope

Restate the Sprint Goal and which items met Definition of Done.

Team sets context
Step 02

Live Demo

Run working features against Acceptance Criteria; name gaps openly.

Developers show output
Step 03

Feedback

Gather real reactions, environment changes, and missing needs.

Stakeholders respond
Step 04

Adapt Backlog

Product Owner orders what matters next; incomplete work returns.

Product Owner decides
Fictional teaching case
Sprint Review · 5 to 15 min
Evidence standard · Part B and Part D

Working Evidence vs Slides-Only Reporting

Comparison between slides-only demonstration and traceable working Increment evidence for Part B and Part D Top path shows a rejected slides-only demo where 90 percent finished code fails the Done gate and returns to the Product Backlog. Bottom path shows User Story checked against Acceptance Criteria and Definition of Done in a live demo, feeding Part B individual marking out of 10 and Part D Sprint Reviews (8 percent each, Group 40 plus Individual 60). REJECTED PATTERN · SLIDES-ONLY OR "ALMOST DONE" Screenshots hide failed checks Code sits unmerged on one laptop (“90% written”). OUTCOME AT DONE GATE: NOT ACCEPTED Cannot be signed off; unfinished items return to the Product Backlog. REQUIRED EVIDENCE CHAIN · TRACEABLE INCREMENT 01 STORY & CRITERIA Given / When / Then + DoD 02 LIVE INCREMENT DEMO Show working product + limits PART B · INDIVIDUAL /10 Evidence /4 + Live /6 Demo 1 attributable User Story, apply Acceptance Criteria, and answer 1 directed question. PART D · SPRINT REVIEWS (8% EACH) Group /40 + Individual /60 Live Backlog, Sprint Plan, demo, Test Report, role evidence, and 48-hour Retrospective submission. Slides may support the session, but never replace working results.
Text version of the diagram

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).

Full specification walkthrough: detailed Part B and Part D rubrics, plus the In-person Class Test briefing, take place in this week's Seminar.
Sprint Review · 5 to 15 min
Sprint Retrospective · Quality and effectiveness

Sprint Retrospective: Inspect How We Worked

Plain anchor: A team-only meeting after Sprint Review to look at how we worked and pick one concrete fix for the next Sprint.
Step 01

Gather Facts

What actually happened in code, merges, handoffs and communication?

Evidence before feelings
Step 02

Find Cause

Which missing habit, rule, or tool bottleneck allowed the failure?

Workflow root cause
Step 03

Pick One Change

Select one small, testable practice to run during the next Sprint.

Focus beats ten wishes
Step 04

Set Check

Assign who checks it and the exact day to verify whether it worked.

Owner + review point
Part D 48-hour rule Submit a structured Sprint Retrospective within 48 hours of each Sprint Review (date, participants, fact-backed wins/issues, owned actions, and prior follow-up).
Sprint Retrospective · 15 to 25 min
Sprint Retrospective · Facilitation rules

Fix the Workflow, Not the Person

Psychological Safety: making it safe to raise errors and blockers early without fear of personal attack.
Blameless Analysis: asking what broke in our workflow or tools before asking who clicked merge.
Blame frame · Fails to improve
“Developer X always breaks main on Friday afternoon.”
Result: teammates hide problems until the last hour, avoid risky commits, and stop speaking honestly in the Retrospective.
Blameless frame · Produces a rule
“No daily cut-off or peer-review rule protected main before Friday 16:00.”
Result: the team designs a lightweight pull-request guard that catches defects regardless of who writes the code.
Scope boundary: Retrospectives examine team process and engineering habits. You are never required to disclose sensitive personal or interpersonal conflict.
Sprint Retrospective · 15 to 25 min
Improvement design · From feeling to experiment

A Feeling Is Not an Action Plan

Weak wish: “Test earlier and communicate better next Sprint.” (Zero trigger, zero owner, zero check date.)
Five-link Evidence-to-Action chain turning a workflow fact into an owned experiment Five connected boxes in sequence: 1 Fact (observable event), 2 Process Cause (missing rule or habit), 3 Specific Behaviour (concrete rule), 4 Action Owner (teammate responsible for making it happen), and 5 Review Point (exact day in next Sprint to verify). 01 · FACT Observable event Time, artefact, or measured failure. 02 · CAUSE Workflow gap Blameless reason in process or tools. 03 · BEHAVIOUR Concrete practice Observable habit with clear time or trigger. 04 · ACTION OWNER Named role accountable Makes sure the agreed change actually runs. 05 · REVIEW POINT Exact day to verify Next Sprint check to confirm it worked.
Text version of the diagram

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).

Sprint Retrospective · 15 to 25 min
Worked example · Fictional teaching case

Sprint 1 Close Evidence: What Happened?

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?
Worked example · 25 to 35 min
Worked example · Part 1: Sprint Review · Fictional teaching case

Sprint Review Decisions: Sign-Off and Adaptation

PROMPT 01 · ACCEPTANCE CHECK

Can Story 2 be signed off as Done?

Demo works with the Day 4 5-dish stub, but real CSV import fails two Acceptance Criteria and lacked peer review.

PROMPT 02 · BACKLOG ADAPTATION

Must dark mode go into Sprint 2?

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.

Story 1
Signed off as Done: meets every Acceptance Criterion and all four DoD checks live on a test phone.
Story 2
Not Done (Return): demonstrate the working Day 4 stub honestly, state the CSV failures, and return unfinished CSV work to the Product Backlog.
Dark mode
Ordered by Product Owner: record the request in the Product Backlog; finishing real menu data and core order safety outranks visual theming.
Fictional teaching case
Worked example · 25 to 35 min
Worked example · Part 2: Sprint Retrospective · Fictional teaching case

Retrospective Fix: From Wish to Owned Rule

Before (vague wish): “Be more careful before merging and communicate better in Sprint 2.”

Ask pairs how to turn the Friday 15:30 incident into an owned rule before revealing the 5-link rewrite.

01 Fact
Friday 15:30 unreviewed CSV push broke main login for 20 minutes before Review.
02 Cause
No daily pull-request cut-off or peer-review check existed before merging to main.
03 Behaviour
Open a pull request by 16:00 daily; one rotating teammate reviews and tests before merge.
04 Action Owner
Developers run the daily review rota; Scrum Master checks compliance and clears blockers.
05 Review Point
Inspect the Sprint 2 merge log together at Sprint 2 Day 3 Daily Scrum.
Fictional teaching case
Worked example · 25 to 35 min
Guided application · Fictional teaching case

Activity: Close Sprint 1 and Fix One Habit

Sprint 1 Close Input (Pairs)
Review input

Story 2 runs only on the Day 4 stub (2 CSV checks fail). Stakeholder asks: “Add Order Rating next.”

Retrospective input

“Some teammates started coding too late on Thursday.”

01Review decision: state Story 2's status and how the Product Owner adapts the Product Backlog for “Order Rating”.
02Retrospective rewrite: turn the vague note into a blameless 4-part action (Fact, Behaviour, Action Owner, Review Point).
04 min in pairs03 min class debrief
Fictional teaching case
Guided application · 35 to 42 min
Close

Three Things to Take Away

01

Sprint Review inspects working output with Stakeholders to drive Backlog Adaptation.

02

Incomplete stories return to the Product Backlog; slides never substitute for Definition of Done.

03

Sprint Retrospective uses Blameless Analysis inside Psychological Safety to assign one change with an Action Owner and Review Point.

Exit check: In one sentence, what does Sprint Review change versus what does Sprint Retrospective change?
One sentence
on the way out
Exit check and transition · 42 to 45 min
Transition · Seminar and Week 9

Next: Week 8 Seminar and Week 9

This Week's Seminar (2 × 45 min)
Part B & D walkthrough, Class Test briefing, and simulation.
Walk through full Part B (/10) and Part D (Sprint Reviews + 48h Retro) specifications and rubrics, receive the In-person Class Test briefing (format, scope, central scheduling), and simulate Review and Retro on your team artefacts.
Next Week's Lecture (S1 Week 9)
Product Design and Confirmation.
Turn adapted Product Backlog stories and stakeholder feedback into user flows, low-fidelity wireframes, interaction states, and evidence-based confirmation checks.
Seminar evidence produced this week Review agenda · Backlog Adaptation decision · 48h Sprint Retrospective record
Exit check and transition · 42 to 45 min

Speaker notes