<aside> <img src="/icons/target_blue.svg" alt="/icons/target_blue.svg" width="40px" />
Release and Sprint Planning
Two releases across two sprints, planned from one product backlog.
</aside>
| Release | Sprint | Environment | Address | Content |
|---|---|---|---|---|
| Release 1 | Sprint 1 | Staging, Docker on a VPS | culprit.wyco-dev.com | Public site, admin console, Events module, Calendly booking with a Turnstile check |
| Release 2 | Sprint 2 | Production, Vercel | culprits-mystery.party | Lab website with member pages and teams, Intaglio design, event galleries, mandatory two-step admin sign-in, Neon standby |
<aside> <img src="/icons/code_gray.svg" alt="/icons/code_gray.svg" width="40px" />
Release process Every merge to main runs lint, type checks and the full test suite, migrates the database and releases staging automatically. Production is released by hand on Vercel after the change is checked on staging.
</aside>
| Meeting | Date | Objective | Decisions | Outcome | Actions |
|---|---|---|---|---|---|
| Release planning (Team Meeting #1, SE-MIN-002) | 24 Jul 2026 | Agree the process, roles and tools for the project | Scrum across two sprints from one product backlog (DEC-005); roles as in the team charter (DEC-006); Figma, GitHub and Canva (DEC-008 to DEC-010) | Two sprints, each closing with a review and a release | Set up the repository, design file and workspace (Pre-Sprint Setup) |
| Sprint 1 planning | Start of Sprint 1 | Set the Sprint 1 goal and commitment | Goal: ship the public content modules and admin panel; prove the staging pipeline end to end | Committed: Events module, public content pages, Calendly booking, public release | Sprint 1 Backlog |
| Sprint 2 planning (Sprint 1 Review, SE-MIN-006) | 8 Sep 2026 | Set the Sprint 2 goal from the Sprint 1 review | Release the deferred features with stakeholder sign-off; put production on Vercel separately from staging; close the DevOps open items | Sprint 2 opened on 8 September | Sprint 2 Backlog |
| Sprint 2 scope update (team channel) | 11 Sep 2026 | Plan the move to the lab website | Professor's information moves to Team, Director, profile, with the same page for every member; only the admin edits content; public tabs serve the whole team; director's research and publications highlight registered members | Lab re-scope started the same day (PR #15, ADR-016) | Apply the design feedback; revise the SDS |