CPIT APM key terms

A temporary effort with a defined start and end, undertaken to produce a unique product, service, or result. It differs from ongoing operations because it is finite and creates something new.

The interdependent limits of scope, time, and cost that define what a project can deliver. Changing one constraint forces adjustment in the others, which is why trade-offs must be managed deliberately.

The sequence of phases a project passes through from start to finish, such as initiation, planning, execution, and closure. Phase gates typically control the transition from one stage to the next.

A formal review point at the end of a project phase where stakeholders decide whether to continue, revise, or terminate the work. It prevents problems from carrying forward unchecked.

An organizational unit that sets project standards, provides templates and tools, and oversees project performance across the organization. Its authority ranges from advisory support to direct control of projects.

The framework of decision rights, policies, and oversight that determines who approves changes, allocates resources, and resolves escalations on a project. It clarifies accountability beyond the project manager alone.

A document that formally authorizes a project, names the project manager, and states high-level objectives, scope boundaries, and constraints. It gives the manager authority to commit resources.

The justification for starting a project, describing the problem or opportunity, expected benefits, costs, and risks. It supports the sponsor's decision to invest and is revisited at phase gates.

A record of everyone affected by or interested in the project, including their roles, influence, interests, and communication needs. It drives engagement planning and is updated as the project evolves.

The process of identifying stakeholders and assessing their power, interest, and likely impact on the project. Results typically feed a grid that guides how closely each person is managed.

A document describing what the project will and will not deliver, including major deliverables and acceptance criteria. It anchors later planning and helps prevent unapproved expansion of work.

A hierarchical decomposition of the total project scope into manageable work packages. Each package can be estimated, assigned, and tracked, forming the basis for scheduling and cost control.

The lowest level of a work breakdown structure, small enough to estimate duration and cost reliably and to assign to a single owner. It is the unit from which activities are scheduled.

A scheduling technique that identifies the longest sequence of dependent activities through the network. Any delay on that path delays the whole project, so it receives the closest monitoring.

The amount of time an activity can be delayed without delaying the project finish or a successor activity. Activities with zero float sit on the critical path.

A relationship in which one activity must start or finish before another can proceed. Dependencies may be mandatory, discretionary, or driven by external parties, and each type carries different flexibility.

The approved combination of the scope statement, work breakdown structure, and work breakdown structure dictionary. It is the reference against which scope changes and completion are judged.

The approved version of the project schedule, including start and finish dates for activities and milestones. Actual progress is compared against it to detect variance.

The approved, time-phased budget used to measure and monitor project cost performance, excluding management reserve. Expenditures are tracked against it to calculate variances.

A log of identified risks with their probability, impact, owner, and planned response. It is reviewed regularly so that responses are triggered before risks become issues.

A planned action for handling an identified risk, such as avoiding, mitigating, transferring, or accepting it. Each response is assigned an owner and, where needed, a contingency reserve.

Money or time set aside for known risks that have been identified and analyzed. It is controlled by the project manager and included in the cost baseline.

A buffer held outside the cost baseline for unforeseen work within the approved project scope. Using it typically requires sponsor or management approval.

A document specifying who receives what information, in which format, and how often. It sets expectations for reporting and escalation so stakeholders are not surprised by developments.

A responsibility matrix that labels each task as Responsible, Accountable, Consulted, or Informed for named people. It exposes gaps and overlaps in role assignments before work begins.

A start-of-execution gathering where the team and key stakeholders confirm objectives, roles, schedule, and working agreements. It builds shared commitment before delivery work accelerates.

A document capturing a team's agreed norms, decision rules, and behavioral expectations. It reduces friction by making expectations explicit early in the project.

The process-oriented activity of auditing work processes to confirm they follow agreed standards. It aims to prevent defects rather than detect them after delivery.

The product-oriented activity of inspecting deliverables and measuring results against requirements. Defects found here are logged, corrected, and verified before acceptance.

The specific, testable conditions a deliverable must satisfy to be accepted by the customer or sponsor. They are agreed in advance and used to judge completion objectively.

The formal process of having the customer or sponsor confirm that completed deliverables meet the agreed acceptance criteria. Approval here authorizes payment or progression to the next phase.

Uncontrolled expansion of project scope through small, unapproved additions. It erodes schedule and budget because the extra work is absorbed without adjusting the baseline.

A group authorized to review, approve, reject, or defer change requests. It protects the baselines by ensuring changes are evaluated for impact before being accepted.

A formal proposal to modify scope, schedule, cost, or quality. It must be documented, assessed for impact, and decided through the change control process.

A technique that compares planned value, earned value, and actual cost to assess schedule and cost performance. It yields indices and variances that forecast likely outcomes.

The comparison of actual performance against the approved baseline to explain deviations in cost, schedule, or scope. Significant variances trigger corrective action or escalation.

A deliberate adjustment made to bring future project performance back in line with the plan. It addresses the cause of a variance rather than merely recording the deviation.

A record of problems that have already occurred and require resolution, with owners and target dates. Unlike risks, issues are certain and demand active management now.

Insights captured about what worked, what failed, and what should change on future projects. They are most valuable when collected throughout the project and stored where others can find them.

The final phase in which deliverables are handed over, contracts closed, resources released, and final reports issued. Formal closure confirms the project is complete and transfers ownership.

The achievement of the business outcomes the project was funded to produce, often measured after closure. It links project deliverables back to the original business case.

A checkpoint where decision-makers judge whether work should proceed based on readiness, risk, and value. A no-go outcome may pause, rescope, or cancel the effort.

The practice of raising an issue or decision to a higher authority when it exceeds the project manager's mandate or the team's ability to resolve it. Clear escalation paths prevent stalled decisions.