PECB ISO 21502 Lead Project Manager Exam Questions Instant Access

Question 1

Whose cultural and ethical norms should the governance of projects take into consideration?

ACommunities in which the organization operates

BAny other organizations involved

CBoth A and B

Answer : C

The correct answer is C because project governance should consider both the cultural and ethical norms of the communities in which the organization operates and those of any other organizations involved. Governance is not limited to decision rights, reporting lines, and approval processes. It also establishes the behavioral expectations, accountability model, ethical standards, stakeholder treatment, and decision environment for the project. Projects frequently affect communities, customers, regulators, suppliers, partners, and internal teams. If governance ignores cultural or ethical expectations, the project may face resistance, reputational harm, stakeholder conflict, compliance issues, or poor adoption of project outputs. In multi-organization projects, governance must also respect the ethical and cultural norms of partner organizations because decisions, responsibilities, communication styles, escalation practices, and acceptance expectations may differ. This is especially important in international, public-facing, sustainability-related, or joint projects. Option A is incomplete because it excludes other organizations involved. Option B is also incomplete because it excludes the community context. The source question set presents ''Both A and B'' as the complete governance answer.

Reference topics: project governance, cultural norms, ethical norms, community context, multi-organization projects, stakeholder environment.

Question 2

Scenario:

Oakniture is a furniture manufacturer located in Bristol, England. It is known for its kitchen tables made out of different types of wood, such as chestnut, walnut, and oak. In early 2022, Lana, one of the senior researchers of the company, conducted a feasibility study to determine if there is a market for oak wood coffee tables, which indicated that the demand for oak wood coffee tables is relatively high. As such, Lana prepared a project brief and presented it to the top management of the company. The project brief included information on the project context and project objectives. After several discussions, the top management agreed that the project should be undertaken, but lastly, they asked Lana about the project duration. Lana claimed that the project duration cannot be determined and such information was not provided in the project brief; however, she added that the project duration will mainly depend on the competencies of the project team and on Oakniture's suppliers of wood.

Following that, the top management initiated the project and assigned Tom, the operations director, as the project manager, and Lana as the project sponsor. To manage the project, they decided to use the guidelines of ISO 21502.

Initially, Tom defined the governance and management framework alone, and then he mobilized the team and assigned the roles and responsibilities to each team member. In addition, Tom and the project team identified the stakeholders and developed the project plan. To ensure effective management of each project phase, Tom used a work breakdown structure (WBS) to organize project activities. Tom presented the project activities in the WBS by linking task dependencies and showing project milestones. In addition, Tom calculated the duration of each work package by determining the early start and early finish dates. Regarding the relationship between work packages, Tom required the project team to perform tasks in the predetermined order, regardless of any resource shortages they might experience.

A week after the project implementation began, Tom collected and analyzed data regarding the progress of the project. To keep everyone up to date, he held a meeting with Lana and project stakeholders.

Based on scenario 4, the governance and management approach was defined by Tom alone. Is this acceptable?

AYes, the governance and management approach should be defined only by Tom, the project manager

BNo, Tom should have defined the governance and management approach in cooperation with the project team

CNo, Tom should have defined the governance and management approach in cooperation with Lana, the project sponsor

Answer : C

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.

Question 3

Which of the following situations indicates a hope creep?

AProject team members randomly add elements and features to the deliverables that they believe the client would prefer to have

BA member of the project team slips behind schedule, but reports that they are on track, expecting to catch up by the next report deadline

CA project team member works, but does not make progress proportional to their efforts

Answer : B

The correct answer is B. Hope creep occurs when a team member falls behind schedule but reports that work is still on track because they hope to recover before the next reporting point. It is a reporting and control problem because the project manager receives inaccurate status information and may fail to identify schedule risk early. Hope creep is dangerous because it delays escalation, hides performance issues, weakens forecasting, and can cause sudden schedule slippage when recovery does not occur. Option A describes scope creep or gold plating, where unauthorized features are added to deliverables because team members believe the client may prefer them. Option C describes effort creep, where work continues but progress is not proportional to the effort being invested. Hope creep is specifically linked to optimistic or misleading progress reporting based on the expectation that the delay will be corrected later. Effective project control requires honest reporting, early issue identification, realistic forecasting, and corrective action rather than relying on unverified recovery expectations.

Reference topics: hope creep, schedule reporting, project control, progress monitoring, scope creep, effort creep.

Question 4

Scenario:

Exhibix is a video game developer headquartered in Zagreb, Croatia, which is known for producing therapeutic video games for children dealing with ADHD. In order to improve users' experience, Exhibix suggested undertaking a project that would enable users to interact with the virtual content in the form of holograms through augmented reality glasses in the video games. For this project, the management decided to follow the guidelines of ISO 21502 on project management.

Prior to formalizing project management, the management of Exhibix assessed, among others, the potential impacts that the project management approach may have on both internal and external stakeholders. In addition, they determined if there were sufficient resources, both human and financial, for the formalized project management. Furthermore, during this period, the management decided to assess only the nature of previous projects, due to their successful delivery.

After formalizing project management, the project board organized a meeting during which they delegated their responsibilities to the project sponsor. Following this meeting, the project sponsor and project manager proceeded to define the project phases and their time frames. Considering the complexity of the project, the project manager suggested leaving open the possibility of overlapping certain phases of the project.

The preparations began in June, and the project manager and the team, consisting of 20 highly skilled professionals, had approximately six months to implement the project. During the implementation of the project, the project team noticed that the low maturity level of the company's project management and the limited availability of resources were likely to have a negative impact on the performance of the project. With the deadline approaching, the team was also under a lot of pressure to close the project on time.

They were confronted with numerous challenges with the AR software, which led to the extension of the deadline for the project completion. During this period, the project office assisted the project manager and the team by providing administrative support and managing information regarding the project. Following these events, the project manager and the team were able to complete the project within the new set deadline. After the project sponsor confirmed the project closure, the AR glasses were released for use.

Prior to formalizing project management, Exhibix decided to assess only the nature of previous projects. Is this acceptable?

AYes, only the nature of previously successful projects should be assessed before formalizing project management

BNo, the nature of current and future projects should also be assessed before formalizing project management

CNo, only the nature of current projects should be assessed before formalizing project management

Answer : B

No. Exhibix should also assess the nature of current and future projects before formalizing project management. Formalizing project management means establishing a consistent approach for governance, roles, responsibilities, planning, controls, resources, methods, tools, reporting, assurance, and decision-making. If an organization assesses only previous successful projects, it may design a project management approach that reflects past conditions but fails to address current complexity or future strategic needs. In this scenario, the project involves holograms, augmented reality glasses, therapeutic gaming, a six-month delivery target, and significant software complexity. These characteristics may differ substantially from Exhibix's previous successful projects. The organization therefore needs to assess current project demands, future project pipeline requirements, resource capacity, project management maturity, stakeholder impacts, and expected complexity. The scenario itself later confirms that low maturity and limited resources negatively affected project performance, showing why broader assessment was necessary. A mature ISO 21502-aligned approach requires tailoring project management to the organization's current and anticipated project environment, not merely repeating practices from past success.

Reference topics: formalizing project management, organizational context, project management maturity, current and future projects, resource assessment, stakeholder impact.

Question 5

According to ISO 21502, how should the project benefits be maintained?

ABy taking corrective, and when required, preventive actions in case of deviations from the planned benefits

BBy collecting performance measurements for each benefit

CBy reporting and communicating the status of expected benefits

Answer : A

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.

Question 6

According to PMBOK, what is the definition of Earned Value Analysis (EVA)?

AA method that utilizes a set of measures associated with scope, schedule, and cost to determine the cost and schedule performance of a project

BThe amount of budget deficit or surplus at a given point in time, expressed as the difference between the earned value and the actual cost

CAn earned value management measure that indicates how efficiently the work is being performed with regard to the budgeted cost of the work

Answer : A

The correct answer is A. Earned Value Analysis, within the earned value management family of techniques, uses integrated performance measures to determine project cost and schedule performance. It links work accomplished with the budget authorized for that work and compares it against actual cost and planned progress. This makes it more powerful than simple expenditure tracking because it shows whether the project is earning value at the expected rate. Option B describes cost variance, not EVA. Cost variance is the budget deficit or surplus at a point in time, normally calculated as earned value minus actual cost. Option C describes the cost performance index, not EVA. CPI indicates cost efficiency by comparing earned value to actual cost. EVA is the broader analytical method; CV and CPI are specific measures used within earned value analysis. PMBOK defines earned value management as a methodology combining measures of scope, schedule, and resources to evaluate project performance and progress, which supports the integrated nature of EVA. The uploaded question set lists option A as the definition choice for EVA.

Reference topics: earned value analysis, earned value management, cost performance, schedule performance, cost variance, CPI.

Question 7

Which methodologies below are more flexible in nature and provide an iterative approach for project management?

AChange management

BTraditional

CAgile

Answer : C

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.