Portfolio layer
The Portfolio layer is where an organisation decides what to fund. Its PMO assures every business case, keeps the gate calendar and reports health, so money follows value across the organisation’s projects and products.
When you need it
Switch it on when one organisation runs several products and projects competing for the same funding: the Organisation configuration and above.
What this layer decides
- Which projects and products receive funding, and how much
- Whether a business case is assured and approved
- Investment guardrails: the share kept for safety, regulatory and platform work
- Whether benefits delivered justify continued investment
Portfolio Kanban
Each organisation’s portfolio board. Strategic epics (six months or more, sized S, M or L) and investment proposals move through one visible flow, ordered by the DelPulse Value Index, so funding follows value. Epics break down into features on each product’s Product Kanban. No epic moves to Approved or Implementing until its feasibility is assessed and its funding approved at a Portfolio Review; epics under way are reviewed for value there, to persevere or stop early. They never sit on network or Portfolio of Networks boards.
Proposed states; confirm when the Portfolio configuration is first adopted.
Levers used here
The rest of this page is for subscribers
Subscribe to read the other 7 sections of this page:
- Roles
- Events
- Artifacts
- Inputs and outputs
- How it connects
- If you use Jira or Azure DevOps
- Getting started