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 status meeting agenda decides whether the session produces decisions or just a round of updates. This covers a timeboxed weekly template with decisions first, three worked examples for delivery teams, sponsors and recovery projects, the pre-read rule, who to keep out of the room, and how to tell from blocker residence time whether the meeting is clearing work or only tracking it.
A project health check is an independent review of an in-flight project against evidence rather than opinion. This covers who is allowed to run one, the seven areas to score, the questions and the artifact each one needs, the trigger conditions that force an unscheduled check, and how findings become decisions instead of a filed document.
A project prioritization workshop is the working session where a group with real authority ranks candidate projects against agreed criteria and draws a funding line. This covers the pre-work data pack, a timeboxed agenda, who belongs in the room, how to break ties, the sponsor override protocol, and the decision record it has to produce.
A skills matrix maps every person on a team against every skill the work needs, scored on one shared scale, so you can see who can actually do what before you commit them to a project. This covers the template fields, a behaviorally anchored rating scale, a filled example, the single point of failure count, and how to turn the matrix into a resource plan.
A risk matrix scores each risk by how likely it is and how badly it would hurt, then multiplies the two into a rating that decides who owns it and how fast you respond. This covers the 5x5 grid, written probability and impact scales, response thresholds, and a filled project example.
Project budgeting turns a scope into an approved number you can be held to. This covers the three layers of a budget, the estimation methods and how accurate each one really is, contingency and management reserves, a worked example that adds up, and how to read a variance.
A matrix organization structure has people report to both a functional manager and a project manager. This guide covers the three matrix types, a scored diagnostic that tells you which one you actually run, a worked example, matrix org chart shapes, and the tie-break rule that keeps dual reporting from stalling.
A work breakdown structure decomposes the full scope of a project into deliverables and then into work packages small enough to estimate, assign, and track. This covers the WBS levels, the 100 percent rule, a filled example from an ERP finance rollout, the template field by field, the WBS dictionary, how to size a work package against your reporting cadence, and what changes when a PMO runs decomposition across a whole portfolio.
Stakeholder mapping places every person who can affect or is affected by a project onto a grid by power and interest, so you can decide who gets managed closely and who gets a monthly email. This covers the analysis matrix template field by field, a filled example, the engagement gap that generates real actions, and how a PMO maps stakeholders across a whole portfolio.
A communication plan states who needs project information, what they need, how often, through which channel, and who is accountable for sending it. This covers the template section by section, a filled example you can copy, how to set frequency, and how a PMO runs one standard plan across a whole portfolio.
A project kickoff meeting is the first working session of an approved project, where the sponsor confirms the objective and the team agrees how it will run. This covers a timed agenda, a section by section template, who to invite, the readiness test to pass first, and what the meeting has to produce.
A project charter is the document that formally authorizes a project and gives its manager the authority to spend budget and use people. This covers what goes in one, a section by section template, a worked example, who signs it, and how it fits the portfolio governance cycle.
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.