The as-code family
The as-code family.
PMO as Code did not invent its pattern. It applies a discipline that infrastructure, documentation, process, and policy each adopted first, one practice at a time, over the last two decades.
The shared pattern.
Every member of the family makes the same move: take a practice that lived in hand-work and tribal knowledge, and express it as plain-text files in version control. Four things follow from that one move.
One source of truth
The files are authoritative. Anything derived from them is a build output, and anything that contradicts them is drift.
Review before change
Changes arrive as diffs, get reviewed as diffs, and merge with a named author and a timestamp.
Validation by machine
Automation checks every change against the rules before it lands, so the standard is enforced rather than encouraged.
History for free
Who changed what, when, and why stops being a records-management project. It is the commit log.
The family.
The ancestor. Servers stopped being hand-built and became declared state that tooling converges toward. It proved the whole posture.
Technical writers moved documentation into Git and CI. Business documents raise the stakes: they carry commitments, so validation has to reach into structure.
A process written in a wiki describes; a process written as automation executes. The gap between the two is where procedures rot.
Rules that machines evaluate against every change. Branch protection is the version most teams already run without naming it.
The system around the rules: decision rights, recorded approvals, oversight loops, and exceptions with a trail.
Controls checked by machines, evidence accumulating as a by-product, audits that read the record instead of reconstructing it.
GitOps deserves a mention alongside these: the practice of keeping a system converged with its declared sources through automated reconciliation loops. PMO as Code leans on it directly, since the delivery boards are reconciled against the documents the same way a cluster is reconciled against its manifests.
Where PMO as Code sits.
PMO as Code is the family pattern applied to project and portfolio management. The documents are the declared state, the audit is the validation, the merge is the recorded decision, and status is derived rather than reported. Each member of the family contributed a proven piece, and the contribution pages that follow name exactly which piece came from where.