Proposed Sprint 1 discovery completion plan
This public-site discovery package is a baseline. Sprint 1 requirements are not approved merely because the crawl is complete. No replacement website is built in this task.
Work packages and acceptance evidence
| Priority | Work | Proposed owner | Completion evidence / dependency |
|---|---|---|---|
| P0 | Review the discovery report and P0 questions with the office manager | Office manager + project owner | Recorded answers, scope boundaries and named decision owners |
| P0 | Establish domain, content/media and integration ownership | Practice owner/manager; current agency supplies information if authorized | Ownership matrix, export availability and handover path; credentials stay outside repo |
| P0 | Define appointment/contact/chat data flow and handling boundary | Office manager + practice's designated privacy/technical reviewers | Approved fields, destinations, access, notifications, retention and responsibility; request vs booking semantics agreed |
| P0 | Agree staff account, role and approval requirements | Office manager + clinical approver | Approved capability matrix, offboarding/recovery owner and representative editing scenarios |
| P1 | Reconcile all URLs and content | Content/SEO owner + office manager | Every discovered URL has keep/update/merge/retire disposition; separately fetched failures resolved or accepted as gaps; archive migration strategy agreed |
| P1 | Confirm asset reuse and gallery pairing | Office manager + rights/clinical owner | Approved media manifest and sources; missing originals or consent/rights evidence assigned for follow-up |
| P1 | Complete responsive and accessibility follow-up | Implementer/QA with staff | Template coverage, keyboard/screen-reader and contrast findings triaged; third-party widget limitations tracked |
| P1 | Evaluate two CMS candidates against the same tasks | Implementer + actual staff editors | Usability results, server-side permission checks, preview/rollback/export proof, recurring-cost/support comparison; no production build required |
| P1 | Approve architecture decision and migration approach | Project owner + office manager | Short decision record tying CMS/delivery/hosting choices to requirements, cost, maintenance and SEO constraints |
| P2 | Convert findings into implementation backlog and acceptance checks | Implementer + project owner | Prioritized backlog with owners, estimates, dependencies and definition of done |
Suggested sequence
First hold a focused requirements/ownership meeting using office-manager-questions.md. Next resolve the appointment/data and editorial permission decisions because they drive integration and CMS design. In parallel organizational work, staff can review content and media ownership; no additional agents are required. After those decisions, conduct a bounded CMS comparison using synthetic content and a content/URL reconciliation review. Close Sprint 1 with an approved scope and architecture decision, not a speculative frontend implementation.
Definition of discovery complete
- Public-site findings, evidence and coverage limits are reviewed and accepted.
- P0 decisions are answered or explicitly deferred with an owner, date and impact on implementation.
- The practice approves an authoritative content list, migration URL strategy, asset reuse process and SEO baseline.
- Staff roles, authentication/account ownership and publishing approval are specified with acceptance scenarios.
- Appointment and communication boundaries are explicit; no assumed backend behavior is treated as a requirement.
- A CMS/hosting decision is supported by staff tasks, permission evidence and a maintenance/cost plan.
- The next sprint has an agreed backlog, acceptance checks, dependencies and a responsible technical owner.
Scope exclusions and open verification
No production form submission, appointment reservation, login, administrative inspection, security probing, legal/compliance certification, vendor negotiation or current-site modification. Public discovery does not validate delivery success, spam handling, backend storage, calendar availability, staff response, private portal features, analytics attribution, accessibility conformance or historical redirects. These need later authorized evidence and, where applicable, approved synthetic tests.