PECB ISO 21502 Lead Project Manager cheat sheet

ISO 21502 defines a project as a temporary undertaking initiated to achieve agreed objectives and deliver beneficial change or value; temporary means it has defined start and end points, not that it is short.

ISO 21502 is guidance, not a certification scheme: it describes what good project management looks like and is structured around integrated practices plus individual management practices; it does not prescribe a single methodology.

Project management is the coordinated application of methods, tools, techniques and competencies to achieve project objectives; project, programme and portfolio sit at different levels, with portfolio selecting and prioritizing, programme coordinating related projects, and project delivering outputs.

Key roles: project sponsor (accountable for the business case and benefits realization), project manager (day-to-day delivery within delegated authority), project team, and interested parties; the sponsor owns the project mandate and approves the project management plan.

A business case justifies the investment and is maintained across the life cycle; the project should be re-evaluated at decision points (gates) and terminated or re-scoped if benefits no longer justify cost and risk.

Governance provides direction, oversight and decision-making; principles include clear accountability, alignment with organizational strategy, stakeholder engagement, and tailoring to context (size, complexity, uncertainty, culture).

Project life cycle phases (concept, definition, delivery/implementation, closure) are distinct from management processes; phase boundaries are typical decision gates where authorization to proceed is granted.

Outputs, outcomes and benefits differ: outputs are deliverables produced, outcomes are the resulting changes in the operating environment, and benefits are measurable improvements realized after or during handover.

Success criteria are agreed at the start and may include scope, schedule, cost, quality, stakeholder satisfaction and benefits; success is judged against these agreed criteria, not only against the triple constraint.

ISO 21502 groups integrated practices as: project leadership, project management planning, managing the project life cycle, managing benefits, managing stakeholders, and managing project change and transformation; these cut across all delivery work.

The project management plan is the single integrating baseline; it consolidates scope, schedule, cost, quality, resource, risk, communication and procurement plans, and changes to any component flow through integrated change control.

Integrated change control decision rule: assess the change request for impact on scope, schedule, cost, quality, risk and benefits; approve, reject or defer by the authority defined in the plan; then update baselines and records.

Benefits management runs from identification through definition, planning, realization and sustainment; benefit owner accountability typically transfers to the business owner at handover, while the project tracks benefit enablers.

Stakeholder management: identify, analyse (interest, influence, attitude, impact), plan engagement, communicate, and monitor; engagement level is chosen per stakeholder, not uniformly.

Project leadership covers vision, direction, motivation, decision-making and ethics; the project manager integrates work across teams and interfaces, resolving conflicts at the lowest competent level before escalation.

Life-cycle management means tailoring phases, gates and reviews to uncertainty; predictive, iterative, incremental and agile approaches are all compatible with ISO 21502 guidance, chosen by risk profile and requirement stability.

Transformation management addresses the organizational change needed to adopt project outputs; without it, delivered outputs may not convert into outcomes and benefits.

Integration also means managing interfaces: between projects in a programme, with operations, with suppliers, and with governance bodies; interface risks are recorded and owned explicitly.

Scope management: define scope, create a work breakdown structure, verify deliverables, control scope; scope creep is uncontrolled change and must be routed through integrated change control.

Schedule management: define activities, sequence, estimate durations, develop and control the schedule; critical path is the longest dependent path and determines minimum project duration; float (slack) is the amount an activity can slip without delaying the project.

Cost management: estimate costs, determine budget, control costs; earned value formulas - CV = EV − AC, SV = EV − PV, CPI = EV/AC, SPI = EV/PV, EAC = BAC/CPI (when current performance persists).

Resource management: plan, acquire, develop and release team and physical resources; resource levelling resolves over-allocation and usually extends duration, whereas resource smoothing stays within float.

Risk management: identify, analyse (probability and impact), evaluate, treat (avoid, reduce, transfer, accept, exploit, enhance, share), and monitor; maintain a risk register with owners and response plans.

Quality management: plan quality, manage quality (assurance) and control quality; quality assurance is process-focused, quality control is deliverable-focused; acceptance criteria are agreed before work starts.

Communication management: plan who needs what information, when, in what format and channel; communication is planned per stakeholder group and includes reporting, escalation paths and records.

Procurement management: decide make-or-buy, select suppliers, administer contracts and close them; contract type (fixed price, cost-reimbursable, time and materials) allocates cost risk between buyer and seller.

Issue and change control: issues are current problems needing resolution, risks are uncertain future events; both are logged, owned, prioritized and tracked to closure, with lessons captured for organizational learning.