Skip to main content

Requirements — MVP-1 epics

Features are goals; requirements are epics. Each page under Functional and Non-functional takes one MVP-1 feature — the feature architecture is the goal — and breaks it into FR-/NFR- statements each sized to become one or a few user stories, with Given/When/Then acceptance criteria, dependencies, and traceability back to the feature doc and the C4 model.

How to read these​

  • Scope = the MVP-1 cut of the feature; later tiers sit under Out of scope.
  • FR-/NFR-<n> = a requirement sized for one or a few user stories. Priority P1 (must-have for MVP-1) / P2 (should-have). Status marks what is already built vs. still to build.
  • Acceptance = Given/When/Then, naming the flow-test or SDK anchor where one exists.
  • Traces to = the feature doc (the goal) + the C4 component that satisfies it.

Sections​

  • Functional — user-facing capabilities (something a member / admin does).
  • Non-functional — quality attributes and cross-cutting gates (security, COPPA / privacy, the accessibility floor, offline-sync, the authz model, analytics). Graded on operational KPIs; these are pass/fail release gates, not features.
  • Prioritization (RICE) — the scoring matrix that defines the MVP-1 cut and the build order.
  • MVP-1 decisions log — every open decision, resolved.

MVP-1 scope​

Sourced from the prioritization §3 cut:

  • Functional — Today, Onboarding, Member Profile, Catalog, Household, Money & Envelopes, Routines, Visual timers, Notifications (local), Admin, Settings, Print & printables, Account & profile management.
  • Non-functional — Terms & consent, Security & data protection, Personas (authz model), Children's privacy (COPPA), Offline sync, Analytics & telemetry, Accessibility floor.