Practice Free ISO-21502-Lead-Project-Manager PECB ISO 21502 Lead Project Manager Exam Exam Questions Answers With Explanation

The correct answer is C. Project sponsor and project board . The project manager normally reports to the project sponsor and, where established, the project board. These governance roles provide direction, oversight, authorization, and decision-making authority for the project. The sponsor maintains the business link between the project and the sponsoring organization, while the project board may represent broader governance interests, including business, user, supplier, technical, or organizational perspectives. Reporting to these roles enables performance review, escalation, approval of significant changes, risk-based decisions, and continued justification. Option A is too narrow and too rigid because the project manager does not report only to top management in every project. Reporting arrangements depend on the project governance structure. Option B is also too broad because key stakeholders may receive information, but they are not necessarily the formal reporting authority. Stakeholder communications and governance reporting are related but not identical. A project manager may communicate with many stakeholders, but formal accountability reporting is directed to the sponsor and project board. The uploaded source question identifies sponsor and project board as the correct reporting destination.

Reference topics: project manager reporting, project sponsor, project board, governance reporting, accountability, project oversight.

The correct answer is C. Agile . Agile methodologies are more flexible in nature because they use iterative and incremental approaches to project management. Instead of defining all work in detail at the beginning and executing it through a rigid sequence, agile approaches allow the project team to deliver value progressively, inspect results frequently, and adapt the solution based on stakeholder feedback, emerging risks, and changing requirements. This is particularly useful in environments where uncertainty is high, requirements are expected to evolve, or early user feedback is essential. Traditional methodologies are generally more predictive and sequential, with stronger emphasis on upfront planning, baselines, and formal change control. Change management is not a project delivery methodology in this context; it is a management discipline used to control and implement changes affecting the project, product, organization, or stakeholders. Therefore, among the given options, agile is the methodology that best fits the description of being flexible and iterative. The source question set identifies “Agile” as the relevant choice among change management, traditional, and agile approaches.

Reference topics: agile methodology, iterative delivery, adaptive project management, traditional methodology, flexibility.

The correct answer is C . Proposal requests are procurement documents used to obtain supplier proposals when the buyer needs a proposed solution, approach, technical method, commercial offer, or delivery strategy for the required work. In procurement practice, a request for proposal is appropriate when the buyer knows the business need or desired outcome but wants suppliers to propose how they would meet that need. The evaluation is usually based on more than price; it can include technical quality, methodology, supplier capability, risk, schedule, innovation, compliance, and value. Option A is not correct because the request normally comes from the buyer or customer side, not from the contractor to the supplier as a general definition. Option B describes a price-focused request, closer to a request for quotation or bid, where the solution is already clearly defined and price is the main selection criterion. Proposal requests are especially useful where the scope is complex, the solution is not fully predetermined, or supplier expertise is needed to shape the delivery approach. The uploaded source text shows this question and the partial alternatives, with the concept clearly positioned under procurement practices.

Reference topics: procurement, request for proposal, supplier proposal, procurement documentation, supplier selection.

The correct answer is B because positive value is created when the benefits enabled by a project exceed the investment of resources required to deliver it. Project value is not determined solely by the existence of deliverables. A project can produce outputs and still fail to create value if the cost, effort, disruption, risk exposure, or resource consumption outweighs the benefits realized. ISO 21502-aligned project management emphasizes the connection between outputs, outcomes, and benefits. Deliverables are produced by the project, outputs are the immediate results, outcomes represent the changes created by using those outputs, and benefits are the measurable improvements or advantages obtained. Positive value arises when those benefits justify and exceed the resources invested. Option A is insufficient because equal investment and benefit does not create positive value; it merely breaks even. Option C is incorrect because producing deliverables alone does not prove value. Deliverables must contribute to desired outcomes and benefits. The question set explicitly frames this as an ISO 21502 concept of value creation.

Reference topics: value creation, project benefits, investment of resources, deliverables, outputs, outcomes, benefits realization.

The correct answer is C . Tom should not have defined the governance and management approach alone; he should have defined it in cooperation with Lana, the project sponsor. The governance and management approach establishes how the project will be directed, authorized, controlled, reported, escalated, and managed. It includes decision rights, roles, responsibilities, authority levels, reporting arrangements, assurance needs, control mechanisms, and working methods. Because governance connects the project to the sponsoring organization’s objectives and business justification, the project sponsor must be involved. The project manager can develop and operationalize the approach, but the sponsor provides the business authority and ensures that governance remains aligned with organizational priorities, investment logic, and expected benefits. Option B is not the best answer because the project team may contribute delivery insight, but the project sponsor is the essential governance partner. Option A is incorrect because allowing the project manager to define governance alone would create weak oversight and could blur the distinction between management and governance. The source scenario states that Tom defined the governance and management framework alone, which is the non-compliant action being tested.

Reference topics: governance and management framework, project sponsor, project manager, authority, project organization, integrated project direction.

The correct answer is C . Ross’s statement is not compliant because the project plan should be monitored and can be updated when required. A project plan is an approved basis for directing, managing, monitoring, and controlling project work, but it is not an immutable document. Projects operate under uncertainty, and changes may be required due to risks, issues, stakeholder feedback, resource constraints, supplier performance, technical findings, or altered business priorities. In Mallebare’s project, the three-month deadline and tournament-driven launch create schedule pressure, but that does not justify freezing the plan under all circumstances. A concise plan may be appropriate when the project is time-constrained, but it must still be controlled, reviewed, and updated if conditions change. Option A is incorrect because it treats planning as rigid rather than adaptive. Option B is too restrictive because changes may be required during execution or later project phases, not only before execution begins. Effective ISO 21502-aligned management requires maintaining the plan as a living control document while ensuring that changes are justified, authorized, communicated, and reflected in relevant baselines or supporting documents. The source question presents Ross’s “no change” statement as the issue.

Reference topics: project plan, monitoring, plan updates, change control, project control, adaptive management.

The correct answer is C because both statements express valid advantages of using ISO 21502. The standard provides guidance for project management practices that help organizations transform strategic ideas, business needs, and opportunities into project deliverables, outputs, outcomes, and benefits. These benefits may be tangible, such as products, systems, infrastructure, or facilities, or intangible, such as improved capability, customer satisfaction, organizational knowledge, compliance maturity, or reputation. By applying ISO 21502, an organization strengthens its project implementation capability because it uses a structured approach to governance, planning, delivery, control, communication, stakeholder engagement, and closure. This increases consistency and helps ensure that projects are not treated as isolated activities but as instruments for value creation. The source question set presents both statements as possible advantages, making “Both A and B” the complete answer. PMBOK also supports this principle by defining project management as applying knowledge, skills, tools, and techniques to meet project requirements.

Reference topics: ISO 21502 purpose, project value, deliverables, outputs, outcomes, benefits, organizational project capability.

The correct answer is A . Updating the business case to reflect changes in the project’s context is acceptable and necessary. The business case supports project justification by explaining why the project should continue, what value it is expected to enable, and whether the investment remains worthwhile. It should not be treated as a document used only before initiation and then frozen. If major aspects of the project change, such as delivery date, cost, scope, risk exposure, assumptions, expected benefits, or organizational context, the business case should be reviewed and updated so that decision-makers can assess continued viability. In the Leute scenario, the project completion deadline was postponed by two months because of implementation realities and the time required for each phase. This affects schedule, cost exposure, benefit timing, stakeholder expectations, and possibly the value proposition. Therefore, updating the business case was appropriate. Option B is incorrect because the business case may need to be maintained throughout the project. Option C is too narrow because changes beyond delivery, such as risks, benefits, funding, or scope, may also require business case updates.

Reference topics: business case, project justification, change control, project context, continued viability, integrated project control.

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 C . Defining the project governance and management framework is important because it provides direction and working methods to the parties involved in the project. The framework establishes how the project will be governed, managed, controlled, reported, escalated, and coordinated. It clarifies authority, decision rights, roles, responsibilities, approval mechanisms, planning approach, management practices, information flows, assurance activities, and stakeholder interfaces. Without a defined framework, project participants may operate with inconsistent expectations, unclear accountability, duplicated effort, weak escalation, or conflicting working methods. Option A is incomplete because stakeholder commitment may be supported by good governance, but it is not the primary purpose of defining the framework. Option B is also too narrow because sponsor approval to execute the plan may depend on the framework, but the framework serves a broader function across the project life cycle. It guides all involved parties in how the project should operate. The source question set directly associates the governance and management framework with providing direction and working methods. PMBOK similarly describes governance as a framework that guides project management activities to achieve strategic and operational goals.

Reference topics: governance framework, management framework, working methods, project direction, accountability, project controls.

The correct answer is A . A work package is the smallest unit of a work breakdown structure for which cost and duration are estimated and managed. It represents a manageable portion of project work that can be assigned, estimated, scheduled, monitored, controlled, and reported. Work packages are important because they provide a practical bridge between high-level scope and detailed project execution. They help define what must be delivered, who is responsible, what resources are needed, how long the work should take, and how performance will be tracked. Option B is incorrect because it describes earned value analysis or earned value management, not a work package. Option C is incorrect because it refers to a sequence of stages or critical path logic, not WBS decomposition. In a properly structured WBS, work packages sit at the lowest level of decomposition and support cost estimation, schedule development, responsibility assignment, and progress measurement. The uploaded source question gives this exact description as the correct option. PMBOK also supports this interpretation by describing WBS elements as components for which deliverable, activity, and planning information can be defined.

Reference topics: work package, WBS, scope decomposition, cost estimation, duration estimation, work control.

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 . 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.

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 B. Reintroducing a familiar practice . Adaptive change refers to a comparatively low-complexity form of change where people are asked to return to, adjust, or apply something already familiar. It usually does not require a major shift in culture, mindset, technology, or organizational identity. Because the practice is already known, resistance may be lower than with more innovative or transformational changes, although communication, reinforcement, and stakeholder engagement are still required. Option A, introducing a practice new to the practitioners, is more disruptive because the affected people have no direct familiarity with the practice. Option C, introducing a practice that is new to the organization but not the industry, is closer to an innovative or transitional change because the organization must adopt something externally established but internally unfamiliar. Adaptive change is therefore associated with reintroducing or adjusting known practices rather than creating a radically new way of working. In project management, understanding the type of change helps determine communication, training, stakeholder engagement, transition support, and resistance-management needs. The uploaded source lists this question under the ISO 21502 question set and provides these three alternatives.

Reference topics: adaptive change, organizational change, stakeholder readiness, transition management, change complexity.

The correct answer is A . Project management progress evaluations should consult the project sponsor, project manager, and project team because these roles collectively hold the business, management, and delivery perspectives required to assess progress accurately. The sponsor is concerned with continued justification, business alignment, benefits, risks, funding, and stakeholder expectations. The project manager is responsible for directing and controlling the project work, integrating information, reporting performance, managing issues, and recommending corrective action. The project team provides direct insight into completed work, remaining work, quality conditions, technical problems, dependencies, assumptions, and emerging risks. Consulting only governance or assurance roles would provide oversight but may miss operational delivery realities. Consulting only work package leaders would be too narrow because it would exclude business justification and integrated project control. Progress evaluation requires evidence from the people who sponsor, manage, and perform the work. PMBOK similarly describes the project team as individuals who support the project manager in performing project work to achieve objectives. The source question set lists project sponsors, project managers, and their teams as the relevant consultation group.

Reference topics: progress evaluation, project sponsor, project manager, project team, project control, integrated reporting.

No. The project organization should be communicated to everyone involved in the project, not only to the project team. A project organization defines the roles, responsibilities, authorities, decision rights, reporting relationships, escalation routes, and interfaces needed to direct and manage the project. If this structure is communicated only to the project team, other involved parties may not understand how the project is governed, who has authority, who is accountable for decisions, how issues are escalated, or how coordination should occur. In the DND scenario, the project organization included the project office, project assurance, a customer representative, the project board, and work package leadership. These roles are not limited to the delivery team; they are part of the broader governance and management structure. Therefore, they must understand the organization model and their relationship to it. Communicating the structure only to the team creates ambiguity, weakens accountability, and may disrupt assurance, customer involvement, and governance control. The PMBOK also treats project communications as the processes required to ensure project information is planned, collected, created, distributed, stored, monitored, and disposed of appropriately.

Reference topics: project organization, communication, roles and responsibilities, stakeholder involvement, governance interfaces.

Yes. The project organization can change throughout the project life cycle when project circumstances require adjustment. A project organization is not a static administrative chart; it is a governance and management structure designed to ensure that the right responsibilities, authorities, skills, reporting relationships, and decision-making mechanisms exist at the right time. As a project moves from initiation to design, delivery, transition, and closure, its organizational needs may change. In DND’s case, one work package leader resigned from the project to join another company project. This directly affects accountability for a defined area of work. If the project board did not adjust the structure, the project could suffer from unclear ownership, delays, poor coordination, or unmanaged delivery risk. A change is acceptable provided it is made by the appropriate authority, documented, controlled, and communicated to everyone involved in the project. The incorrect options are too rigid: changes are not limited only to the design stage, and approval of an initial project organization does not make it permanent. Effective governance balances stability with controlled adaptability.

Reference topics: project organization, project life cycle, project board authority, role changes, governance control, work package leadership.

The correct answer is B . ISO 21502 provides high-level descriptions of effective practices for project management. It is not designed as a detailed procedural manual, nor does it prescribe one mandatory methodology, life cycle, toolset, or governance model. Its purpose is to guide organizations and practitioners in applying project management concepts and practices in a structured and adaptable way. Option A is incorrect because it mixes project management with program and portfolio principles. ISO 21502 focuses on project management, not the complete governance and management of programs and portfolios. Option C is also incorrect because it expands the scope beyond projects to include programs and portfolios, which are related but distinct disciplines. A project is a temporary endeavor intended to achieve agreed objectives, while programs coordinate related projects and portfolios group projects and programs to support strategic objectives. ISO 21502 is therefore best understood as project-level guidance that can be tailored to different organizations, industries, project sizes, complexities, and delivery approaches. The uploaded question set states this distinction directly by contrasting “high-level descriptions of effective practices for project management” with broader program and portfolio options.

Reference topics: ISO 21502 purpose, effective project management practices, high-level guidance, project-level focus.