Epic: Establish ADO Project Management Infrastructure — Phase 0 &ZeroWidthSpace;

ADO reference content — historical. This file captured the draft description, scope, and acceptance criteria for the Phase 0 project-management-setup Epic. The authoritative item is ADO Epic AB#3150 "Establish planning, docs, and repository foundation". Phase 0 is complete; the ADO project, area paths, iterations, and process are in place. Retained as a record of what the setup covered.

Epic overview — COMPLETE &ZeroWidthSpace;

Established the Azure DevOps project management infrastructure and processes that guide Heritage Community Hub development. This was Phase 0 work, completed before Phase 1 sprint planning.

ADO Boards is the single source of truth for all work items. GitHub Issues are an intake mirror only. This epic wired up that model.

As provisioned: the Heritage Community Hub ADO project exists at dev.azure.com/hybridcloudsolutions; area paths \Platform, \Web, \Mobile, \Homeschool, \Marketplace, \Media are created; iterations follow YYYY-Q<n>-S<m>; the work-item hierarchy (Epic → Feature → User Story → Task) is populated.

Scope &ZeroWidthSpace;

ADO project configuration:

Confirm area paths for Heritage Community Hub ADO project (\Platform, \Web, \Mobile, \Homeschool, \Marketplace, \Media).
Create iteration tree: YYYY-Q<n>-S<m> (2-week sprints, S1–S6 per quarter), starting with the current quarter.
Confirm work item types in use: Epic, Feature, User Story, Task, Bug.
Confirm custom fields as needed (story points, phase tag).
Set up ADO team and board columns: New → Active → Resolved → Closed.

GitHub intake mirror:

Document the GitHub Issues → ADO intake workflow.
Confirm or create the GitHub Actions / webhook that mirrors new Issues into ADO as intake items.
Confirm the ADO → GitHub status-comment feedback path.
Remove or archive any stale GitHub Milestones and GitHub Projects boards that were used for sprint tracking (those concerns now live in ADO).

Process documentation:

Document sprint planning process using YYYY-Q<n>-S<m> iteration naming.
Confirm Definition of Done for each ADO work item type (Epic / Feature / Story / Task / Bug).
Establish code review and PR standards (commits must include AB#<id>).
Document the closing criteria checklist from the work-items standard.

Templates and standards:

Sprint planning template aligned to ADO iteration naming (pmo/planning/sprint-planning-template.md).
Release planning template aligned to ADO (pmo/releases/release-planning-template.md).
Retrospective template aligned to ADO (pmo/retrospectives/retrospective-template.md).

Acceptance criteria &ZeroWidthSpace;

All ADO iteration slots for the current and next quarter exist and follow the YYYY-Q<n>-S<m> naming pattern.
Every new GitHub Issue opens an ADO intake item within one business day (manual or automated).
The sprint planning template uses YYYY-Q<n>-S<m> iteration labels, not sprint numbers or calendar dates.
The work-items standard checklist is reachable from the pmo/README.md quick-links section.
No sprint tracking occurs in GitHub Projects or GitHub Milestones; ADO Boards is the only sprint board.
All team members can create, update, and close ADO work items following the work-items.md standard.

Target users &ZeroWidthSpace;

Project lead — sprint planning, backlog grooming, velocity tracking.
Contributors — clear work assignments, AB# commit linking, ADO board updates.
Community leadership — project visibility through ADO queries and dashboards.

Priority and timing &ZeroWidthSpace;

ADO Priority: 2 (blocked Phase 1 sprint planning)
Phase: 0 — COMPLETE
ADO Epic: AB#3150 — Establish planning, docs, and repository foundation

Dependencies &ZeroWidthSpace;

ADO project "Heritage Community Hub" exists (dev.azure.com/hybridcloudsolutions). (Confirmed.)
GitHub repo exists (Heritage-Virginia/heritage-community-hub). (Confirmed.)
No other items block this epic.

Out of scope &ZeroWidthSpace;

CI/CD pipeline configuration (that is a Phase 1 infrastructure item).
ADR authoring (covered by the Phase 0 research/decisions epic).
Any feature development work.

"By wisdom a house is built, and through understanding it is established." — Proverbs 24:3