Watchtower-Course-Project

Sprint 3 Planning Summary

Note: Sprints 1 and 2 have detailed planning documents written up front. This Sprint 3 summary was reconstructed after the fact from the Sprint 3 standup notes, the Sprint 3 retrospective, and the Sprint 3 decision log. Items that are not explicitly documented in those notes are marked as such. Sources: ../meetings/Sprint/3/, retrospectives/Retrospective 3.md.

Project

WatchTower (Group 09 — “Akatsuki”)

Sprint Goal

Move from two parallel prototypes toward a single product direction: merge the strongest frontend ideas from both prototypes into a people-focused UI, harden the event capture/backend plumbing behind it, and produce the Agile Team Status Video.

What Changed From Sprint 2

Major Planned / Tracked Work

Reconstructed from the Sprint 3 decision log:

Item Focus Issue
Restructure standup/meeting docs to be readable and easy to update Process/Docs #45
Update ADRs to reflect new backend technologies Docs #53
Add filters for querying the event database Backend #54
SDK logic to send correct JSON to the correct endpoints Backend/SDK #55
Verify the event schema fields can all be captured (research new APIs if not) Backend #56
Merge the two frontend candidates into one design Frontend #57
Produce the Team Status Video (slides + script + recording) Whole team

Focus Areas

Owners (from notes)

Risks / Blockers (from the retrospective)

Outcome / Status