Sprint 2 retrospective¶
How to use: the Scrum Master facilitates on Wed 2026-10-28 right after the review. Data first, then discussion, then root cause, then actions. Every action becomes a kaizen issue and a row in docs/lean-six-sigma/KAIZEN_BACKLOG.md. The rubric requires this retrospective to record changes to the research question, method, scope, or interpretation.
Date: 2026-10-28. Facilitator: Hina Kramer. Attendees: [ ] Leticia Aderhold [ ] Jerad Dunne [ ] Allie Hodges [ ] Hina Kramer
1. Data first¶
Paste the Sprint 2 rows from docs/lean-six-sigma/metrics/DASHBOARD.md next to Sprint 1.
| KPI | Target | Sprint 1 | Sprint 2 | 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 1 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¶
| 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 Sprint 3 |
9. Retro on the retro¶
- Does the charter still fit? yes / no. Proposed change:
- Format worked: yes / no. Change for next time: