Sprint 3 review: analysis, integration, and communication

How to use: the Product Owner runs the review on Wed 2026-11-18. Every rubric bullet must link to evidence in this repository. Rubric weight: 25%.

Date: 2026-11-18. Product Owner: Leticia Aderhold. Scrum Master: Jerad Dunne. Present: [ ] Leticia Aderhold [ ] Jerad Dunne [ ] Hina Kramer [ ] Instructor (if present)

Sprint goal check

• Sprint goal (from planning):
• Met: yes / partially / no. Explain in two sentences:

Rubric review checklist (verbatim from the assignment)

The Sprint 3 review must include:

• Final or near-final results addressing the research question. Evidence:
• Robustness checks, sensitivity analysis, or comparison across meaningful subgroups. Evidence:
• Error analysis and manually inspected examples. Evidence:
• Final figures and tables generated from the repository pipeline. Evidence:
• A complete draft report with citations and a clear separation between findings and interpretation. Evidence:
• A threat-to-validity section addressing dataset bias, measurement error, confounding, missing data, reproducibility, and generalizability. Evidence:
• A documented release or tagged version of the repository. Evidence:
• A final demonstration plan and presentation materials. Evidence:
• A retrospective identifying the group's most important process improvement. Evidence:

Sprint 3 acceptance criteria (verbatim)

Criterion	Pass / Fail	Evidence link	Notes
A new user can follow the README to reproduce the primary results		Gemba walk below
The report answers the question with evidence
Limitations are explicit
All major artifacts are traceable to issues, commits, pull requests, or decisions		Traceability audit below

Traceability audit

Artifact (figure, table, decision, dataset step)	Produced by (script)	Issue #	PR #	ADR	OK?

Demo script (15 minutes, rehearsal for the final)

Step	Content	Time	Presenter
1	Question and why it matters	1 min
2	Data: snapshot, sample, unit of analysis, key variables	2 min
3	Live: fresh clone, make pipeline, make figures	4 min
4	Results: main table, main figure, robustness check	4 min
5	Error analysis and limitations, including inter-rater agreement	2 min
6	Process story: velocity, cycle time, contribution balance, and the biggest process improvement with numbers	2 min

Gemba walk: fresh-clone reproduction record

Field	Value
Who (a member who did not write the README; README only, no help) and environment
Date
Tag or commit SHA
Steps followed
Time to primary result (minutes)
Result matched committed output	yes / no
Problems found (open issues)

Instructor feedback

Feedback	Action	Owner	Issue #	Due (finalization)

Velocity and KPIs at review

Metric	Sprint 1	Sprint 2	Sprint 3
Points planned / completed
Issues closed
PRs merged / merged with an approving review from another member
Median PR first-review turnaround (hours)
Median cycle time (days)
Median PR open-to-merge time (hours)
CI pass rate
Rework items
Contribution share per member (min / max)
Test count / coverage

Backlog changes agreed for finalization

• Must fix before submission:
• Nice to have:
• Cancelled: