Kanban at the team level limits work in progress for individual tasks. Portfolio Kanban does the same thing one level up — for initiatives, programs, and large features flowing across multiple teams.
The board columns represent stages: Idea → Analysis → Approved → In Delivery → Done. Each card is an initiative, not a story. WIP limits apply at the portfolio level: if you have eight initiatives in "In Delivery" and the organization can realistically focus on three, the other five are creating the illusion of progress while actually slowing everything down.
"Portfolio Kanban is described in the Agile Extension at the Strategy Horizon."
This is where portfolio Kanban connects to BA work — it's not just a delivery tool. It's a strategy tool. The BA helps define what "ready to enter delivery" means at the portfolio level, ensures initiatives are analyzed before they're approved, and identifies dependencies between initiatives.
The value: limiting simultaneous commitments shortens lead times for everything in the system. Counterintuitive but real — starting fewer things means finishing more things.
I've seen the opposite pattern frequently: organizations approve fifteen initiatives at the beginning of the year and then wonder why nothing ships. Portfolio Kanban makes the capacity constraint visible and forces the conversation about what actually matters.
For PSPO candidates, portfolio Kanban connects product strategy (what initiatives to pursue) with delivery capacity (how much can flow through the system at any given time).
Exam tip: WIP limits at portfolio level are not about effort limits — they're about commitment limits. The constraint protects focus and reduces the coordination overhead that kills large organizations.