Portfolio prioritisation
Score initiatives against strategic objectives, value, risk, capacity. Visual prioritisation matrices. Quarterly reprioritisation cycles. Funded vs. unfunded backlog clearly separated.
Pillar · Projects
Portfolio governance for a CIO who reads three frameworks at once.
Most PMO tooling is a glorified Gantt chart. Argitron treats portfolios, programmes, projects, and tasks as the same first-class object family that incidents, changes, and controls are — so the dependencies and risks aggregate without manual re-keying.
PRINCE2 · PMBOK · agile · hybrid Stage gates RAID logs Capacity planning Benefits realisation
The PMO concerns Argitron addresses
Stage gates
Initiation / planning / execution / closure gates. Gate criteria configurable per project class. Go/no-go decision recorded with evidence: business case, risk register, security review, AI impact assessment if applicable.
RAID logs that actually roll up
Risks, Assumptions, Issues, Dependencies on every project. Risks promote to programme then to enterprise risk register. Issues escalate via SLA. Dependencies show on a portfolio-wide map.
Capacity planning
Skills supply vs. project demand. Resource conflicts visible at portfolio review. Scenarios: "what if we delay X by a quarter?" answered without a spreadsheet.
Dependency management
Cross-project dependencies, technical / architectural couplings, vendor and contract dependencies. Critical-path view across the portfolio.
Benefits realisation
Project closure isn't the end. Benefits tracked post go-live against the original business case. Lagging measures linked to the strategic objective.
The integration most PMO tools miss
Every IT project produces governance artefacts. Argitron stores them once.
Project → ITIL change calendar
Stage-gate "execute" produces the change records that flow through ITIL change enablement. CAB sees what's coming three sprints out.
Project → ISMS evidence
DPIAs, threat models, pen tests, training records, change approvals — collected once, attached to A.8.25–A.8.34 controls automatically.
Project → AIMS lifecycle
If the project introduces or changes an AI system, ISO 42001 A.6 lifecycle artefacts (impact assessment, data lineage, validation, deployment plan) are part of the stage-gate checklist.
Frameworks and methods
Argitron does not impose a methodology. PMBOK-style knowledge-area governance, PRINCE2 stages with defined roles and tolerances, Scrum / SAFe / Kanban for delivery, or a hybrid model where PRINCE2/PMBOK governs the portfolio and agile teams deliver — all supported on the same data model.
For regulated environments, gate criteria can be locked: no project ships to production without a risk register, an information classification, and (if applicable) an AI impact assessment.
One operating model for delivery and governance.
Project risks roll up. Project changes flow through ITIL. Project artefacts feed the auditor's bundle.