A portfolio kanban is one way to visualize the portfolio view: a single board that shows every initiative in an organization and the workflow state it is in, from proposed through to value reviewed. PPM4Agile does not require a board. What it requires is a portfolio view with named states that everyone reads the same way, and a board is the most common way to make that view visible.
What are the states?
These are not the stages in a project plan. They are the stages a piece of work passes through at the portfolio level, from the moment someone has an idea to the moment you know whether it was worth doing. Most portfolios need five to eight. With fewer than five you cannot tell where anything is. With more than eight nobody maintains them. A workable starting set:
| State | Question the state answers |
|---|---|
| Proposed | Has someone put this forward? |
| Evaluated | Has it been scored against the same criteria as everything else? |
| Approved | Has a decision been made, with the trade-off written down? |
| Planned | Is it sized to real capacity and sequenced? |
| In Delivery | Is a team actively building it? |
| Deployed | Is it in production? |
| Value Reviewed | Do we know whether it produced what we said it would? |
Test your own set against three questions. Can you point at any initiative right now and name its state without asking anyone? Is there exactly one way in, or can work appear in delivery without passing through approval? And does each transition require something to be true, rather than just requiring someone to say so? The third question is what separates a workflow from a status field.
Why do the limits matter?
A limit on how many initiatives may sit in delivery at once is what turns the view from a status display into a planning instrument. When the state is full, a new initiative cannot start until one finishes. That single rule forces the conversation annual planning avoids: which of these matters more, and what are we willing to not start? Those limits are set in the Align practice, where focus is protected before anything is planned. Focus is where each approved initiative is then planned against the capacity that actually exists.
Who owns the view?
The portfolio lead maintains it and the leadership group reviews it on the cadence the portfolio runs on: weekly to coordinate across teams, monthly or once per increment to protect portfolio intent. Team-level boards stay with the teams. The portfolio view only carries initiatives large enough to need a portfolio decision.
How do we set one up?
Build it in whatever tool the organization already runs, populate it with the current initiatives, agree what has to be true to leave each state, and set a first limit slightly below the current count. Building it with your own staff can be part of a PPM4Agile implementation.