GUIDE 2026
How to manage an agile portfolio: The operating system I’d use
Agile portfolio management fails when every initiative is "P0." I'd run a portfolio like a constrained investment book tied to capacity, not ambition slides.
Operating pieces I'd want
- A small set of themes tied to measurable outcomes
- Explicit WIP limits across initiatives, not only stories
- Cadence for intake, kill/continue, and capacity reality
- Visibility of dependencies without a 40-tab RAID shrine
- Funding language that can say "not now" without drama
Conversations I'd force quarterly
| Question | Why it matters |
|---|---|
| What do we stop? | Creates capacity |
| What did we learn? | Prevents zombie programs |
| Where is demand lying? | Rebalances investment |
| What risks are compounding? | Surfaces debt and platform drag |
I'd keep artifacts lightweight enough that leaders actually read them. Portfolio agility is saying no with receipts.
This is leadership + systems work—a Technical PM Certification helps bridge strategy and delivery. Stay sharp with the newsletter.
