Sprint calendar and cadence¶
How to use: this is the single schedule of record for Group 9. Every ceremony below has a date. If the instructor moves a deadline, change it here first, then in project.yml and the GitHub milestones, then in PROJECT_PLAN.md.
Course: SWE 380 / CSC 580, University of Michigan-Flint. Instructor: Prof. Mohamed Wiem Mkaouer (@mkaouer). Team: Leticia Aderhold, Jerad Dunne, Hina Kramer. Allie Hodges was a member from ADR-0006 until she left the course in Sprint 2 (D-025).
Sprint calendar¶
| Period | Dates (weekday) | Scrum phase | DMAIC phase | Product Owner | Scrum Master | Deliverable | Rubric weight |
|---|---|---|---|---|---|---|---|
| Formation | Thu 2026-09-10 to Wed 2026-09-16 | Formation and discovery | Define | Jerad Dunne | Jerad Dunne | Topic brief and initial backlog | 10% |
| Sprint 1 | Thu 2026-09-17 to Wed 2026-10-07 (due Oct 7) | Research framing and data foundation | Measure | Jerad Dunne | Leticia Aderhold | Sprint 1 research-and-data package | 20% |
| Sprint 2 | Thu 2026-10-08 to Wed 2026-10-28 (due Oct 28) | Implementation and validation | Analyze | Jerad Dunne (D-025) | Hina Kramer | Sprint 2 implementation-and-evidence package | 20% |
| Sprint 3 | Thu 2026-10-29 to Wed 2026-11-18 (due Nov 18) | Analysis, integration, and communication | Improve | Leticia Aderhold | Jerad Dunne | Sprint 3 complete draft and demonstration | 25% |
| Break | Thu 2026-11-19 to Sun 2026-11-29 (Thanksgiving Thu 2026-11-26) | Buffer | Improve (carry-over only) | - | - | No planned work; respond to feedback if received | - |
| Finalization | Mon 2026-11-30 to Fri 2026-12-04 | Finalization and presentation | Control | Hina Kramer | to be chosen at Sprint 3 planning (D-025) | Final report, repository release, presentation, individual reflections | 20% demo + 5% individual |
Roles are proposed and are confirmed at the 2026-09-16 kickoff. Everyone is a Developer/Researcher in every sprint. A role is not a substitute for shared responsibility: every member contributes technical or research work and participates in review every sprint.
Weekly rhythm (every sprint)¶
| Day | Event | Owner | Where it is recorded |
|---|---|---|---|
| Thursday (sprint day 1) | Sprint planning, 60 minutes | Scrum Master facilitates, Product Owner brings the backlog | docs/sprints/<sprint>/planning.md and docs/meeting-notes/YYYY-MM-DD-planning.md |
| Monday, Wednesday, Friday | Written async stand-up (done / next / blockers / hours) by 21:00 | Every member | docs/meeting-notes/YYYY-MM-DD-standup-week.md (one file per week) |
| Thursday (mid-sprint) | Check-in, 30 minutes, plus Lean Six Sigma metrics review | Scrum Master | docs/meeting-notes/YYYY-MM-DD-checkin.md |
| Sunday | Weekly metrics snapshot PR generated by GitHub Actions | Automation; Scrum Master reviews, another member approves | docs/lean-six-sigma/metrics/DASHBOARD.md |
| Last Wednesday of the sprint | Sprint review (45 minutes), then retrospective (45 minutes) | Product Owner runs the review, Scrum Master runs the retro | docs/sprints/<sprint>/review.md and retrospective.md |
Ceremony schedule with dates¶
Formation (Define)¶
- Sun 2026-09-13: repository created, charter and templates published.
- Mon 2026-09-14: topic P-01 selected (ADR-0004); the project briefly switched to solo execution (ADR-0005).
- Tue 2026-09-15: four-person group reinstated (ADR-0006); Leticia Aderhold, Allie Hodges, and Hina Kramer invited with write access to the repository and the board.
- Wed 2026-09-16: group kickoff. Roles confirmed, charter signing started through onboarding pull requests, second raters chosen for each validation kind, topic brief and initial backlog submitted.
- Before Thu 2026-09-17: any member may open a Decision needed issue to revisit P-01.
Sprint 1 (Measure)¶
- Thu 2026-09-17: Sprint 1 planning.
- Fri 2026-09-18, Mon 09-21, Wed 09-23, Fri 09-25, Mon 09-28, Wed 09-30, Fri 10-02, Mon 10-05, Wed 10-07: written stand-ups.
- Sun 2026-09-20, Sun 09-27, Sun 10-04: metrics snapshot PRs.
- Thu 2026-09-24: check-in 1 and metrics review.
- Thu 2026-10-01: check-in 2 and metrics review; decision on sample only versus a full-dataset pass.
- Wed 2026-10-07: Sprint 1 review and retrospective. Sprint 1 package due.
Sprint 2 (Analyze)¶
- Thu 2026-10-08: Sprint 2 planning.
- Fri 2026-10-09, Mon 10-12, Wed 10-14, Fri 10-16, Mon 10-19, Wed 10-21, Fri 10-23, Mon 10-26, Wed 10-28: written stand-ups.
- Sun 2026-10-11, Sun 10-18, Sun 10-25: metrics snapshot PRs.
- Thu 2026-10-15: check-in 1 and metrics review.
- Fri 2026-10-16: second-rater round 1 labels committed (target).
- Thu 2026-10-22: check-in 2 and metrics review.
- Tue 2026-10-27: validation scoring and error analysis complete.
- Wed 2026-10-28: Sprint 2 review (validation results presented) and retrospective. Sprint 2 package due.
Sprint 3 (Improve)¶
- Thu 2026-10-29: Sprint 3 planning.
- Fri 2026-10-30, Mon 11-02, Wed 11-04, Fri 11-06, Mon 11-09, Wed 11-11, Fri 11-13, Mon 11-16, Wed 11-18: written stand-ups.
- Sun 2026-11-01, Sun 11-08, Sun 11-15: metrics snapshot PRs.
- Thu 2026-11-05: check-in 1 and metrics review.
- Thu 2026-11-12: check-in 2 and metrics review; presentation rehearsal 1.
- Wed 2026-11-18: Sprint 3 review and retrospective. Complete draft, tagged release candidate, and demonstration plan due.
Break and Finalization (Control)¶
- Thu 2026-11-19 to Sun 2026-11-29: no planned work. Thanksgiving is Thu 2026-11-26.
- Mon 2026-11-30: finalization planning (30 minutes); respond to instructor feedback; rehearsal 2.
- Tue 2026-12-01 to Thu 2026-12-03: fixes, README verified by a non-author on a fresh clone, tag
v1.0.0, GitHub release, rehearsal 3. - Fri 2026-12-04: final presentation; individual reflections submitted.
What each folder contains¶
| Folder | Contents |
|---|---|
00-formation/ |
planning.md (formation checklist with owners and dates), review.md (evidence that formation is complete) |
sprint-1/, sprint-2/, sprint-3/ |
planning.md (goal, capacity, candidate backlog, risks, DMAIC exit criteria), review.md (rubric checklist, acceptance table, demo script, feedback, gemba walk), retrospective.md (data first, 5 Whys, kaizen actions, recorded changes) |
finalization/ |
checklist.md (final submission checklist, release steps, rehearsal schedule, response-to-feedback log) |
Definition of Ready and Definition of Done (summary)¶
Full text lives in docs/PROCESS.md.
Definition of Ready (an issue may enter a sprint when):
- [ ] It has an owner, a meaningful description, and at least one acceptance criterion.
- [ ] It is linked to a milestone and carries a type: label and an estimate (1, 2, 3, 5, or 8 points).
- [ ] Dependencies and needed data are identified.
Definition of Done (an issue may move to Done when):
- [ ] The work is on main through a pull request approved by a member other than the author.
- [ ] Tests pass in CI, and any generated tables or figures are regenerated by the pipeline, not pasted in.
- [ ] Documentation touched by the change (README, data dictionary, threats, decisions) is updated.
- [ ] The pull request links the issue, describes testing, and names generated outputs.
Board statuses: Todo, In progress, Done, Block, Cancelled. WIP limit: 5 across the team, at most 2 In progress per person.