IT Portfolio Management

The PMO governs how projects are run. The EPMO governs which projects should exist. Here's the structural difference and the signals that tell you which one your organization actually needs.

A capacity vs demand gap analysis compares what IT is being asked to deliver against what it can actually deliver. Here's how to calculate the gap and use it to make real portfolio decisions.

FTE planning converts headcount into usable capacity numbers. Here's how IT project managers and PMOs calculate FTE demand and aggregate it across a portfolio.

Most portfolio reviews are status updates in disguise. Here's the agenda, the pre-work, the right attendees, and the failure modes that keep the meeting from producing real decisions.

Portfolio rebalancing is the deliberate process of adjusting which projects are in flight based on new information. Here are the six triggers and how to run one without a political firestorm.

A project scoring model moves IT approval decisions from gut feel to a documented, defensible process. Here are the five criteria that work in practice with worked examples.

What happens between someone submitting a project request and IT starting the work? Here's how to build an intake process that creates accountability and prevents invisible work.

Over-allocation rarely gets named directly. Instead it shows up as slipped deadlines, quality problems, and team burnout. Here are the visible and hidden signals.

Sprint teams plan in two-week cycles. Portfolio managers plan in quarters. The gap between them causes chronic mismatches. Here's how to bridge it.

Top-down sets budget targets. Bottom-up rolls up project demand. Organizations that use only one end up with a capacity plan that doesn't reflect reality.