CPEM key terms

The discipline of planning, organizing, directing, and controlling technical work and the people who perform it, blending engineering judgment with business and leadership skills.

Applying knowledge, skills, tools, and techniques to plan, schedule, resource, and control a temporary effort that delivers a defined product or result within constraints.

An interdisciplinary approach that defines stakeholder needs, translates them into requirements, and integrates hardware, software, and human elements into a verified, validated system across its life cycle.

A hierarchical decomposition of total project scope into manageable deliverables and work packages, forming the basis for estimating cost, scheduling activities, and assigning accountability.

A scheduling technique that identifies the longest sequence of dependent activities through a network, determining the shortest possible project duration and showing where delay directly extends completion.

The amount of time an activity can be delayed without delaying a successor or the project finish date; zero float indicates an activity on the critical path.

A bar chart displaying activities against a calendar timeline, showing durations, start and finish dates, dependencies, and progress, widely used for communicating schedules to stakeholders.

A significant, zero-duration point in a schedule marking completion of a key deliverable, phase gate, or decision, used to track progress and anchor reporting.

A performance measurement method comparing planned value, earned value, and actual cost to quantify schedule and cost variance and forecast final project outcomes.

The difference between earned value and actual cost; a negative value means work cost more than budgeted for the value delivered so far.

The difference between earned value and planned value, expressed in cost or time terms; a negative value indicates work is behind the planned schedule.

A forecast of the total cost of a project when finished, derived from actual costs to date plus an estimate of remaining work, often adjusted by cost performance.

The approved combination of project scope statement, work breakdown structure, and WBS dictionary, used to measure and control scope changes against an agreed reference.

A formally constituted group that reviews, evaluates, approves, defers, or rejects proposed changes to baselines, ensuring changes are assessed for impact before acceptance.

A disciplined process for identifying, controlling, recording, and auditing the status of configuration items such as specifications, drawings, software, and documents throughout a product's life.

The ability to link each requirement forward to design, implementation, and test evidence, and backward to its source, ensuring nothing is unbuilt and nothing unrequested is built.

Verification confirms a product was built correctly against specified requirements; validation confirms the correct product was built to meet stakeholder needs and intended use.

A formal review point between project phases where progress, risk, and business case are assessed before authorizing further funding and work.

A living document listing identified risks with their probability, impact, owner, response strategy, and status, used to prioritize and track risk treatment.

A planned action for a specific risk, such as avoiding, mitigating, transferring, or accepting it, chosen according to likelihood, consequence, and cost-effectiveness.

Identifying the people and groups affected by or able to influence a project, then assessing their interests, influence, and expectations to plan appropriate engagement.

A documented approach specifying who receives what information, in what format, at what frequency, and through which channels, aligned to stakeholder needs and project governance.

A responsibility assignment chart that labels each task as Responsible, Accountable, Consulted, or Informed, clarifying decision rights and eliminating ambiguity about ownership.

The arrangement of authority, reporting lines, and coordination mechanisms in an enterprise, commonly functional, projectized, or matrix, which shapes how engineering teams are managed.

The number of subordinates reporting directly to one manager; wide spans flatten hierarchies but demand more delegation, while narrow spans increase supervision layers.

A structure in which staff report to both a functional manager and a project or product manager, balancing technical depth against project focus but risking conflicting priorities.

Assigning responsibility and the necessary authority to a subordinate for a defined task while retaining accountability for the outcome, a core lever for manager leverage.

Adapting leadership style, from directing to coaching, supporting, and delegating, according to the competence and commitment of the individual or team for a given task.

The typical progression of a team through forming, storming, norming, performing, and adjourning, each requiring different managerial attention and support.

The process of addressing disagreement among individuals or groups using approaches such as collaborating, compromising, accommodating, avoiding, or competing, chosen to fit the situation.

A structured dialogue to reach agreement on resources, scope, schedule, contracts, or priorities, ideally seeking integrative outcomes that expand value rather than only splitting differences.

Frameworks explaining what drives effort, such as Maslow's hierarchy, Herzberg's hygiene and motivator factors, and expectancy theory linking effort, performance, and valued rewards.

Setting measurable goals, monitoring progress, giving feedback, and appraising results, then linking outcomes to development, recognition, and compensation decisions.

Professional obligations to hold public safety, health, and welfare paramount, act competently and honestly, avoid conflicts of interest, and report risks or violations appropriately.

The duty of engineers and managers to act within their competence, protect confidential information, disclose material facts, and accept accountability for decisions and their consequences.

Reporting an organization's illegal, unsafe, or unethical conduct to an internal or external authority, normally after internal channels fail and with attention to legal and professional duties.

Coordinated activities for setting quality policy and objectives, then planning, assuring, controlling, and continually improving processes and products to meet requirements and customer expectations.

Planned process-oriented activities, such as audits, standards, and procedure reviews, intended to prevent defects by confirming that work processes are capable and followed.

An ongoing, systematic effort to incrementally improve processes and products, often using plan-do-check-act cycles, root-cause analysis, and employee-driven problem solving.

A structured investigation, using tools such as fishbone diagrams and five-whys questioning, to find underlying causes of a problem rather than treating symptoms.