Free Preparation Discussions
MENU
PECB ISO 21502 Lead Project Manager Exam Questions
- Topic 1: Fundamental principles and concepts of project management: Covers the core principles, concepts, and foundational elements of project management based on ISO 21502, providing the basis for effective project execution.
- Topic 2: Integrated project management practices: Focuses on applying integrated project management practices to coordinate project activities, resources, governance, and stakeholder engagement throughout the project lifecycle.
- Topic 3: Individual management practices for a project: Explains the key management practices used to plan, monitor, control, and deliver individual project components in alignment with ISO 21502 guidance.
Free PECB ISO 21502 Lead Project Manager Exam Actual Questions
Note: Premium Questions for ISO 21502 Lead Project Manager were last updated On Aug. 14, 2026 (see below)
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.
Based on the fourth paragraph of scenario 2, what factors did the project team notice that were likely to have a detrimental impact on the project's performance?
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.
According to ISO 21502, what is the main purpose of pre-project activities?
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.
What is the purpose of the planning quality phase?
The correct answer is A. The purpose of planning quality is to define the applicable standards and quality requirements for the project and its outcomes. Quality planning establishes what ''acceptable quality'' means before work is performed. It identifies relevant standards, customer requirements, regulatory requirements, acceptance criteria, quality metrics, inspection needs, test approaches, responsibilities, and control methods. This allows the team to build quality into the work rather than discovering quality problems late. Option B describes quality assurance or quality management activities focused on ensuring that work is being performed in accordance with defined quality requirements and standards. Option C describes quality control, where results are checked, nonconformities are identified, and corrective action is taken to improve unsatisfactory performance. Planning quality is therefore the front-end definition phase: it clarifies the quality basis against which project work and outcomes will later be assessed. Without effective quality planning, the project team may deliver outputs that are technically complete but unacceptable to the customer or performing organization.
Reference topics: quality planning, quality standards, quality requirements, acceptance criteria, project outcomes.
Scenario:
Leute is a low-cost airline, headquartered in Wien, Austri
a. The company aims to offer passengers optimal options regarding its services and gain the lead role among other competitors in the airline industry. Recently, Leute experienced a major drop in revenue due to negative reviews from customers in various online platforms. To increase its profit and enhance customer satisfaction, the company decided to expand its in-flight services by offering entertainment, such as movies, audio books, and games, food for purchase in economy and full meals in premium cabins, and comforts, such as blankets and pillows. For the implementation of this project and future projects of the airline, the CEO of Leute, Michaele Wagner, decided to follow the guidelines of ISO 21502 on project management.
Initially, Allison, the project manager, created a short document in which she justified and summarized all project aspects, including: the nature and purpose of the project, the objectives of the project, key milestones of the project and the time needed to complete the project, and the audience that the project targets.
Afterward, Allison held a meeting with Michaele during which she presented this document and briefly explained each of its points. After a considerable amount of analysis and discussions, the project initiation was approved by Michaele. In addition, a team of eighteen members was authorized to start with the project activities.
While undertaking the project activities, Allison ensured that each work package takes longer than 8 hours, but less than 80 hours, so that they would be completed in 1 to 10 working days. In addition, during this phase, several changes were made in the predefined aspects of the project, which were approved by Nick Todd, the project sponsor. For instance, initially, the project delivery was set to be completed after six months. However, considering how the project was implemented and the time required for the completion of each phase, the deadline for the project completion was postponed for another two months. These changes were also reflected in the business case, which was updated accordingly.
A month after the project execution began, Allison conducted an earned value analysis to measure the progress of the project up to that stage. She measured how efficiently the work was being performed with regard to its budgeted cost, after which she concluded that it was going according to the plan. Moreover, she organized a meeting with relevant project stakeholders in order to communicate the progress report to them.
Based on scenario 3, Allison ensured that the size of each work package was longer than 8 hours, but less than 80 hours in order to complete them in 1 to 10 working days. What rule did Allison follow in this case?
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.
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.
Lana did not provide any information regarding the project duration in the project brief. Is this acceptable?
The correct answer is B. The project brief should include information about project duration, at least at a high level or as an initial estimate. A project brief is used to summarize the proposed project so that decision-makers can evaluate whether it should be initiated. It should provide enough information to understand the project context, objectives, rationale, high-level scope, target outcomes, key milestones, time frame, and major assumptions or constraints. Duration is especially important because it affects resource planning, cost estimation, feasibility, supplier coordination, governance decisions, and expected benefit timing. Lana included project context and objectives, but omitted duration and stated that it could not be determined. While exact duration may not be fully known at the brief stage, a preliminary time frame, assumption-based estimate, or duration range should still be provided. Her verbal statement during discussions does not replace properly documenting the duration in the project brief. A decision to initiate the project should be based on recorded information, not only informal explanation. Therefore, the omission was not acceptable. The source scenario explicitly states that duration was missing from the project brief and asks whether that omission is acceptable.
Reference topics: project brief, project duration, pre-project activities, project initiation, high-level planning, feasibility.
- Select Question Types you want
- Set your Desired Pass Percentage
- Allocate Time (Hours : Minutes)
- Create Multiple Practice tests with Limited Questions
- Customer Support
Barbara Robinson
2 days agoRyan Harris
13 days agoStephanie Davis
1 month ago