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.
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.
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 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 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.
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.
Scope creep is the gradual, uncontrolled expansion of a project beyond its agreed boundary, added a request at a time without matching increases in time, budget or people. This covers the causes, real examples, the warning signs, and the controls that actually work.
A RACI matrix maps every significant activity against the people involved and marks each one Responsible, Accountable, Consulted or Informed. This covers what the letters mean, how to build the chart, a worked portfolio governance example, and the rules that stop it turning into wallpaper.
A change control process is the defined route a proposed change takes from request through impact assessment to an approval decision and an updated baseline. This covers the five steps, the request form, the change control board, approval thresholds, and the log.
A post implementation review is the structured look back at a project after it has gone live, checking whether the promised benefits actually arrived. This covers when to run a PIR, who belongs in the room, the questions to ask, and what goes in the report.
SteerCo is the common workplace abbreviation for steering committee. This covers what SteerCo stands for, what a SteerCo meeting and a SteerCo call actually are, who sits in the room, the decisions the group owns, and the spellings and variants you will run into.
A PMO job description defines what the role owns, decides, and reports on inside the project management office. This guide covers the duties and responsibilities to include, the requirements worth asking for, ready-to-adapt outlines for PMO analyst, manager, and director roles, and how a job description differs from a responsibilities matrix.