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 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.
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.
AI in the PMO works best on the reading and reconciling work: drafting status, spotting risk signals across projects, triaging intake, and testing capacity scenarios. Here are the use cases that pay off first, what agentic AI actually changes, the tool categories, the data you need in place, and a 90 day pilot that will not embarrass you.
PMO KPIs measure the office itself rather than the projects it oversees: forecast accuracy, decision throughput, intake service levels, governance adoption, and the benefits that can be traced back to what the PMO did. Here are the metrics worth tracking, how to calculate them, examples by PMO type, and how to baseline them in year one.
A resource management plan template you can rebuild from scratch: the four tabs it needs, the resource register and demand grid columns, the SUMIFS and conditional formatting that flag over-allocation, a worked six-person example, and when Word beats Excel.
What a portfolio status report should contain, how the one page executive version differs from the full pack, a worked example table, the right cadence, and why the decisions section is the only part that changes anything.