# PMO as Code

> A vendor-neutral standard for running a PMO from version-controlled,
> testable documents. Project status is a build artifact.

The reference implementation is docassert (https://docassert.com),
a CLI that validates business documents the way a test suite validates code.

## Start here

- [Home](https://pmoascode.com/): Project status is a build artifact: the thesis, the five defaults, and the live deployments.
- [Why PMO as Code](https://pmoascode.com/why/): Why the PowerPoint-Excel-SharePoint-email PMO fails: stale artifacts, self-reported RAG, unauditable approvals. Includes the author statement.
- [Case study: Refuge](https://pmoascode.com/case-study/): A real 14-section Word BRD converted to a gated, traceable, self-reporting project, failures included.
- [Runs on itself](https://pmoascode.com/self-governance/): The portfolio that builds PMO as Code is run as PMO as Code: live dashboards, governing documents, observable gates.

## Principles

- [Principles](https://pmoascode.com/principles/): The five defaults, and why the right-hand column is an exception rather than a ban.
- [Declarative sources of truth](https://pmoascode.com/principles/declarative/): Declare once in the documents; matrices, dashboards, and registries become build outputs.
- [Automation & audit](https://pmoascode.com/principles/automation/): Gates move from the default to the documented exception; policy becomes code.
- [Traceability](https://pmoascode.com/principles/traceability/): Value lives in typed links between thin documents; every test walks back to a business reason.
- [Derived status](https://pmoascode.com/principles/derived-status/): Nobody types a color: RAG is computed, every verdict names its causes, and reports can only lower it.
- [Composable definitions](https://pmoascode.com/principles/composable/): One grammar across twenty-one kinds, profiles as named bundles, a versioned spec at the boundary.

## The as-code family

- [The as-code family](https://pmoascode.com/as-code/): The shared pattern and the family tree: what infrastructure, documents, process, and policy each proved first.
- [Infrastructure as Code](https://pmoascode.com/as-code/infrastructure/): The ancestor: declared state, convergence, drift detection, and review for operations.
- [Documents as Code](https://pmoascode.com/as-code/documents/): From the docs-as-code movement to business documents, where validation must reach into structure.
- [Process as Code](https://pmoascode.com/as-code/process/): A described process drifts; an executed process holds. The PMO procedures that run today.
- [Policy as Code](https://pmoascode.com/as-code/policy/): Rules evaluated on every change: branch protection as the everyday policy engine, governance made binding.
- [Governance as Code](https://pmoascode.com/as-code/governance/): The system around the rules: decision rights, recorded approvals, oversight loops, exceptions with a trail.
- [Compliance as Code](https://pmoascode.com/as-code/compliance/): Machine-checked controls and evidence that accumulates as a by-product, so audits read the record.

## Reference approach

- [Artifact Crosswalk](https://pmoascode.com/crosswalk/): Traditional PMO artifacts and their as-code equivalents, row by row.
- [Core Concepts](https://pmoascode.com/concepts/): Documents with frontmatter and sections, project identity, linked items, two check tiers, twenty-one kinds.
- [Quickstart](https://pmoascode.com/quickstart/): Empty repo to merged validated document in eight steps with docassert.
- [Quickstart with Claude Code](https://pmoascode.com/quickstart-claude/): The same setup driven by Claude Code from one prompt, including Word-document conversion.
- [Guides](https://pmoascode.com/guides/): Task-oriented guides: converting documents, wiring CI, bridging execution to GitHub.
- [Reference](https://pmoascode.com/reference/): The twenty-one document kinds with their frontmatter, sections, items, and checks.
- [The standard](https://pmoascode.com/standard/): The normative spec: what it covers, how it versions, and the 73-case conformance suite that makes "implements PMO as Code" checkable.
- [Integrations](https://pmoascode.com/integrations/): GitHub Actions, badges, Pages dashboards, and the execution bridge.

## Profiles

- [Profiles](https://pmoascode.com/profiles/): Named document-set expectations: lean-startup, agile-delivery, regulated-industry, operations.
- [Adoption & Maturity](https://pmoascode.com/adoption/): Crawl, walk, run: one validated document to a fully traceable, consistency-enforced set.

## Compare

- [vs Traditional PPM](https://pmoascode.com/vs/): Row-by-row comparison with traditional PPM, including where traditional gates still belong.
- [FAQ](https://pmoascode.com/faq/): The questions every audience asks first, answered plainly.

## Optional

- [News](https://pmoascode.com/news/): Release-tied announcements, dated and factual, with an RSS feed at /rss.xml.
- [Press & share kit](https://pmoascode.com/press/): Press boilerplate, verified facts, quotable copy, real product images, and a shareable blurb.