Delivery Portfolio: Personal Training OS

Joseph Schweizer · Project / Program / Delivery Manager · LinkedIn ↗

Why this is a personal project, not a work sample

I cannot show you my professional artifacts. That work is controlled. I cannot host the documentation, I cannot publish the analysis, and some of it I cannot discuss at all. So I built something I could put on the table, and I held it to the same gates a regulated delivery org would enforce. Every artifact here is inspectable.

A working system (a Notion-based training platform), delivered end-to-end with the full delivery lifecycle and its governing artifacts. This site is the delivery record: charter → planning → design → verification → release, run as a deliberate demonstration of project/program/delivery management practice.

What it is in one line: I specified, planned, governed, verified, and shipped a real system (v1.0), directing an AI-implemented build through a tailored hybrid stage-gate and agile process, and produced the artifacts a PMO, healthcare, or defense delivery org would expect at each gate.

Published baseline

This site is a frozen snapshot of the project's closure baseline (the project is formally closed at G7; content last synchronized from the private delivery record on 2026-07-17, including the post-release increments and their formal verification). The private record remains the source of truth for history. Controlled-document practice: the published artifact states the version it reflects, and diverges from its source only by decision, not by drift. See ADR-0008.

Why it's here

Most PM candidates can describe a lifecycle. This is a live, inspectable instance of one: a real product with a baselined requirements set, requirement→design→test traceability, a RAID log, a RACI, MoSCoW scope control, ADRs, an IEEE-829 V&V summary, and a governed release, all under version control with CI gates. Every artifact below is the real thing, lightly genericized for privacy.

Competencies demonstrated

The role screens for…	Shown in
Delivery governance / stage-gates	Delivery Process · gate sign-offs throughout
Initiation & stakeholder management	Project Charter · Stakeholder Register & RACI
Scope & prioritization	MoSCoW Prioritization (with re-baselining) · Roadmap
Risk / issue / decision control	RAID Log · Architecture Decision Records
Requirements engineering & traceability	Requirements & Traceability site ↗ (EARS + StrictDoc, 101/101 covered)
Verification & validation	Test Plan · V&V Summary (IEEE-829)
Release & operations	Release Notes · Go-Live Checklist · Backup & Recovery Runbook

How I run a program

The same shape every time, whatever the domain: a gated lifecycle with governance running continuously underneath it, not bolted on at the end. RAID reviews, stakeholder touchpoints, and repeatable playbooks feed every phase and every gate decision.

flowchart LR
  A["Intake and charter"] --> B["Planning and baseline"]
  B --> C["Execution"]
  C --> G{"Gate review"}
  G -->|approved| H["Release and handoff"]
  G -->|rework| C
  subgraph GOV["Continuous governance"]
    direction LR
    R["RAID reviews"] ~~~ S["Stakeholder touchpoints"] ~~~ P["Playbooks and change control"]
  end
  GOV -.-> B
  GOV -.-> C
  GOV -.-> G

Every box above maps to a real artifact on this site: the charter, the RAID log, the stakeholder register and RACI, the gate sign-offs in the delivery process, and the release checklist.

How it was delivered (the differentiator)

The whole thing is docs-as-code: requirements, design, and delivery artifacts live in git, reviewed via pull request, and gated by CI. I directed the delivery and governance decisions; AI handled the implementation, held to the same gates and review discipline a technical program would enforce. StrictDoc enforces that every requirement has design coverage, a coverage-gated test suite runs, and security scanning blocks on findings before merge.

---

Third-party names, dates, and personal details on this public site are genericized (the author byline is deliberate); the working system and its data remain private.