Team¶
How to use: one profile per member (from TEMPLATE-member-profile.md), the role rotation, and the RACI. Update your own profile by pull request whenever your availability changes.
Roster¶
| Member | GitHub | Profile | Onboarding issue |
|---|---|---|---|
| Leticia Aderhold | @angel06la | leticia-aderhold.md |
pending |
| Jerad Dunne | @jeraddunne | jerad-dunne.md |
pending |
| Allie Hodges | @AllieHgs | allie-hodges.md |
pending; left the course in Sprint 2 (D-025) |
| Hina Kramer | @hinak786 | hina-kramer.md |
pending |
The repository was set up on 2026-09-13 for this four-person group, ran briefly as a solo project on 2026-09-14 (ADR-0005), and returned to the four-person group on 2026-09-15 (ADR-0006). Leticia, Allie, and Hina were invited as collaborators with write access on 2026-09-15. Allie Hodges left the course during Sprint 2 (D-025, recorded 2026-10-16); the group continues with three members.
Role rotation¶
Proposed; confirm at the 2026-09-16 kickoff and update project.yml (roles:) if changed.
| Period | Product Owner | Scrum Master (also metrics owner) |
|---|---|---|
| Formation (Sep 10 to 16) | Jerad Dunne | Jerad Dunne |
| Sprint 1 (Sep 17 to Oct 7) | Jerad Dunne | Leticia Aderhold |
| Sprint 2 (Oct 8 to Oct 28) | Jerad Dunne (D-025) | Hina Kramer |
| Sprint 3 (Oct 29 to Nov 18) | Leticia Aderhold | Jerad Dunne |
| Finalization (Nov 30 to Dec 4) | Hina Kramer | to be chosen at Sprint 3 planning (D-025) |
Rationale: every member holds each of the two roles at least once across the semester; the member who set up the repository holds Product Owner first so the initial backlog matches the rubric, then hands over.
Validation rater ids¶
| Member | Rater id | Role in validation |
|---|---|---|
| Jerad Dunne | jd |
Primary rater |
| Leticia Aderhold | la |
Second rater for drift (D-020) |
| Hina Kramer | hk |
Second rater for lineage (D-024) |
| Allie Hodges | ah |
Left the course in Sprint 2 (D-025); no labels |
What each role does¶
See TEAM_CHARTER.md section 3 for the definitions and RACI.md for activity-level responsibility.
Joining steps¶
- Accept the repository invitation.
- Submit the Team member onboarding issue.
- In your first pull request, fill in your profile here and sign
TEAM_CHARTER.mdsection 14. Another member reviews it.
Full path: docs/GETTING_STARTED.md.