Portfolio Hub is a practical guide to running project portfolios: how to stand up a PMO, prioritize the work that matters, plan capacity you actually have, and govern programs so strategy turns into delivery. Frameworks and checklists, not buzzwords.
Read the handbookA PMO framework is the operating structure of a project management office: its mandate, functions, governance, delivery methodology, operating model, and metrics. This guide explains each component, the common PMO framework models, how a framework differs from a methodology, and how to build one that fits your organization.
A project intake form is a standard request form that captures the same core information from every new project idea so requests can be compared and prioritized fairly. This guide gives the exact fields to include, a filled sample form, how to build one in Excel, Word, or Google Forms, and how the form feeds your prioritization process.
A PMO methodology is the standardized, tailored approach to running projects that a PMO defines, publishes, and governs so every team delivers the same way. This guide explains what a PMO methodology includes, how it differs from a framework, how a PMO selects and tailors one, and how it gets adopted across the organization.
A project portfolio is a coordinated group of projects funded to deliver a shared strategic outcome. This guide gives five concrete examples, an IT portfolio, a new product portfolio, a transformation portfolio, a capital portfolio, and a marketing portfolio, each with its objective, its sample projects, and the way it gets prioritized and measured.
A resource management plan is the document that defines how projects and portfolios estimate, acquire, assign, develop, and release their resources. This guide covers what a resource management plan includes, the roles and responsibilities it records, how to build one step by step, and how it differs from a capacity plan.
The RICE scoring model ranks projects and features by reach, impact, confidence, and effort. Here is the formula, how to score each factor, a worked example, what counts as a good score, and how RICE compares to other prioritization frameworks.
WSJF (weighted shortest job first) sequences work by dividing cost of delay by job size, so short, urgent, high-value jobs go first. Here is the formula, how to score each input, a worked example, and how WSJF compares to RICE.
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.
Project portfolio management is the practice of choosing which projects to fund and which to stop, so that limited money and people go to the work that advances strategy. Here is what PPM means, what it involves, the benefits, and a worked example.
A steering committee is the small group of senior people who can fund, change, or stop a project. Here is what SteerCo means, who belongs on it, the decisions it owns, how often it should meet, and why most of them quietly turn into status meetings.
The project sponsor owns the business case, funds the work, and is accountable for the benefit. Here is the PMI definition, the responsibilities across the lifecycle, how the role differs from the project manager, and the four signs of a sponsor who has gone missing.
Project governance is the system of decision rights, forums, and escalation paths that controls a project. Here is what it means, the five components of a governance framework, a simple model you can copy, and where project governance ends and portfolio governance begins.
Lean portfolio management aligns strategy and execution by funding value streams instead of projects. Here are the three dimensions, lean budgets and the four guardrails, the portfolio Kanban, what changed with AI-Native SAFe in 2026, and how LPM really differs from traditional PPM.
Project management delivers a single piece of work well. Project portfolio management decides which work gets funded in the first place. Here is the difference in scope, ownership, funding, and success measures, plus where programs sit between the two.
A PMO earns its place by making decisions better, not by collecting status. Here are twelve PMO best practices that hold up in real organizations, a checklist you can audit yourself against, and the failure patterns that get project management offices disbanded.
Dependency mapping is how you make the links between work visible before they turn into slippage. Here is the five-step process, a template you can copy, a worked example, an honest look at the tooling, and how to run the mapping workshop that produces most of the value.
Twenty five worked examples of project dependencies, sorted by type: mandatory, discretionary, internal, external, and cross-project. Each one includes what it looks like in a plan and what to do about it once you have found it.
IT portfolio management covers three portfolios, not one: projects, applications, and infrastructure. Here is how the pieces fit, how the TIME model and run-grow-transform actually get used, and where IT PPM differs from ordinary project portfolio management.
There is no current Gartner Magic Quadrant for Project and Portfolio Management. The last one was published in May 2019, and the market was split into two reports: Adaptive Project Management and Reporting, and Strategic Portfolio Management. Here is what each one covers, which you should read, and how to build a shortlist from it.
A PMO analyst collects, cleans, and interprets project data across a portfolio, builds the reporting leadership relies on, and spots the project that is slipping before it turns red. Here is what the role involves day to day, a job description you can adapt, the skills that matter, and how it differs from a project manager and a business analyst.
Hiring a project manager is one of the hardest headcount cases to make, because the role produces no visible output of its own. This guide shows how to price the do-nothing option, which four alternatives to put in front of finance, a worked example with the arithmetic, and what to do when the answer is no.
A PMO manager leads the project management office: setting delivery standards, running portfolio governance and reporting, and making sure the projects an organization funds are the ones it should be running. Here is what the role actually involves, a practical job description, and how it differs from a project manager.
A project portfolio manager decides which projects an organization should fund, in what order, and against what capacity. Here is what the role does, how it differs from a project manager, a program manager, and a PMO manager, and what a credible job description looks like.
Resource leveling and resource smoothing both resolve over-allocation, but leveling can move the project end date while smoothing works only within available float and keeps the date fixed. This guide explains each technique, the effect on the critical path, a worked example, and when to use which.
A dependency matrix is a grid that maps which tasks or projects depend on which, with items listed down the rows and across the columns and a mark in each cell where a dependency exists. This guide covers what it is, how to build one, a worked example, and how it differs from a dependency log.
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.
A project portfolio dashboard is a single view of every active project showing status, budget, schedule, risk, and resource load, so leaders can spot which projects need a decision without reading a stack of status reports. This guide covers what to include, an example layout, the metrics that matter, and how to build one in Excel or Power BI.
Project prioritization criteria are the factors, such as strategic alignment, financial return, risk, and resource demand, that a portfolio scores every project against to decide what gets funded first. This guide gives you the standard criteria with examples, how to group and weight them, a worked scoring example, and the mistakes that quietly bias the ranking.
A portfolio review meeting is a recurring forum where leaders review the whole set of active projects and decide where capacity and funding should go next. This guide gives you the objectives, a time-boxed agenda, the roles, a reusable template, and the mistakes that turn the meeting into a status parade.
A capacity planning template is a spreadsheet that compares each person's available hours against the hours their assigned work requires, week by week, and flags anyone overallocated. This guide covers the exact columns to include, the formulas, a worked example with real numbers, and the point where the spreadsheet runs out of road.
A portfolio roadmap is a high-level timeline of every funded initiative in the portfolio, grouped by strategic theme, showing sequence, milestones, and dependencies over 12 to 18 months. This guide covers what belongs on one, a template you can rebuild in Excel or PowerPoint, three worked examples, and six steps to build a roadmap that survives contact with quarterly reality.
A project scoring model turns competing projects into comparable numbers so a portfolio can be ranked without collapsing into politics. This guide compares the four models most PMOs use, RICE, WSJF, weighted scoring, and cost of delay, with a side-by-side table, worked formulas, and a plain rule for choosing the one that fits your organization.
Benefits realization management is the practice of identifying, planning, tracking, and sustaining the business value a project or portfolio is meant to deliver. Here is the framework, the process steps, who owns the benefits, how to build a benefits realization plan, and how to measure whether value actually landed.
Project portfolio management KPIs measure whether the portfolio is on budget, on schedule, well-resourced, and aligned to strategy. Here are the metrics that matter across financial, delivery, resource, and strategic categories, plus how to choose a lean set and where leading and lagging KPIs fit.
An enterprise PMO (EPMO) governs projects and portfolios at the organizational level and reports to the executive team. Here is how an EPMO differs from a PMO, what it does, how to structure one, and when a company actually needs one.
A project management office gives an organization a single, consistent way to choose, run, and govern its projects. Here is what a PMO actually does, the three common types, and a practical path to standing one up.
When every project is "high priority," nothing is. This is a practical method for prioritizing a project portfolio: how to score work, weight your criteria, and force the tradeoffs that a real ranking requires.
Most portfolios are over-committed long before anyone notices, because demand is tracked and capacity is assumed. This guide covers how to plan resource capacity across a portfolio: demand versus supply, utilization, and protecting teams from silent overload.
Most portfolio governance fails by being either a rubber stamp or a bottleneck. This guide covers the cadences, stage gates, and decision rights that let a portfolio actually steer: review work, reallocate capacity, and stop projects that should stop.
Most portfolio budget overruns are not dramatic. They are a slow accumulation of approved purchase orders that nobody reconciled against the plan. Here is how to keep project spend visible and under control across a portfolio.
Project portfolios that lean on contractors and vendors carry a quiet risk: lapsed insurance and missing compliance documents. Here is how to keep vendor compliance and certificates of insurance current without it becoming a full-time job.
Statements of work, contracts, invoices, and status reports carry the real data of program delivery, but it stays locked in documents. Here is how to turn the paperwork of a project portfolio into data you can actually report on.
Most PMO reporting drowns executives in detail they did not ask for and hides the one thing they need: is the portfolio on track to deliver its outcomes? Here is how to build portfolio reporting and a status cadence leaders actually use.
A project intake process is the standard way an organization captures, reviews, and decides on new project requests. Here are the stages that work, the fields a good intake form needs, and how to connect intake to prioritization without drowning in bureaucracy.
The stage gate process breaks a project into phases separated by go/kill decision gates. Here are the five stages, what happens at each gate, who approves them, and how stage gate compares to agile.
Project portfolio management software gives a PMO one view of every project, its cost, and its people. Here is what a PPM tool is, how it works, the features that matter, how the main platforms compare, and how to choose one without buying capability you will never use.
What roles sit inside a project management office, and what is each one accountable for? A practical breakdown of PMO roles and responsibilities: the director, manager, analyst, and administrator, plus how the structure grows with portfolio size.
A PMO charter is the document that legitimizes a project management office and defines its mandate. Here is what a PMO charter should include, a section-by-section template outline, and examples of how to scope the authority that makes one work.
A PMO maturity model rates how capable a project management office is on a 1 to 5 scale. Here are the five levels explained, how a PMO maturity assessment works, and what it realistically takes to advance from one level to the next.
A reusable stage gate review template: the gate review agenda, the criteria checklist, the deliverables required at each gate, and the decision log that records go, kill, hold, or recycle. Copy the structure straight into your own gate process.
How to build a project prioritization matrix: choosing weighted criteria, picking a scoring scale, running the calculation, and reading the result. Includes a worked example and the difference between a scoring matrix and a 2x2 grid.