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.
Why it matters
Budgets are fixed and scrutinised. One visible flow of investment proposals stops money being committed through side conversations.
Workflow
Draws on
In the resource library
Ready-to-use resources in the DelPulse workspace (sign in to open them):
- Ways of working playbook: how work flows · Playbooks
- Ways of working playbook: principles, behaviours and team structure · Playbooks
- Estimation · Runbooks
- Light business case and requirements capture · Templates
- Product pack · Reporting packs
- New idea and request prioritisation · Guides
- Portfolio Kanban states and exit criteria · Guides
- Product dashboard: what to show · Guides
- Roles at a glance · Guides
- Working in Azure DevOps alongside DelPulse · Guides
- Portfolio Lead · Role guides
The rest of this page is for subscribers
Subscribe to read the other 4 sections of this page:
- How to run it
- Rules
- In the DelPulse workspace
- If you use Jira or Azure DevOps