PECB ISO 21502 Lead Project Manager Exam Questions

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

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.