These are the quality gates every story passes through — DoR before a story can enter a sprint, DoD before it can be called complete. Both teams (Falcon and Anchor) work from the same two checklists so a story's status means the same thing regardless of which team owns it.
Definition of Ready
- Story has a clear user-story statement (As a… I want… so that…)
- Acceptance criteria are written and testable
- Story is sized by the owning team (Planning Poker, in story points)
- Dependencies on the other team are identified and flagged, if any
- UX mockups attached for any patient- or provider-facing screen
- No open compliance or clinical-workflow question blocking the story
- Small enough to complete within a single sprint
Definition of Done
- Code reviewed by at least one other engineer and merged
- Unit and integration tests written and passing
- Acceptance criteria verified against the story by the Product Owner
- Mobile accessibility check passed (screen reader, tap-target size, contrast)
- Security scan clean — no new high/critical findings
- Deployed and verified in the staging environment
- Documentation (API docs or release notes entry) updated
Telehealth-specific additions (beyond a standard software DoD)
- Any story touching patient-identifiable data passes a PHI-handling review by T. Brannigan (Compliance) before it can move to Done
- Any story changing a clinical workflow (scheduling, visit launch, provider notes handoff) gets a quick sign-off from Dr. L. Nguyen (CMIO) — added specifically after Sprint 0 planning flagged that "looks done to engineering" and "safe for a clinical workflow" are not always the same thing
- Data-migration stories additionally require a record-count and spot-check validation step before being marked Done