Sprint 1 Backlog (Core HR Platform)¶
Sprint Dates: TBD (2-week iteration) Generated: 2025-11-22
1. Sprint Goal¶
Establish platform foundation and tenant activation funnel: deliver modular monolith baseline, core signup + invite + magic link flows, and initial employee profile read-only view. Achieve first end-to-end activation trace from anonymous visitor to tenant dashboard with at least one invited user.
2. Success Criteria¶
- Anonymous visitor can sign up and land in tenant dashboard (<2m total flow).
- Admin can invite a user; invitee activates via magic link and accesses tenant.
- Isolation tests pass for basic tenant data boundaries.
- Employee profile read-only view accessible (empty or sample employee).
- Activation funnel events visible in analytics dashboard.
3. Committed Stories / Requirements¶
| ID | Title | Epic | Points | Notes |
|---|---|---|---|---|
| REQ-ARCH-1 (part of REQ-131) | Service boundary & project scaffolding | CORE-ARCH | 5 | Initial modules + layering |
| REQ-ARCH-2 (part of REQ-133) | SPA/PWA shell minimal | CORE-ARCH | 5 | Basic layout + routing |
| REQ-ARCH-3 (subset REQ-134) | Tenant isolation pattern baseline | CORE-ARCH | 5 | Data access filter + test harness |
| US-101 | Self-service signup & tenant creation | CORE-USER | 5 | Full acceptance suite |
| US-102 | Email invite creation & resend | CORE-USER | 3 | Exclude resend automation |
| US-103 | Magic link activation | CORE-USER | 3 | Reuse token validation module |
| US-301 (subset) | Employee profile read-only (core fields) | HR-EMP | 3 | Edit deferred to Sprint 2 |
| TECH-OBS-1 | Activation funnel event instrumentation | CROSS | 3 | Emit + log + trace |
| TECH-QA-1 | Isolation & activation automated test suite | CROSS | 5 | Coverage signup/invite/activation |
| BUFFER | Contingency / emergent tasks | - | 4 | ~15% capacity buffer |
Indicative Total: 41 points (includes buffer & cross-cutting tasks). If velocity baseline lower, reduce scope by deferring US-301.
4. Capacity & Allocation¶
- Engineers: 4
- Nominal velocity target: 34–38 pts (ramp) → Slightly aggressive plan; monitor daily burndown.
- Buffer reserved for defects, integration adjustments, environment setup.
5. Task Breakdown (Examples)¶
| Story/Req | Tasks |
|---|---|
| REQ-ARCH-1 | Repo structure, base modules (auth, tenant, employee), code quality tooling setup |
| REQ-ARCH-2 | SPA scaffold, routing, layout shell, feature flag infra placeholder |
| REQ-ARCH-3 | Tenant context injection, DB filter/middleware, isolation test fixtures |
| US-101 | API endpoint, validation, tenant provisioning service, dashboard redirect, events |
| US-102 | Invitation model, invite create endpoint, email template, status table UI, audit event |
| US-103 | Token validation endpoint, activation form, password policy reuse, activation events |
| US-301 | Employee entity stub, read endpoint, simple display component |
| TECH-OBS-1 | Event schema, logging adapters, trace IDs, dashboard config scripts |
| TECH-QA-1 | E2E tests (signup->invite->activation), isolation tests, CI pipeline wiring |
6. Dependencies & Sequencing¶
- REQ-ARCH-1 scaffolding before all feature tasks.
- Tenant isolation baseline (REQ-ARCH-3) before profile access & event instrumentation.
- Signup (US-101) before invite (US-102) before activation (US-103) for end-to-end test assembly.
- Observability (TECH-OBS-1) starts after initial endpoints stubbed.
- QA suite (TECH-QA-1) incremental as flows emerge; finalization end of sprint.
7. Risks & Mitigations (Sprint-Level)¶
| Risk | Impact | Mitigation |
|---|---|---|
| Over-investment in architecture boilerplate | Delays feature delivery | Define strict MVP boundary; defer service extraction |
| Email deliverability delays invite testing | Block activation flow | Use dev mail sink + manual token retrieval fallback |
| Isolation pattern complexity | Rework near launch | Keep pattern minimal; expand next sprint |
| Frontend shell churn | UI instability | Agree on minimal layout; postpone advanced theming |
8. Definition of Done (Sprint Increment)¶
- All committed stories meet individual DoD.
- End-to-end signup→invite→activation tested & traceable.
- Isolation tests green in CI.
- Observability events visible & documented.
- Sprint review demonstrates activation funnel.
9. Non-Functional Focus This Sprint¶
- Security: password hashing & token TTL enforced.
- Observability: core activation trace.
- Performance: signup & invite endpoints p95 baseline capture (no tuning yet).
10. Exit Criteria¶
- Demo: Create tenant, invite user, activate user, view employee profile.
- Burndown shows no high-risk carry-over items.
- Decision log updated for any architecture deviations.
11. Open Questions¶
- Include email verification in Sprint 1 or later?
- Minimum tenant dashboard content (empty state vs quickstart checklist)?
- Activation funnel dashboard tool (in-house vs existing analytics)?
Version: 1.0