Portfolio WIP: It's Not About Limits
Every time I introduce a portfolio Kanban, somebody asks about WIP limits. At the portfolio level my answer is usually: don't limit WIP: at least not that way.
Every time I introduce a portfolio Kanban, somebody asks about WIP limits. At the portfolio level my answer is usually: don't limit WIP: at least not that way.
I revisited my 2011 talk on scaling Kanban from team to program and portfolio. What still holds up, and what I would change today.
When you are running specs through coding agents, the spec is the work in progress. WIP limits are the valve that keeps agentic throughput from piling up in front of the humans who still have to review it.
How to get clear on goals before rushing into OKRs or any goal-setting system: the exercise that separates directional intent from measurable outcomes.
Treating OKRs as a Kanban system: visualizing strategic work, limiting WIP at the leadership level, and using Kanban cadences to review and adapt priorities.
Sustainable pace is a core agile principle that often gets sacrificed in enterprise implementations. How Scrum, SAFe, and Kanban each approach the problem.