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 project risk register is a living document that lists each risk, its likelihood and impact, an owner, and a planned response. This guide covers the standard columns, the risk categories, how to build one, and a worked example.
Project portfolio risk management identifies, assesses, and responds to risk across an entire set of projects treated as one system. This guide covers the process, the main risk types, key risk indicators, and how it differs from single-project risk management.
Program management vs project management: a project delivers one output, a program coordinates related projects for a shared benefit. This guide compares the disciplines, the program manager and project manager roles, and where portfolio management fits above both.
The project portfolio management process in seven steps: identify, categorize, evaluate, select, prioritize, balance, and authorize projects, plus the PMI process groups and the review loop that keeps a portfolio aligned to strategy.
How to set up a PMO from scratch: an eight-step implementation roadmap, a setup checklist, and a phased 30/60/90-day plan for standing up a project management office that leadership actually backs.
A program management office (PgMO) coordinates a set of related projects toward one strategic outcome, managing dependencies, shared resources, and collective benefit. This guide covers what a PgMO does, how it differs from a PMO, its structure and roles, and how to set one up.
PMO functions are the core jobs the office owns: governance, portfolio management, resource management, performance monitoring, risk, standards, and reporting. This guide lists each function and shows how the PMO process runs them end to end.
PMO structure is the organizational design of the office: the three common models (centralized, decentralized, hub-and-spoke), where the PMO reports, and how to staff it by portfolio size. Here is how to choose the right one.
Project dependency management is the practice of identifying, mapping, and tracking the relationships between tasks and between projects so that work happens in a workable order. This guide covers the four dependency types, the logical relationship types (finish-to-start and its siblings), how to map dependencies, how to build a dependency matrix and a dependency log, and how a PMO manages interdependencies across a whole portfolio.
Resource allocation in project management is the process of assigning specific people, equipment, and budget to the tasks and projects that need them, then resolving the conflicts that assignment creates. This guide covers the main allocation methods, the difference between resource leveling and resource smoothing, how to spot and fix over-allocation, and a simple allocation matrix you can build this week.
A project business case is the document that justifies an investment before a project is approved, setting out the problem, the options considered, the costs and benefits, the risks, and a clear recommendation. This guide gives you the full section-by-section template, a worked example, and the difference between a business case and a project charter.
Project selection methods are the structured techniques a portfolio uses to decide which proposed projects to fund, grouped into benefit measurement methods (scoring models, cost-benefit analysis, NPV, payback period) and constrained optimization methods (linear and integer programming). This guide walks the full selection process step by step, explains each method with worked examples, and shows how selection differs from prioritization.