Every task, risk, issue, decision and baseline is a version-controlled file in your team's own GitHub repository, with the governance practice of a PMO on top. Any record can be summoned in seconds, so a quality audit becomes a lookup instead of a scramble. Built in a university capstone program, where the practice was graded as closely as the product.
Sign in with GitHub · Free for education · Every record stays in your repository
Not a screenshot of a database row — the actual file, in the actual repo, on the actual branch.
Sign in with GitHub, pick the repo. Git PMO writes the project record there as Markdown and YAML — nothing to migrate, export or lose.
Repo admin becomes Admin, write becomes Member, read becomes Advisor — read live from GitHub, never a user table you maintain. A repo someone can't see doesn't exist for them: a 404, not a 403.
Every risk raised, decision superseded and baseline re-cut is a commit with an author and a timestamp. So when a sponsor, an advisor or an auditor asks for the record, you summon the file — or the whole printable report — instead of reconstructing the story from memory.
Discord runs a full bot: slash commands, a status message that keeps itself current, due-date reminders, deep links straight to a task, and agent questions that mention the person accountable. Every message it sends is logged with the project.
Git PMO supports the practices described in PMI's PMBOK Guide. PMI certifies people, not products, so there is no badge here — only the artifacts the product writes into your repository.
Project charter, team charter, and one printable Summary Report consolidating status, deliverable coverage, risk exposure, cost variance and change history — an audit pack on demand.
Statement of Work with in- and out-of-scope declared separately, WBS and WBS dictionary, declared — not keyword-guessed — task-to-deliverable traceability, and an audit pass that flags any deliverable nothing serves.
Critical path with effort split from duration, dependencies and milestones, and a captured baseline drawn beneath every Gantt bar — so drift shows against the original, not the latest.
Currency, budget and rates by role or named member, then earned value: planned, earned and actual value, schedule and cost variance, SPI, CPI and a forecast at completion on an S-curve.
A3, PDCA, 8D and 8D+CAPA workbooks: stages completed explicitly, CAPA adding an approval gate and effectiveness-verification evidence before closure, and closure immutable until a recorded reopening.
Roster with per-platform identity, roles read live from repository permissions, per-task assignment, logged effort, and rate cards visible to the project creator only — while the aggregates reach every role.
Live status where the team already talks — a Discord bot and due-date reminders, with every message it sends logged — plus a communications management plan and the printable report.
Category, response strategy — avoid, mitigate, transfer, accept — inherent and residual probability by impact, triggers, threatened tasks, and mitigation carried by linked tasks, not a prose field. A risk with no mitigation task says so.
Roster with advisor-level read derived from the repository, a stakeholder register — influence, interest, and engagement now against what the project needs — and a stakeholder engagement plan.
Out of scope by decision and documented as excluded rather than half-built — as are benefits realization and organizational change.
The artifacts, fourteen in all
Statement of Work · Work Breakdown Structure · WBS Dictionary · Project Charter · Team Charter · Conformity and Exclusions · and eight management plans: scope, schedule, risk, quality, resource, communications, stakeholder engagement, change control. Each written in the app, stored as Markdown in your repository, each with its own revision history.
ISO 21502 is guidance, not a certification any software can hold — so no badge here either. Practice by practice, this is what Git PMO does, and where it stops.
| Practice | In Git PMO today |
|---|---|
| Project oversight | Accounts, programs and projects as a real portfolio layer, with a live panel showing each program admin's actual GitHub access on every project filed under them |
| Directing a project | Roles derived live from repository permissions, settings gated to the project creator, a conflict banner on any write against a stale revision |
| Planning | Description and Statement of Work drive the work breakdown structure — drafted by rules, or by AI on request — then committed as files and baselined |
| Scope management | In- and out-of-scope declared separately, deliverables traced to the tasks serving them, uncovered deliverables and orphaned tasks both surfaced |
| Resource management | Roster, per-task assignment, logged effort, rate cards by role or named member |
| Schedule management | Critical path, duration held separate from effort, baseline capture, variance against the original baseline |
| Cost management | Budget at completion, rate card, earned value, schedule and cost variance, SPI and CPI, forecast at completion |
| Risk management | Register with inherent and residual scoring, response strategy, triggers, threatened tasks, linked mitigation work |
| Issue management | Severity, owner, resolve-by date, affected tasks, an embedded five-whys chain, an append-only status history |
| Change control | Every governance write requires a stated reason; reason and superseded version stay in the revision history permanently |
| Quality management | A3, PDCA, 8D and 8D+CAPA — approval and effectiveness-verification gates before closure, closure immutable until explicitly reopened |
| Stakeholder engagement | A stakeholder register with an engagement assessment, the roster, and a stakeholder engagement plan |
| Communication management | Discord bot, due-date reminders, deep links to a task, and a log of every message sent |
| Reporting | One printable report, generated on demand: deliverable-by-deliverable status, risk and issue exposure, change history, schedule against baseline, cost and earned value |
| Information and documentation | Fourteen document types, version-controlled as Markdown in your own repository, each revision carrying its stated reason |
| Lessons learned | A retrospective workbook, and decisions superseded rather than deleted so the reasoning behind a reversal survives it |
| Benefits management · Organizational and societal change · Procurement | Coming Soon |
Practice names are paraphrased; no clause or section numbers are reproduced. Everything listed exists in the product today — roadmap items are marked as such.
| Git PMO | GitHub Projects | Zenhub | Jira | |
|---|---|---|---|---|
| Records stored in your own repository | Yes | No | No | No |
| Risk register with residual scoring | Yes | No | No | Add-on |
| 8D / CAPA problem-solving with gates | Yes | No | No | No |
| Decision log, ADR-style | Yes | No | No | No |
| Baseline & schedule variance on the record | Yes | No | No | Add-on |
| Critical path with effort/duration split | Yes | No | No | Add-on |
| Roles derived from repo permissions | Yes | Yes | Yes | No |
| Cost tracking & earned value (SPI/CPI) | Yes | No | No | Add-on |
| Printable governance report for a sponsor or auditor | Yes | No | No | Add-on |
| AI-drafted work breakdown from a plain-English scope | Yes | No | No | Add-on |
| Sprints, velocity & burndown charts | Coming Soon | Yes | Yes | Yes |
| Slash commands outside Discord | Coming Soon | No | No | Yes |
| Native mobile app | Coming Soon | Yes | No | Yes |
Competitor capabilities as assessed August 2026; "add-on" means a paid tier or marketplace app, not the base product. The last three rows are the ones we do not have yet — if your team runs on velocity charts today, Git PMO is not that tool.
Free for education. Tell us the course, program or lab and we'll send a key for the cohort. All you need is a GitHub repository per team — Git PMO writes the record into it.
Sign-in is GitHub OAuth. Git PMO reads only the repositories you point it at.