7.2. Terms N–Z
Operations — Ongoing, repetitive work that sustains the business. (1-1)
Organizational process asset (OPA) — An existing process, template, or knowledge base the organization can draw on. (4-1)
Planned Value (PV) — The budgeted cost of work scheduled to be complete by a given point. (5-3)
PMI Code of Ethics and Professional Conduct — PMI's ethical standard, built on responsibility, respect, fairness, and honesty. (2-1-2)
Portfolio — A collection of projects, programs, and other work grouped to achieve a strategic objective. (1-1)
Predictive approach — A delivery approach that plans in detail up front and manages change through formal control. (1-2, 5-1)
Process manager — Owns day-to-day execution of a business process. (3-1)
Process owner — Owns a business process's overall design and outcomes. (3-1)
Product backlog — See Backlog.
Product manager — Owns a product's strategy and lifecycle. (3-1)
Product owner — Owns backlog prioritization for value delivery. (3-1)
Product roadmap — A strategic view of feature/capability rollout across releases. (3-4)
Program — A group of related projects and program activities managed together for benefits not available from managing them individually. (1-1)
Project — A temporary endeavor undertaken to create a unique product, service, or result. (1-1)
Project charter — The document formally authorizing a project's initiation. (5-1)
Project management plan — The document describing how the project itself will be managed. (2-2-1)
Quality management plan — The plan establishing the standards a deliverable must meet. (5-2-2)
Requirements traceability matrix (RTM) — Links each requirement to its source, design element, and verifying test. (3-3)
Risk — An uncertain future event or condition that may affect the project. (2-1-2)
Risk register — A living log of identified risks, their assessment, and planned responses. (2-2-2)
SAFe (Scaled Agile Framework) — An adaptive framework coordinating multiple teams on a shared, interdependent product. (4-4)
Schedule Variance (SV) — EV − PV; measures whether a project is ahead of or behind schedule. (5-2-1, 5-3)
Scrum — An adaptive framework using fixed-length sprints, defined roles, and set ceremonies. (4-4)
Scrum Master — A Scrum role responsible for removing impediments and upholding the framework's practices. (4-4)
Stakeholder register — A living log identifying stakeholders and their interest, influence, and expectations. (2-2-2)
Use case — A description of how actors interact with a system through a defined set of steps. (3-3)
User story — A requirement framed from the end user's perspective, sized for a backlog. (3-3)
Vehicle for change — The idea that a project exists to produce an intended organizational benefit, not just a deliverable. (1-2, 2-1-2)
Work breakdown structure (WBS) — A deliverable-oriented hierarchical decomposition of total project scope. (5-2-1)
Work package — The smallest unit of a WBS, small enough to reliably estimate and assign. (5-2-1)
Work-in-progress (WIP) limit — A cap on how many items can be actively in progress at once, central to Kanban. (4-4)
