Sprint 3 retrospective¶
How to use: the Scrum Master facilitates on Wed 2026-11-18 right after the review. Data first, then discussion, then root cause, then actions. The rubric requires this retrospective to identify the group's most important process improvement; section 9 is mandatory and should be supported by numbers from the dashboard.
Date: 2026-11-18. Facilitator: Jerad Dunne. Attendees: [ ] Leticia Aderhold [ ] Jerad Dunne [ ] Hina Kramer
1. Data first¶
Paste all three sprints from docs/lean-six-sigma/metrics/DASHBOARD.md.
| KPI | Target | Sprint 1 | Sprint 2 | Sprint 3 | Trend | In control? |
|---|---|---|---|---|---|---|
| Points completed / planned | 0.80 | |||||
| Median issue cycle time (days) | 5 | |||||
| Median PR first-review turnaround (hours) | 48 | |||||
| Median PR open-to-merge time (hours) | 96 | |||||
| PRs merged without an approving review from another member | 0 | |||||
| CI pass rate on main | 0.90 | |||||
Rework items (rework label) |
||||||
| Stand-ups posted / expected | ||||||
| Contribution share per member (min / max) | 0.15 to 0.45 | |||||
| Hours logged per member (min / max) |
2. Did the Sprint 2 kaizen actions work?¶
| Kaizen issue # | Action | Owner | Effect seen in the data? | Keep / adjust / drop |
|---|---|---|---|---|
3. What went well¶
-
4. What did not go well¶
-
5. Puzzles and open questions¶
-
6. Root cause on the top issue (5 Whys)¶
- Problem statement:
- Why 1:
- Why 2:
- Why 3:
- Why 4:
- Why 5:
- Root cause:
- Waste category:
7. Kaizen actions for finalization¶
| Action | Owner | Kaizen issue # | Due | How we will know it worked |
|---|---|---|---|---|
8. Changes recorded (rubric)¶
| What changed | From | To | Reason | Where recorded |
|---|---|---|---|---|
| Research question | ||||
| Method | ||||
| Scope | ||||
| Interpretation | ||||
| Backlog | Milestone Finalization |
9. Most important process improvement this semester (rubric, mandatory)¶
Write one paragraph agreed by the team. Name the improvement, when it was introduced (kaizen issue #), the KPI it moved, and the before and after values. This paragraph goes into the final presentation and the report's artifact appendix.
- Improvement:
- Introduced in sprint / kaizen issue #:
- KPI affected:
- Before:
- After:
- Why we believe the improvement caused the change (and the alternative explanation):
10. Retro on the retro¶
- Does the charter still fit? yes / no. Proposed change:
- Format worked: yes / no. Change for next time: