Field notes on running project portfolios. Written for PMO leads, portfolio managers, and the program teams who turn a list of projects into delivered outcomes.
A portfolio Kanban visualizes the flow of large initiatives, or epics, from idea to done, with work-in-progress limits so a portfolio stops taking on more than it can finish. Here are the stages, how it works, and who manages it.
An impact effort matrix ranks work by impact against effort so you can spot quick wins fast. Here are the four quadrants, a step by step build, a worked example, scoring guidance, and when to use a weighted scoring model instead.
Program governance is the framework of boards, decision rights, and reviews that keeps a program aligned to its benefits. Here is how it differs from project and portfolio governance, what a program governance framework contains, who sits on the program board, and what it decides.
Project prioritization frameworks fall into three families: scoring models, categorical methods, and visual grids. Here is a side by side comparison of RICE, WSJF, weighted scoring, MoSCoW, and the impact effort matrix, plus a simple rule for choosing and combining them.
Strategic portfolio management (SPM) is how leadership turns strategy into funded, prioritized work and adjusts it as conditions change. Here is a plain definition, how SPM differs from project portfolio management, why Gartner split it into its own market, and who owns it.
Resource utilization is the share of available time your people actually spend on work. Here is the formula, what counts as a healthy rate, the difference between billable and productive utilization, and how utilization differs from capacity and allocation.
Continuous planning replaces the once a year budget with a rolling rhythm that revisits priorities and funding every quarter or month. Here is what it is, how it differs from annual and rolling wave planning, the process, and how it supports strategic portfolio management.
The MoSCoW method sorts work into must have, should have, could have, and won't have this time. Here is what each category means, the 60 percent rule, how to run the workshop, how it compares to weighted scoring, and where it breaks.
Cost of delay is the economic cost of finishing later rather than sooner. Here is the formula, the four delay profiles, how to calculate it, the CD3 shortcut, and how it drives portfolio sequencing.
Demand management is how a PMO captures, categorizes, assesses, and prioritizes every project request against real capacity. Here is the process, the types of demand, and how it differs from intake and from supply-chain demand planning.
A RAID log tracks risks, assumptions, issues and dependencies in one place. Here is what each letter means, why the A and the D are contested, the columns a working log needs, who owns it, and how a PMO rolls RAID up across a portfolio.
A RAID log template you can rebuild in a spreadsheet in ten minutes: the shared columns, the fields that differ per row type, worked example rows, and the four mistakes that turn a template into an archive nobody reads.
One account for the handbook and the template pack. Enter your email and we send a 6-digit code to confirm it.
No card needed. One email when something worth reading ships, and you can leave with one click.