PECB인증ISO-21502-Lead-Project-Manager시험준비를 하고 계시다면Fast2test에서 출시한PECB인증ISO-21502-Lead-Project-Manager덤프를 제일 먼저 추천해드리고 싶습니다. Fast2test제품은 여러분들이 제일 간편한 방법으로 시험에서 고득점을 받을수 있도록 도와드리는 시험동반자입니다. PECB인증ISO-21502-Lead-Project-Manager시험패는Fast2test제품으로 고고고!
| Section | Objectives |
|---|---|
| Project Planning | - Communication and procurement planning - Risk management planning and quality planning - Scope, schedule, cost, and resource planning |
| Project Closure | - Administrative closure and handover - Lessons learned and project evaluation - Final deliverables acceptance |
| Project Initiation | - Project charter and stakeholder identification - Business case development and justification |
| Project Management Principles (ISO 21502 Framework) | - Project management concepts and governance alignment - Roles, responsibilities, and organizational context |
| Monitoring and Controlling | - Performance tracking and reporting - Change control and issue management - Risk and quality control |
| Project Execution | - Deliverable production and integration management - Team leadership and resource coordination |
>> ISO-21502-Lead-Project-Manager최신버전 시험공부 <<
현재 많은 IT인사들이 같은 생각하고 잇습니다. 그것은 바로PECB ISO-21502-Lead-Project-Manager인증시험자격증 취득으로 하여 IT업계의 아주 중요한 한걸음이라고 말입니다.그만큼PECB ISO-21502-Lead-Project-Manager인증시험의 인기는 말 그대로 하늘을 찌르고 잇습니다,
질문 # 50
According to ISO 21502, what does a project plan include, among others?
정답：A
설명：
The correct answer is C. Both A and B . A project plan should include, among other elements, the project scope, risks, assumptions, and constraints. The project plan is the integrated reference document that describes how the project will be executed, monitored, controlled, and closed. Scope defines what the project is expected to deliver and the boundaries of the work. Risks identify uncertain events or conditions that could affect project objectives. Assumptions describe factors considered true for planning purposes, even though they may later require validation. Constraints define limiting conditions, such as fixed deadlines, budget ceilings, regulatory obligations, resource limits, contractual requirements, or technology restrictions. These elements are interconnected: assumptions and constraints influence scope, risk exposure, schedule, cost, quality, and resource planning. A project plan that includes only scope and risks would omit the planning logic behind them. A plan that includes only assumptions and constraints would not adequately define the deliverables or uncertainty profile. Therefore, both sets of information are necessary for sound integrated project management.
Reference topics: project plan, scope, risks, assumptions, constraints, integrated planning.
질문 # 51
Scenario:
Leute is a low-cost airline, headquartered in Wien, Austria. 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.
Question:
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?
정답：B
설명：
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.
질문 # 52
Scenario:
Leute is a low-cost airline, headquartered in Wien, Austria. 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.
Question:
According to scenario 3, the business case was updated to reflect the changes made regarding the project delivery. Is this acceptable?
정답：C
설명：
The correct answer is A . Updating the business case to reflect changes in the project's context is acceptable and necessary. The business case supports project justification by explaining why the project should continue, what value it is expected to enable, and whether the investment remains worthwhile. It should not be treated as a document used only before initiation and then frozen. If major aspects of the project change, such as delivery date, cost, scope, risk exposure, assumptions, expected benefits, or organizational context, the business case should be reviewed and updated so that decision-makers can assess continued viability. In the Leute scenario, the project completion deadline was postponed by two months because of implementation realities and the time required for each phase. This affects schedule, cost exposure, benefit timing, stakeholder expectations, and possibly the value proposition. Therefore, updating the business case was appropriate.
Option B is incorrect because the business case may need to be maintained throughout the project. Option C is too narrow because changes beyond delivery, such as risks, benefits, funding, or scope, may also require business case updates.
Reference topics: business case, project justification, change control, project context, continued viability, integrated project control.
질문 # 53
According to ISO 21502, when is positive value created?
정답：A
설명：
The correct answer is B because positive value is created when the benefits enabled by a project exceed the investment of resources required to deliver it. Project value is not determined solely by the existence of deliverables. A project can produce outputs and still fail to create value if the cost, effort, disruption, risk exposure, or resource consumption outweighs the benefits realized. ISO 21502-aligned project management emphasizes the connection between outputs, outcomes, and benefits. Deliverables are produced by the project, outputs are the immediate results, outcomes represent the changes created by using those outputs, and benefits are the measurable improvements or advantages obtained. Positive value arises when those benefits justify and exceed the resources invested. Option A is insufficient because equal investment and benefit does not create positive value; it merely breaks even. Option C is incorrect because producing deliverables alone does not prove value. Deliverables must contribute to desired outcomes and benefits. The question set explicitly frames this as an ISO 21502 concept of value creation.
Reference topics: value creation, project benefits, investment of resources, deliverables, outputs, outcomes, benefits realization.
질문 # 54
Which of the following statements describes a project termination by extinction?
정답：C
설명：
The correct answer is A . Project termination by extinction occurs when a project is brought to an end because it has either successfully achieved its objectives or has failed and is no longer justified. In both cases, the project ceases to exist as an active project. If successful, extinction means the project has completed its intended work, deliverables have been accepted or transferred, and closure activities can proceed. If unsuccessful, extinction means the project is stopped because its continuation is no longer viable, valuable, or possible. Option B describes suspension or temporary termination, where the project is closed or paused with the intention of resuming later. Option C describes termination by integration, where project outputs are absorbed into the operations of the parent organization and the project team or structures may be integrated into ongoing operations. Extinction is therefore the clearest form of final termination: the project ends because completion or failure removes the basis for continuing project work. The source question set identifies closure due to failure or successful completion as the definition of termination by extinction.
Reference topics: project termination, termination by extinction, project closure, successful completion, project failure, closure decision.
질문 # 55
......
퍼펙트한PECB ISO-21502-Lead-Project-Manager시험대비덤프자료는 Fast2test가 전문입니다. PECB ISO-21502-Lead-Project-Manager덤프를 다운받아 가장 쉬운 시험준비를 하여 한방에 패스가는것입니다. 다같이 PECB ISO-21502-Lead-Project-Manager덤프로 시험패스에 주문걸어 보아요. 마술처럼PECB ISO-21502-Lead-Project-Manager시험합격이 실현될것입니다.
ISO-21502-Lead-Project-Manager높은 통과율 시험공부: https://kr.fast2test.com/ISO-21502-Lead-Project-Manager-premium-file.html