Sprint 1 retrospective¶

How to use: the Scrum Master facilitates on Wed 2026-10-07 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 explain what the group learned and what changed in the backlog.

Date: 2026-10-07. Facilitator: Leticia Aderhold. Attendees: [ ] Leticia Aderhold [ ] Jerad Dunne [ ] Allie Hodges [ ] Hina Kramer

1. Data first¶

Paste the Sprint 1 rows from docs/lean-six-sigma/metrics/DASHBOARD.md. Compare against the targets in docs/lean-six-sigma/KPIS.md.

KPI	Target	Sprint 1 value	In control?	Comment
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. What went well¶

-¶

3. What did not go well¶

-¶

4. Puzzles and open questions¶

-

5. Root cause on the top issue (5 Whys)¶

Use docs/lean-six-sigma/ROOT_CAUSE_TEMPLATE.md for the long form. Pick the single item with the largest effect on the sprint goal.

Problem statement:
Why 1:
Why 2:
Why 3:
Why 4:
Why 5:
Root cause:
Waste category (see docs/lean-six-sigma/WASTE_LOG.md):

6. Kaizen actions¶

Action	Owner	Kaizen issue #	Due	How we will know it worked

7. What we learned (rubric)¶

About the dataset:
About the research question:
About working together (onboarding, reviews, communication):

8. Changes recorded (rubric)¶

What changed	From	To	Reason	Where recorded
Research question				ADR / `RESEARCH_QUESTION.md`
Method
Scope
Interpretation
Backlog (added / removed / re-estimated)				Milestone `Sprint 2`

9. Retro on the retro¶

Does the charter still fit? yes / no. Proposed change:
Format worked: yes / no. Change for next time: