ISO-21502-Lead-Project-Manager PECB ISO 21502 Lead Project Manager Exam Questions and Answers

The correct answer is C. Both A and B . A project plan should include, among other elements, the project scope, risks, assumptions, and constraints. The project plan is the integrated reference document that describes how the project will be executed, monitored, controlled, and closed. Scope defines what the project is expected to deliver and the boundaries of the work. Risks identify uncertain events or conditions that could affect project objectives. Assumptions describe factors considered true for planning purposes, even though they may later require validation. Constraints define limiting conditions, such as fixed deadlines, budget ceilings, regulatory obligations, resource limits, contractual requirements, or technology restrictions. These elements are interconnected: assumptions and constraints influence scope, risk exposure, schedule, cost, quality, and resource planning. A project plan that includes only scope and risks would omit the planning logic behind them. A plan that includes only assumptions and constraints would not adequately define the deliverables or uncertainty profile. Therefore, both sets of information are necessary for sound integrated project management.

Reference topics: project plan, scope, risks, assumptions, constraints, integrated planning.

The correct answer is B . Lessons learned should be captured, compiled, formalized, and stored. Lessons learned are a structured form of organizational knowledge that helps current and future projects improve performance and avoid repeated mistakes. They should capture what was planned, what actually happened, why variances occurred, what worked well, what failed, what actions were effective, and what recommendations should be reused or avoided. Option A is incorrect because lessons learned should not describe only what happened; they should also compare actual performance against the plan and examine causes, effects, and improvement opportunities. Option C is also incorrect because lessons should not be used only after all project activities are complete. They can and should be captured throughout the project so that the team can apply learning immediately where useful. At closure, they are consolidated and stored for future use. PMBOK recognizes a lessons learned register as a project document that records knowledge gained during a project and supports future performance improvement. The uploaded question set identifies capture, compilation, formalization, and storage as the correct statement.

Reference topics: lessons learned, knowledge management, formalization, storage, continuous improvement, project closure.

The correct answer is A . Managing delivery is concerned with defining the required outputs and outcomes, then planning and implementing their delivery so that the project can achieve its intended outcomes and enable benefits realization. Delivery management bridges the gap between project planning and the creation of usable outputs. It ensures that the project’s scope, outputs, acceptance expectations, work packages, resources, dependencies, quality needs, and implementation activities are organized to produce what the project was established to deliver. Option B relates more closely to closure and post-delivery transition, because demobilizing remaining resources and facilities occurs when project work is being concluded. Option C describes continued business justification, governance review, or project control, where the organization verifies whether the project remains relevant, acceptable, and aligned with stakeholder expectations and risk tolerance. Managing delivery is therefore more operational and output-focused: it turns the approved plan and requirements into controlled execution. It also supports benefits indirectly by ensuring that outputs are fit for use and capable of producing intended outcomes. The source question set gives option A as the complete purpose statement for managing delivery.

Reference topics: managing delivery, outputs, outcomes, benefits realization, implementation planning, delivery control.

The correct answer is B. Performing organization or customer . Acceptance of quality standards and product quality requirements belongs to the party that has authority over what the product, service, or result must satisfy. Depending on the project context, this may be the customer, the performing organization, the sponsoring organization, or another authorized acceptance body. The project manager is responsible for planning, managing, and controlling the project so that the agreed quality requirements are met, but the project manager does not unilaterally determine acceptance unless specifically delegated that authority. The work package leader manages assigned work and supports compliance within a defined area, but does not normally own final acceptance of product quality requirements. Quality standards and requirements must be accepted by the appropriate business or customer authority because they define whether the delivered output is fit for purpose, compliant, and acceptable for use. In practical terms, the performing organization or customer confirms whether the quality expectations reflect organizational needs, customer requirements, contractual obligations, and acceptance criteria.

Reference topics: quality standards, product quality requirements, customer acceptance, performing organization, quality planning.

The correct answer is B. The 8/80 rule . This rule is used when decomposing work into work packages or activities. It states that a work package should generally require no less than 8 hours and no more than 80 hours of effort. In practical terms, this means the work package should be large enough to avoid excessive administrative fragmentation, but small enough to be estimated, assigned, monitored, and controlled effectively. In Allison’s case, she ensured that each work package took longer than 8 hours but less than 80 hours and could be completed within 1 to 10 working days. That is a direct application of the 8/80 rule. The 1/10 rule is related but expressed differently: work packages should usually represent between 1% and 10% of the project duration or effort, depending on the planning method. The reporting period rule links work package size to the frequency of performance reporting. The scenario specifically refers to the 8-hour and 80-hour thresholds, so the correct rule is unmistakably the 8/80 rule.

Reference topics: work breakdown structure, work package sizing, 8/80 rule, activity planning, scope decomposition.

The correct answer is A . To avoid repeating mistakes from previous projects, the organization and project team should utilize lessons learned from previous, relevant projects. Lessons learned capture practical knowledge about what went well, what went wrong, what assumptions failed, what risks occurred, which controls were effective, which stakeholder issues emerged, and what should be improved in future projects. Applying lessons learned strengthens planning, governance, risk management, estimation, stakeholder engagement, procurement, quality control, and delivery execution. Hiring subject-matter experts may be useful in some circumstances, especially where specialist knowledge is required, but it does not directly replace the value of organizational learning. Experts can still repeat past mistakes if the project does not actively review and apply prior lessons. The duplicate subject-matter expert options do not change the correct answer because the principle being tested is knowledge reuse. ISO 21502-aligned practice treats lessons learned as an important input for improving current and future project performance. The uploaded source question specifically asks what should be considered to avoid repetition of previous mistakes and identifies lessons learned from previous, relevant projects as the proper response.

Reference topics: lessons learned, organizational knowledge, continuous improvement, previous projects, project planning, risk avoidance.

The correct answer is C. Both A and B . Digital tools that facilitate project team collaboration can include agenda management tools, teleconferencing platforms, document-sharing websites, planning software, digital collaboration platforms, and social media or enterprise social tools. These tools support different collaboration needs. Agenda management helps structure meetings and decision points. Teleconferencing enables remote interaction and real-time discussion. Document-sharing websites support version access, review, storage, and team visibility. Planning software helps coordinate schedules, tasks, dependencies, resources, and progress. Digital collaboration platforms support messaging, shared workspaces, issue tracking, knowledge exchange, and team coordination. Social media or enterprise social tools can support rapid communication, community building, informal updates, and engagement, where appropriate and controlled. Option A is correct but incomplete. Option B is also correct but incomplete. The question asks which digital tools can be used, and both groups contain valid examples. Effective project managers select tools based on information sensitivity, stakeholder needs, accessibility, governance requirements, team distribution, and the complexity of collaboration. The uploaded source question lists both tool groups and provides “Both A and B” as the complete answer option.

Reference topics: digital collaboration tools, project team collaboration, planning software, teleconferencing, document sharing, communication technology.

The correct answer is A . The purpose of reporting is to provide the current status, forecast, and analysis of the project. Reporting converts project management information into useful, structured communication for decision-making and control. It should explain where the project currently stands, what is expected to happen next, what variances or trends exist, and what decisions or actions may be required. Effective reports may cover scope, schedule, cost, quality, resources, risks, issues, changes, stakeholder engagement, benefits, and overall confidence. Option B is related to communication management because project communications should meet stakeholder information needs, but reporting specifically focuses on presenting project status, forecasts, and analysis. Option C is incorrect because reporting is not limited to the end of the project; it occurs throughout the project life cycle. Waiting until completion would prevent timely governance decisions, corrective actions, escalation, and stakeholder alignment. PMBOK also supports this by describing project reporting as collecting performance data, producing performance measures, and reporting and disseminating performance information. The uploaded question set identifies current status, forecast, and analysis as the reporting purpose.

Reference topics: project reporting, current status, forecasting, performance analysis, project control, stakeholder information.

The correct answer is A . The purpose of benefit management is to assist the sponsoring organization and the customer in realizing the desired benefits of a project from the project’s outcomes. Benefits are not created simply because deliverables have been produced. Deliverables must be used, adopted, integrated, or operated in a way that produces outcomes, and those outcomes must create measurable advantages. Benefit management therefore connects the project’s outputs to organizational value. It identifies expected benefits, defines how they will be measured, assigns ownership, monitors benefit realization, and supports corrective action when benefits are not being achieved. Option B describes continued business justification, which helps determine whether the project remains relevant and beneficial in context, but it is not the full purpose of benefit management. Option C describes review or control of continued alignment, stakeholder expectations, and risk acceptability. Benefit management is specifically focused on realizing desired benefits from outcomes, often extending beyond project closure into operational use.

Reference topics: benefit management, outcomes, benefits realization, sponsoring organization, customer value, project outputs.

The correct answer is A . To assess project progress, the project manager should collect and analyze the status of planned and forecasted stakeholder engagement and communications, among other performance information. Progress assessment is not limited to technical work completed or schedule dates achieved. It also includes whether stakeholders are being engaged as planned, whether communications are occurring at the right time, whether information needs are being met, and whether future engagement activities are still realistic. Stakeholder engagement and communications directly affect acceptance, decision-making, issue resolution, risk visibility, and project support. Option B is incorrect in this context because lessons learned from previous projects are valuable inputs for planning and improvement, but they are not the primary current-progress information being asked for. Option C is also not the best answer because the business case and initiation document establish justification and authorization; they may be reviewed for continued alignment, but they are not the direct status information used to assess ongoing progress. PMBOK emphasizes that project communications management ensures project information is planned, created, distributed, monitored, and disposed of appropriately. The uploaded source lists stakeholder engagement and communication status as the relevant answer.

Reference topics: project progress assessment, stakeholder engagement, communications, monitoring, project reporting.

The correct answer is B . Lily’s statement is not acceptable because project team composition can be reassessed and revised where necessary. Project resource needs are not always fixed after the project plan is authorized. As the project progresses, changes in scope, schedule, risks, technical requirements, stakeholder expectations, supplier performance, or team availability may require adjustments to the team structure. In Tricko’s online store project, the team includes web developers, network engineers, and a systems analyst. If additional cybersecurity, payment integration, UX design, legal compliance, or e-commerce operations expertise becomes necessary, the team should be adjusted rather than constrained by the original plan. Option A is incorrect because it treats the approved plan as permanently fixed. Option C is also too restrictive because reassessment may be required whenever circumstances justify it, not only at the beginning of a phase or work package. Sound project management maintains control while allowing justified adaptation. The project manager should monitor team capability, availability, workload, and performance, then revise composition through approved processes where needed. The source scenario explicitly tests Lily’s claim that team composition cannot be revised after authorization.

Reference topics: project team, resource management, team composition, reassessment, project plan adaptation.

The correct answer is B . Needs and opportunities resulting from organizational strategy or business requirements should be evaluated before formal authorization to initiate a new project. This evaluation is part of pre-project analysis and helps determine whether a project should be started. It connects the potential project to business drivers, strategic objectives, expected outcomes, benefits, risks, required investment, constraints, and stakeholder needs. If this evaluation is postponed until after authorization, the organization may approve a project without sufficient justification, resulting in weak strategic alignment or poor value realization. Option A may sound attractive because projects should remain aligned throughout the life cycle, but the specific evaluation of needs and opportunities for initiation occurs before formal authorization. During the project, continued justification may be reviewed, but the initial evaluation belongs before authorization. Option C is incorrect because pre-project activities are the period in which this evaluation is performed; it should not wait until they are completed. The decision to authorize the project should be based on the results of this evaluation. The uploaded source question presents this timing directly.

Reference topics: organizational strategy, business requirements, needs and opportunities, pre-project activities, authorization, project initiation.

The correct answer is internal. The fourth paragraph identifies two factors that were likely to negatively affect project performance: the low maturity level of the company’s project management and the limited availability of resources. Both are internal factors because they originate within Exhibix’s organizational environment. Project management maturity refers to the organization’s capability to apply consistent governance, planning, control, reporting, lessons learned, decision-making, and management practices. Resource availability also belongs to the internal environment when it concerns the organization’s human, financial, technical, or operational capacity to support the project. These factors can influence schedule reliability, delivery confidence, team workload, decision speed, quality of planning, and the effectiveness of risk responses. External factors would include conditions outside the organization, such as regulatory changes, supplier disruption, market instability, competitor action, customer behavior, economic factors, or changes in technology standards. Although the scenario later describes technical challenges with AR software, the question specifically asks about the fourth paragraph. That paragraph refers to organizational maturity and resource limitations, both of which are internal project context factors.

Reference topics: internal factors, organizational maturity, resource availability, project environment, project performance influences.

The correct answer is academic research. Studies related to similar projects are knowledge-based external sources used to understand project context, benchmark assumptions, identify risks, and support decisions about the project life cycle. When an organization analyzes its external environment, it may consider legal, regulatory, market, social, technological, environmental, economic, and knowledge-based factors. In the scenario, DND reviewed studies related to similar projects specifically to help determine the project life cycle. These studies are not described as supplier records, procurement databases, customer pricing intelligence, competitor data, or commercial data platforms. Therefore, they do not fit the concept of a commercial database. They are also not marketplace conditions, because marketplace conditions refer to demand, supply, competition, pricing, customer behavior, and industry trends. Academic research is the most appropriate classification because it includes structured studies, research findings, technical investigations, feasibility evidence, and lessons from comparable initiatives. In a complex project such as alternative fuel vehicle production, academic research can inform technology readiness, sustainability considerations, safety assumptions, environmental performance, and life cycle selection. This supports an evidence-based governance and planning approach.

Reference topics: external environment, academic research, project life cycle, comparable project studies, project context analysis.

The correct answer is B because organizational strategy should be used to identify, document, and evaluate opportunities, threats, weaknesses, and strengths that can inform future action. Projects should be connected to the organization’s strategic direction, business needs, and intended value. Strategy helps determine why a project should exist, what opportunities it should exploit, what weaknesses it may address, what threats it should respond to, and how it supports organizational objectives. This strategic analysis provides the rationale for selecting, prioritizing, authorizing, and shaping projects. Option A is partially aligned with strategic thinking, but it is incorrect because threats cannot simply be eliminated in most project environments; they must be identified, assessed, treated, monitored, and controlled. Option C is incorrect because ISO 21502 recognizes both tangible and intangible value. A project may produce physical deliverables, digital outputs, capability improvements, customer experience improvements, compliance outcomes, or knowledge-based benefits. Strategy is therefore not used to favor only tangible value. The source question set places this question directly under ISO 21502 project management concepts and presents option B as the complete strategic-use statement.

Reference topics: organizational strategy, opportunities, threats, strengths, weaknesses, business needs, project justification.

The correct answer is C. Both A and B . Project scope should be considered in future decisions and when communicating the importance of the project, its objectives, and its benefits. Scope defines what is included in the project, what is excluded, the work required, the expected deliverables, and the boundaries for decision-making. Future decisions about changes, resources, schedule, cost, quality, risks, procurement, and stakeholder expectations should be evaluated against the approved scope to avoid uncontrolled expansion or misalignment. Scope is also central to communication because stakeholders need to understand what the project is intended to achieve, why it matters, and how its deliverables support objectives and benefits. If scope is unclear or not considered when communicating project value, stakeholders may develop unrealistic expectations or misunderstand the project’s purpose. Therefore, scope is both a control reference and a communication tool. It helps maintain alignment between the project’s authorized boundaries and the benefits the organization expects to realize.

Reference topics: project scope, future decisions, project objectives, benefits communication, scope control, stakeholder alignment.

The correct answer is C . The project initiation should be approved by the sponsoring organization or by a person acting with authority on its behalf. In the scenario, Michaele Wagner is the CEO of Leute and therefore represents the organization’s senior authority. Her approval of project initiation is acceptable because initiation commits the organization to proceed with a project, allocate resources, and authorize project activities. This decision should not be made solely by the project manager, because the project manager manages the project after authorization but does not normally provide the business authority to initiate it. It should also not be delegated only to work package leaders, whose responsibilities relate to assigned packages of work, not organizational investment decisions. Project initiation connects the proposed project to business needs, strategic objectives, expected benefits, funding, and governance accountability. Since Leute is using the project to recover revenue and improve customer satisfaction, authorization by the sponsoring organization is essential. The uploaded scenario confirms that Michaele approved initiation after reviewing Allison’s project brief and after discussions and analysis.

Reference topics: project initiation, sponsoring organization, project authorization, project brief, governance approval.

Yes. It is possible for project phases to overlap when the project life cycle and management approach justify it. Project phases are used to structure work, manage decision points, organize resources, control risks, and support progressive delivery. However, phases do not always have to be strictly sequential. Depending on complexity, urgency, uncertainty, and delivery strategy, a project may use overlapping, iterative, incremental, adaptive, or hybrid approaches. In Exhibix’s case, the project involves augmented reality glasses, holographic interaction, and software development for therapeutic video games. This type of project may benefit from overlapping phases because design, software development, technical validation, user experience testing, and integration may need to proceed in parallel or through repeated feedback cycles. Overlapping phases can reduce schedule duration and expose technical issues earlier, but they must be controlled carefully because they can increase rework, coordination complexity, dependency risk, and change management demands. The project manager’s suggestion is therefore acceptable, provided the sponsor and governance structure maintain appropriate oversight, decision points, and controls. The key issue is not whether phases overlap, but whether the overlap is intentional, justified, authorized, and managed.

Reference topics: project life cycle, phase overlap, tailoring, complexity, adaptive delivery, phase control.

The correct answer is C. Wideband Delphi estimating . The network engineer proposed that each team member should provide an estimate and that the team should then reach agreement on a joint estimate. This is consistent with Wideband Delphi, a group-based estimation technique in which several experts or team members contribute estimates, discuss assumptions, reconcile differences, and converge toward a consensus estimate. It is especially useful when work is uncertain, expert judgment is needed, or several technical perspectives must be integrated. Option A, parametric estimating, uses statistical relationships or parameters, such as cost per page, cost per transaction, cost per server, or effort per function point. The scenario does not describe the use of historical rates or mathematical parameters. Option B, single-point estimating, provides one estimate for a task, often without explicitly representing uncertainty or group consensus. The network engineer’s proposal is not an individual single estimate; it is a collaborative consensus process. For Tricko’s online store, this method is suitable because developers, network engineers, and systems analysts each understand different cost drivers. The uploaded source scenario describes this team-estimate-and-consensus method directly.

Reference topics: cost estimating, Wideband Delphi, expert judgment, consensus estimating, project cost planning.

Yes. Considering the legal context of stakeholders is acceptable when developing a project governance framework. Governance establishes how a project is authorized, directed, monitored, controlled, escalated, and aligned with the sponsoring organization’s objectives. Because projects operate within a wider environment, governance cannot be based only on the organization’s internal legal position. It must also reflect stakeholder-related legal, regulatory, contractual, ethical, safety, environmental, and compliance conditions. In DND’s case, the production of alternative fuel cars may involve vehicle safety regulations, environmental standards, emissions requirements, supplier contracts, customer protection obligations, and approval requirements from public authorities. Stakeholders such as regulators, customers, suppliers, investors, communities, and environmental bodies may all impose legal expectations that directly affect the project’s scope, risks, requirements, acceptance criteria, and decision-making controls. Therefore, including stakeholder legal context strengthens governance and reduces exposure to non-compliance, rework, delay, and reputational damage. The PMBOK definition of project governance also supports this logic by describing governance as the framework, functions, and processes that guide project management activities to create a unique product, service, or result that meets organizational strategic and operational goals.

Reference topics: project governance framework, stakeholder context, legal environment, external factors, governance alignment.

The correct answer is A . The purpose of post-project activities is to verify that project outcomes are sustainable and that the expected benefits are being realized. Post-project activities occur after the project has delivered its outputs and moved into use, operation, or benefit realization. At this stage, the focus shifts from producing deliverables to confirming whether those deliverables are creating the intended outcomes and benefits. This may include reviewing benefit performance, operational adoption, user satisfaction, sustainability of results, residual risks, lessons learned, and whether additional action is required to secure value. Option B describes issue management during the project, where events or problems that threaten success must be handled. Option C describes acceptance management or validation of deliverables, which normally occurs before or during project closure. Post-project activity is broader and more value-oriented: it asks whether the project’s intended change has endured and whether benefits are actually being realized. This distinction is central to ISO 21502-style thinking because project success is not only the completion of outputs, but also the enablement of outcomes and benefits. The source question set identifies sustainable outcomes and benefit realization as the correct purpose.

Reference topics: post-project activities, outcomes, benefits realization, sustainability, value realization, project transition.