Delivery Portfolio — Personal Training OS¶
Joseph Schweizer · Project / Program / Delivery Manager · LinkedIn ↗
A working software product, 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.
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 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.
Names, dates, and personal details on this public site are genericized; the working system and its data remain private.