Skip to content

Core HR Platform Release Estimation

Generated: 2025-11-22 Source Inputs: docs/000-core-hr.prd.md, docs/backlog/EPICS.md, story files.

1. Scope Overview (MVP)

MVP targets activation, basic HR value, and initial engagement: - EP-CORE-ARCH (foundational subset) - EP-CORE-USER (signup, invite, magic link, tenant switch minimal) - EP-HR-EMP (profile read + limited edit; custom fields basic) - EP-HR-LEAVE (configure types + balances + request workflow) - EP-HR-RECRUIT (job posting + pipeline minimal) - EP-DOC-MGMT (upload contracts; simple metadata)

Deferred to Post-MVP: Performance mgmt (EP-HR-PERF), advanced billing (dynamic pricing), advanced accruals, complex onboarding automations.

2. Effort Buckets (T-Shirt Sizes)

Epic Scope Slice Size Notes
CORE-ARCH Modular monolith + messaging adapter + tenant isolation baseline L Avoid premature service splitting
CORE-USER Signup, invite, magic link, tenant switcher M SSO deferred to later slice
HR-EMP Profile read/edit + custom fields (text/number/date) M Dropdown fields later if needed
HR-LEAVE Types CRUD + monthly accrual job + request workflow M Calendar UI & advanced rules deferred
RECRUIT Job posting + public listing + pipeline board (4 static stages) M Conversion & onboarding tasks later
DOC-MGMT Upload API + signed URL + metadata store S Virus scanning & DLP later
BILLING Static plan view (read-only) XS Activation flows deferred

Legend: XS (0.5–1 dev week), S (1–2), M (2–3), L (3–5).

3. Initial Story Pointing (Indicative)

Story Points
US-101 5
US-102 3
US-103 3
US-301 5
US-302 8
US-311 5
US-312 5
US-321 5
US-322 8
US-331 (Deferred) 0 (future)
REQ-131 8
REQ-132 13
REQ-133 5
REQ-134 8
DOC-MGMT slice (US-201/US-202/REQ-203 combined) 8
BILLING static view 3

Draft total (MVP minus deferred): 92 points (indicative).

4. Team & Velocity Assumptions

Assume: 4 engineers (blend FE/BE), sprint length 2 weeks. Effective velocity (first 2 sprints ramp): ~28–32 points, stabilizing ~34–38. Projected schedule (with 92 points & integration overhead ~15% => ~106 effective): - Sprint 1: Foundation (REQ-131, REQ-133, US-101, US-102) ~26 pts + overhead. - Sprint 2: Tenant switch, magic link (US-103), basic employee profile (US-301), start isolation (REQ-134). ~30 pts. - Sprint 3: Custom fields (US-302), Leave config (US-311), Accrual job infra (part REQ-132). ~32 pts. - Sprint 4: Leave requests (US-312), Job posting (US-321), Pipeline board (US-322), Doc mgmt slice. ~30 pts. - Sprint 5: Hardening, billing view, remaining messaging reliability (REQ-132 remainder), polish & launch readiness. ~25 pts.

Indicative MVP release: End of Sprint 5 (10 weeks elapsed).

5. Critical Path

  1. Architecture baseline (REQ-131/133) → Signup (US-101) → Invite/Magic link (US-102/103).
  2. Isolation patterns (REQ-134) parallel with Employee profile (US-301).
  3. Custom fields (US-302) precedes leave requests only for extended data (nice-to-have dependency; can decouple).
  4. Accrual (US-311) must precede request submission (US-312).
  5. Recruitment board (US-322) depends on job posting (US-321) but independent from leave.
  6. Document management required before onboarding contracts (future), optional for MVP except employment contract upload demo.

6. Risk Register & Mitigations

Risk Category Impact Likelihood Mitigation Owner
Over-engineered microservices early Architecture Schedule slip Medium Modular monolith first, service extraction via load thresholds Tech Lead
Messaging complexity delays async adoption Integration Feature coupling Medium Start synchronous APIs, wrap messaging behind adapter Backend Eng
Multi-tenant isolation flaw Security Data breach Low Automated isolation tests + pre-production pen test Security Eng
Custom field performance degradation Performance Slow profiles Medium Hard field cap + indexing + profiling in staging Backend Eng
Leave accrual race conditions Data Integrity Incorrect balances Low Idempotent accrual job + locking strategy Backend Eng
Pipeline board scaling UX/Perf Degraded hiring UX Medium Implement virtualization threshold (>100 cards) Frontend Eng
Activation funnel drop-offs Product Lower conversion High Instrument funnel events + iterative UX tweaks Product Owner

7. NFR Baselines (MVP Targets)

  • Latency: p95 profile read < 400ms; signup end-to-end < 2s.
  • Security: OWASP top 10 scanning; tenant isolation test suite 100% pass.
  • Availability: 99% (non-critical MVP); degrade gracefully for messaging.
  • Observability: Tracing with correlation IDs across user->tenant provisioning & leave request flows.
  • Data Protection: At-rest encryption for documents & passwords hashed with Argon2.

8. Estimation Assumptions

  • Story points include dev + test automation + review.
  • 15% overhead for integration, refactors, emergent tasks.
  • Velocity improvement after sprint 2 as architecture stabilizes.
  • No major external dependency blockers (e.g., identity provider available early).

9. Contingency & Flex Scope

  • If velocity < planned: Defer recruitment pipeline (US-322) to Post-MVP.
  • If isolation complexity rises: Reduce custom fields types to text only for MVP.
  • Maintain 10–15% buffer in Sprint 5 for stabilization.

10. Release Readiness Checklist (Aggregate)

  • All critical path stories Done & accepted.
  • Tenant isolation penetration test passed.
  • Activation, leave request, pipeline funnels instrumented & dashboards live.
  • Log & trace coverage for signup, invite, accrual, request flows.
  • Security review sign-off; backup & restore tested minimally.
  • Operational runbook drafted (provisioning, incident response, escalation matrix).

11. Post-MVP Candidate Roadmap (High-Level)

  • SSO (US-106) & advanced RBAC.
  • Performance management (US-331/332/333).
  • Advanced billing (usage metrics, upgrade/downgrade self-serve flows).
  • Calendar enhancements + partial-day leave.
  • Candidate conversion & onboarding checklist automation.

12. Open Questions

  1. Target initial set of plan tiers? (Affects BILLING scope expansion.)
  2. Do we require audit export at MVP or Phase 2?
  3. Messaging backbone choice (Kafka vs RabbitMQ) finalization timeline?
  4. Minimum acceptable tenant isolation test coverage metrics definition.

Document Version: 1.0