Pass the PECB ISO 21502 ISO-21502-Lead-Project-Manager Questions and answers with ExamsMirror

The correct answer is C . A project interface is the area, point, or zone where different stakeholders, teams, systems, organizations, functions, phases, or work packages meet and interact. Interfaces are important because many project issues arise not inside a single work area, but at the boundaries between areas of responsibility. Examples include the handover between design and construction, coordination between the project team and operations, engagement between supplier and customer, or decision points between project governance and delivery teams. Option A is incorrect because control mechanisms are part of project monitoring and control, not the definition of an interface. Option B is also too narrow because an interface may exist between phases, but it is not simply the transition period between phases. Interfaces can be organizational, technical, contractual, informational, procedural, or stakeholder-based. Effective interface management clarifies responsibilities, communication channels, dependencies, handover criteria, escalation paths, and decision rights. Poorly managed interfaces create ambiguity, delays, rework, conflict, and quality problems. The uploaded source question identifies the interaction zone between stakeholders as the correct definition of project interface.

Reference topics: project interface, stakeholder interaction, coordination, handover, dependencies, interface management.

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

The correct answer is A . Project benefits should be maintained by taking corrective, and when required, preventive actions when deviations from planned benefits occur. Maintaining benefits requires active management, not passive observation. If expected benefits are not being achieved, are delayed, or are at risk, the organization should identify the cause of deviation and take action to restore or protect benefit realization. Corrective action addresses an existing deviation, while preventive action reduces the likelihood of future deviation. Option B, collecting performance measurements for each benefit, is important for monitoring, but measurement alone does not maintain benefits. Option C, reporting and communicating benefit status, supports visibility and decision-making, but communication alone does not correct underperformance. Maintaining benefits means acting on benefit information to preserve expected value. This may involve adjusting adoption plans, improving operational readiness, addressing stakeholder resistance, changing processes, providing training, or revising transition arrangements. The emphasis is on ensuring that project outcomes continue to support the desired benefits.

Reference topics: benefits management, corrective action, preventive action, planned benefits, benefit deviation, benefit realization control.

The correct answer is C . The main purpose of pre-project activities is to verify whether the project is worth starting. Before formal authorization, the organization should evaluate the need or opportunity, strategic alignment, expected benefits, rationale, feasibility, high-level risks, assumptions, constraints, investment requirements, and stakeholder expectations. This stage helps determine whether the proposed project should proceed, be modified, deferred, rejected, or combined with other initiatives. Option A is too narrow because evaluating team competence may be useful later in resourcing, but it is not the central purpose of pre-project activities. Option B relates more to planning and delivery control after the project has been authorized. Pre-project work is primarily concerned with justification and selection: does the project make sense, does it support organizational objectives, and is it likely to deliver value? This is also where a project brief or business case may be developed or refined to support decision-making. The source question set states this purpose directly in the options and identifies verification of whether the project is worth starting as the main purpose.

Reference topics: pre-project activities, project justification, project brief, business case, authorization, strategic alignment.

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.

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 C because it is the statement that is not correct. The reporting approach and methods should be planned and documented early enough to guide project communications and control, not at the end of the project. Reporting needs to support decision-making throughout the project life cycle, so the project manager should define what will be reported, to whom, how often, in what format, by which method, and using which project information sources. Option A is correct because reporting should align with current project documentation and be based on analysis of project management information. Reports must reflect reliable data, not informal impressions. Option B is also correct because reporting should be monitored and adjusted as stakeholder needs, governance expectations, project complexity, or information requirements change. Reporting is not static; it must remain useful to recipients. Option C would make reporting ineffective because planning it at the end would remove its value for monitoring, forecasting, escalation, and corrective action during delivery. The uploaded question set frames this as a “NOT correct” reporting question and includes option C as the incorrect reporting practice.

Reference topics: project reporting, reporting approach, project information, communication planning, report recipients, monitoring and adjustment.

The correct answer is B. Effectiveness of communication channels . Ross selected communication methods according to the nature and complexity of the information being transmitted. He planned ad hoc discussions for complex and personal matters, and notes or text messages for simple and factual information. This reflects the principle that communication channels differ in richness, speed, feedback capability, personal focus, and suitability for the message. Richer channels, such as direct discussion, are more effective when information is ambiguous, sensitive, complex, or requires immediate feedback. Leaner channels, such as notes or text messages, are suitable for simple, factual, routine, or low-risk information. Ross’s explanation that the model allows faster processing of information and uses natural language directly supports the idea of channel effectiveness. Option A is incorrect because the scenario does not focus on cultural interpretation, language barriers, or cross-cultural norms. Option C is also incorrect because the gulf of execution and evaluation concerns user interaction and usability, not the selection of communication media in project communication planning.

Reference topics: communication planning, communication channels, channel effectiveness, information complexity, stakeholder communication.

The correct answer is A . Tom followed the rule of reflecting only sequence constraints between work packages. The scenario states that Tom required the project team to perform tasks in a predetermined order regardless of any resource shortages. This means he prioritized logical or technical sequence dependencies and did not account for resource constraints. Sequence constraints describe the order in which work must be performed, such as when one task must finish before another can start. Resource constraints, however, relate to the availability of people, equipment, materials, funding, facilities, or supplier capacity. If a schedule reflects both sequence and resource constraints, the timing of work may change when resources are unavailable or overallocated. Tom’s approach ignored those resource limitations and focused only on task order. Option B is therefore incorrect because the scenario specifically says resource shortages were disregarded. Option C is too general because defining relationships between tasks does not capture the specific issue being tested: whether the schedule logic reflects only sequence constraints or also resource constraints. This is an important scheduling distinction because ignoring resource constraints can produce an unrealistic plan.

Reference topics: schedule management, sequence constraints, resource constraints, work package dependencies, project planning.