This is the glossary for agile portfolio management: the working terms that carry real decisions, each defined in a sentence here and covered in full on its own page. Most arguments in a PMO are really disagreements about what one of these terms means.
The terms are grouped by the PPM4Agile practice that owns them: Align, Focus, Deliver, or Learn. A term belongs to the practice where its decision gets made, not to every practice that reads the result. Operational drivers come first, because they sit underneath all four.
What are operational drivers?
Operational drivers are the six things a portfolio operating system has to govern: workflow, meetings, people, metrics, artifacts, and the tools pipeline. A seventh piece sits beside them, OCM OS governance, which is the change management of the operating system itself. The six define what your operating system is. The seventh decides whether it becomes how the organization actually works.
What are the Align practice terms?
Align turns strategy into a ranked, funded, and protected set of work, with explicit decision rights and the limits that protect focus before anything gets planned. Seven terms belong to it.
- A measurable objective is a goal restated so that a number, a date, and an owner make it falsifiable.
- A weighted scoring rubric is a fixed set of criteria, each with a stated weight, applied to every candidate initiative so scores are comparable across sponsors.
- A stability window is the period during which the portfolio ranking is fixed, plus the explicit conditions that can reopen it early.
- Work-in-progress limits cap how many initiatives the portfolio may have active at once, set against real capacity rather than ambition.
- Decision rights name who can approve, defer, reprioritize, or cancel work at each level, and what each person can decide without escalating.
- Portfolio approval is the decision that an initiative may consume capacity.
- Portfolio commitment is the organization agreeing to protect that capacity for the length of the stability window.
What are the Focus practice terms?
Focus turns one approved initiative into a plan someone can execute, from discovery through validated capacity and a release plan. Six terms belong to it.
- Scope elaboration takes an approved initiative from a one-line business case to a described solution with boundaries, done with the people who will build and use it.
- MVP prioritization draws the line between what ships in the first release and what waits, based on which slice delivers the measurable objective.
- Capacity validation checks a plan against the people who actually exist, by name and availability, rather than against headcount on a spreadsheet.
- Team mapping assigns each workstream to a specific team with a named owner, so every piece of scope has one group accountable for it.
- A release plan sequences the mapped workstreams into releases with owned dependencies and a stated planning horizon.
- A forecast window states the range of dates a release is expected within, along with the confidence behind that range.
What are the Deliver practice terms?
Deliver manages the flow of work across teams once it is planned, through coordinated execution, quality gates, and the release decision. Five terms belong to it.
- A sprint goal system connects each team's sprint goal to the portfolio objective it serves, so team-level progress is legible at portfolio level.
- Dependency ownership assigns every cross-team dependency to a single named person responsible for resolving it, with a date.
- A coordination rhythm is the fixed schedule of cross-team conversations that resolve dependencies and surface blockers.
- Quality gates are the criteria a release must meet before it can proceed, defined before the work starts rather than negotiated at the end.
- Release readiness is the evidence-based decision that a release can go to production, usually run as a go or no-go review.
What are the Learn practice terms?
Learn measures what production actually returned and feeds the result into the next Align decision. Four terms belong to it.
- An operational dashboard shows the small set of indicators that tell you whether delivered work is behaving in production, with an owner and a defined response for each threshold.
- An improvement backlog is a ranked list of the process and product improvements surfaced during delivery, scheduled like any other portfolio work.
- A value realization review compares what an initiative actually delivered in production against the measurable objective it was approved on.
- Scale, sustain, or retire is the three-way decision that review has to end in: expand the investment, keep it running, or stop it and recover the capacity.
Which terms matter first?
Four of them: a weighted scoring rubric, a ranked list produced by it, a WIP limit, and a stability window with named decision rights behind it. Those four make the portfolio decidable, which is the precondition for everything else in this glossary. The rest of the vocabulary matters once decisions are actually being made and you need them to survive contact with the organization.
PPM4Agile terms vs SAFe LPM and traditional PPM
Most of these terms have a rough equivalent elsewhere, which is worth knowing when you are mapping an existing process onto this vocabulary. A weighted scoring rubric plays the role WSJF plays in SAFe and business case scoring plays in traditional PPM. A stability window does what a planning interval boundary does in SAFe, and what the annual plan was supposed to do before it got reopened every month. The mappings below are ours, not claims that either framework defines its own term this way.
| PPM4Agile term | Traditional PPM: closest equivalent | SAFe LPM: closest equivalent |
|---|---|---|
| Weighted scoring rubric | Business case scoring | WSJF (weighted shortest job first) |
| Stability window | Annual plan | Planning interval boundary |
| WIP limits | Resource leveling | Portfolio Kanban WIP limits |
| Value realization review | Benefits realization | Lean portfolio metrics |
| Operational drivers | Governance framework plus a benefits log | Lean governance |
The practical difference is scope rather than vocabulary. SAFe Lean Portfolio Management assumes agile release trains underneath it, and traditional PPM assumes an annual cycle. PPM4Agile assumes neither. The PPM4Agile and SAFe LPM comparison goes through that in detail, and portfolio Kanban covers the board that several of these terms sit on.
Common questions about agile portfolio terms
How many agile portfolio management terms do you need to start?
Four. A weighted scoring rubric, a ranked list, a WIP limit, and a stability window with named decision rights. Those four make the portfolio decidable. Everything else in this glossary is about making the resulting decisions survive.
What is the difference between a goal and a measurable objective?
A goal states a direction and an objective states a falsifiable result with a number, a date, and an owner. Goals are useful for communication and useless for prioritization, because two initiatives can both claim to serve the same goal and there is no way to compare them.
Who owns this vocabulary, the PMO or the business?
The PMO owns the mechanics: the rubric, the cadence, the artifacts, and whether the operational drivers are actually governed. The business owns the content of the decisions: the weights, the ranking, and the approvals. A PMO that owns both ends up defending priorities it did not set.
How is this different from doing team-level agile well?
Team-level agile decides how work gets done once it reaches a team. This vocabulary is about what reaches the team in the first place, and it is framework neutral: Scrum, Kanban, SAFe, and plain project delivery all keep working the way they work. A 60-minute Portfolio Clarity Session looks at your current portfolio and ends with what fits next, and a PPM4Agile implementation puts them in place phase by phase.
Sources
- GAO, Agile Assessment Guide (GAO-20-590G), September 2020, on governance, decision authority, and oversight practices in agile programs
- Scaled Agile, Lean Portfolio Management, for the SAFe terms named in the comparison table
- Scrum Guide, for the sprint goal definition