ITIL 4 PM PDF key terms

A temporary structure of resources and activities created to deliver one or more defined outputs, used to move an organization from a current state to a desired future state.

The coordinated set of practices and decisions used to plan, organize, direct, and control a project so that its agreed outputs are delivered within constraints accepted by stakeholders.

A tangible or intangible deliverable produced by a project or activity, such as a document, application, or service component, that is intended to create value for stakeholders.

A result or change in state experienced by stakeholders because of one or more outputs; it describes the effect achieved, not the deliverable itself, and is often measured after the project closes.

The perceived benefit, usefulness, or importance of something to a stakeholder, judged by what it enables and costs, and central to how projects are justified and evaluated.

The measurable gains realized when project outputs and outcomes are used; benefits are tracked to confirm that the investment produced the improvement it was intended to produce.

A documented justification for an initiative that sets out expected value, costs, risks, and constraints, and supports decisions to start, continue, change, or stop the work.

The agreed boundary of what a project will and will not deliver, including the products, services, and activities included; scope changes usually require assessment of impact on cost and schedule.

Limits within which a project must operate, such as budget, deadline, resource availability, regulation, or quality thresholds, which shape planning decisions and trade-offs.

A person or group with an interest in, influence over, or dependency on a project or its outcomes, whose needs and expectations must be understood and managed.

The senior role that provides direction, resources, and authority for a project, owns the business justification, and removes obstacles that the project team cannot resolve itself.

The role responsible for coordinating the project team and its work, managing plans, risks, and stakeholder expectations, and ensuring the agreed outputs are delivered and value is enabled.

The group of people, often drawn from multiple disciplines or suppliers, who perform the work of the project and collaborate to deliver outputs and outcomes.

The documented allocation of authority and duties among participants, clarifying who decides, who performs work, and who is consulted or informed, to reduce ambiguity and conflict.

A responsibility mapping technique that labels each activity as Responsible, Accountable, Consulted, or Informed, making accountability explicit and exposing gaps or overlaps in role assignment.

The means by which an organization directs and controls its projects, including decision rights, oversight bodies, policies, and reporting that keep work aligned with strategy and risk appetite.

A decision-making group, typically including senior sponsor and user representation, that provides oversight, approves key plans and changes, and resolves escalated issues for a project.

The shared norms, behaviors, and working habits of a project team, including psychological safety, collaboration, and openness, which strongly influence how effectively work flows.

The deliberate exchange of information with stakeholders, planned to ensure the right people receive accurate, timely, and appropriately detailed messages about progress, decisions, and change.

A set of organizational resources designed for performing work or accomplishing an objective; each practice combines people, processes, information, technology, partners, and value streams.

In ITIL terms, the practice concerned with ensuring projects are delivered successfully within constraints by coordinating resources, plans, risks, and stakeholder expectations.

The practice of identifying, assessing, treating, and monitoring uncertainties that could affect objectives, keeping exposure within agreed tolerances and informing project decisions.

A problem or situation that has already happened and requires action, distinct from a risk, which is uncertain; issues are logged, prioritized, and resolved or escalated.

The practice of ensuring changes to products and services are assessed, authorized, scheduled, and implemented in a controlled way, with risks and impacts understood before approval.

The recurring practice of identifying and acting on opportunities to improve products, services, and ways of working, using feedback, measurement, and structured improvement methods.

The practice of maintaining and sharing accurate information and know-how so that decisions and work are based on reliable knowledge rather than individual memory.

The practice of ensuring accurate information about configuration items and their relationships is available when and where needed, supporting change, incident, and project decisions.

A configuration management database holding records of configuration items and their relationships, used to assess the impact of changes and to understand dependencies in the environment.

A series of steps an organization uses to create and deliver products or services to a consumer, mapped to show where value is added, where delays occur, and where work hands off.

A technique for visualizing the flow of work through a value stream, identifying delays, bottlenecks, and waste, and designing a better sequence of activities.

A set of interrelated or interacting activities that transforms inputs into outputs; processes define what is done, by which roles, with which controls, and how results are measured.

The defined sequence and states through which a unit of work moves, including queues, approvals, and handoffs, often visualized on a board to make progress and blockers visible.

A visual method for managing flow that limits work in progress, makes bottlenecks visible, and helps teams pull work at a sustainable pace rather than pushing it into overload.

A way of working that favors short iterations, frequent feedback, and adaptive planning, enabling teams to respond to changing requirements and deliver value incrementally.

A fixed, short period of work in which a team plans, delivers, and reviews a small increment of value, then uses the feedback to adjust the next period.

The smallest version of a product that delivers enough value to be usable and to generate learning, allowing teams to validate assumptions before investing further.

The practice of understanding and managing the information used by an organization, ensuring it is accurate, available, secure, and fit for the decisions it supports.

The degree to which information is complete, accurate, consistent, and timely enough for its intended use; poor quality undermines reporting, decisions, and project control.

Quantitative measures used to track performance, progress, and value; good metrics are relevant, actionable, and balanced so they inform decisions rather than distort behavior.

An external organization that provides products, services, or resources to a project, whose performance, dependencies, and risks must be managed as part of delivery.

The practice of managing relationships and performance with suppliers to ensure they deliver agreed value, meet obligations, and integrate smoothly with internal work.

A formal agreement defining what a supplier will provide, the terms of payment and performance, and the remedies available if obligations are not met.

The coordination of multiple internal and external providers so that their combined work delivers a seamless service or project outcome without gaps at the boundaries.

An external organization with which a closer, longer-term relationship is maintained, often sharing risk and knowledge, in contrast to a purely transactional supplier arrangement.

The practice of identifying, understanding, and involving stakeholders so that their needs, concerns, and contributions are addressed and support for the work is built.