PECB ISO-21502-Lead-Project-Manager Practice Test Questions Answers

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 . Needs and opportunities resulting from organizational strategy or business requirements should be evaluated before formal authorization to initiate a new project. This evaluation is part of pre-project analysis and helps determine whether a project should be started. It connects the potential project to business drivers, strategic objectives, expected outcomes, benefits, risks, required investment, constraints, and stakeholder needs. If this evaluation is postponed until after authorization, the organization may approve a project without sufficient justification, resulting in weak strategic alignment or poor value realization. Option A may sound attractive because projects should remain aligned throughout the life cycle, but the specific evaluation of needs and opportunities for initiation occurs before formal authorization. During the project, continued justification may be reviewed, but the initial evaluation belongs before authorization. Option C is incorrect because pre-project activities are the period in which this evaluation is performed; it should not wait until they are completed. The decision to authorize the project should be based on the results of this evaluation. The uploaded source question presents this timing directly.

Reference topics: organizational strategy, business requirements, needs and opportunities, pre-project activities, authorization, project initiation.

The correct answer is C because stakeholder involvement is generally more intensive and continuous in agile approaches than in traditional predictive approaches. In traditional project management, the project structure, scope baseline, schedule, cost baseline, and delivery path are often defined more firmly at earlier stages. Stakeholder input is important, but it is commonly concentrated during initiation, requirements gathering, approvals, stage gates, and formal change control. Agile approaches, by contrast, rely on iterative development, frequent feedback, progressive refinement, and continuous stakeholder collaboration. Stakeholders, users, product owners, customers, or customer representatives can significantly influence priorities, acceptance, backlog refinement, and the evolving shape of the solution. Option A is incorrect because agile approaches are generally more capable of changing direction based on feedback, while traditional approaches are usually less flexible once baselines are established. Option B is also reversed: traditional approaches usually have a more firmly defined project structure, whereas agile approaches allow more adaptation. The source question set identifies this item as a comparison between traditional and agile methodologies.

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

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.

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.