PRINCE2 Agile Foundation Exam 온라인 연습
최종 업데이트 시간: 2025년10월10일
당신은 온라인 연습 문제를 통해 PRINCE2 Exam PRINCE2 Agile Foundation 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 PRINCE2 Agile Foundation 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 50개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
Reference: https://www.prince2primer.com/directing-a-project-3/
정답:
Explanation:
Reference: https://worldofagile.com/blog/product-based-planning-technique-in-prince2/
정답:
Explanation:
Reference: https://www.lucidchart.com/blog/agile-vs-waterfall-vs-kanban-vs-scrum
정답:
Explanation:
Reference: https://publications.axelos.com/PRINCE2Agile2016/content.aspx?page=pra_166&showNav=true&expandNav=true
정답:
Explanation:
Reference: https://publications.axelos.com/prince2agile2016/content.aspx?page=pra_206&showNav=true&expandNav=true
정답:
Explanation:
The Project Closure Workshop is the formal forum used to reflect on lessons learned during the project lifecycle. It is held towards the end of the project and provides an opportunity for the project team, stakeholders, and sponsors to review successes, challenges, and areas for improvement.
Capturing lessons learned supports organizational learning, helps avoid repeating mistakes, and improves future projects and agile adoption. This reflective practice aligns with PRINCE2’s focus on continuous improvement and governance requirements.
Other workshops such as team planning (A) focus on upcoming work, agile enablement (B) on agile adoption, and project kickoff (C) on project initiation, none of which prioritize lessons learned reflection.
The project closure workshop is a vital practice to ensure knowledge retention and maturity in both traditional and agile project environments.
Reference: PRINCE2 Agile Foundation Version 2, Section 9.2 "Closing a Project," and PRINCE2 Agile Study Guide, Chapter 9.
정답:
Explanation:
The Progress practice in PRINCE2 Agile is focused on providing a forecast of the project's viability by monitoring actual progress against plans and predicting future performance. It ensures that decisions can be made based on current status and trends, enabling timely interventions if necessary.
This practice involves collecting progress data, reviewing milestones, updating forecasts, and communicating status to stakeholders. Forecasting viability includes assessing whether the project remains aligned with business justification and expected benefits.
While opportunities and threats are part of risk management (B), user needs belong to requirements management (C), and accountability is a broader governance concern (D), progress specifically deals with tracking and forecasting delivery status.
The practice combines traditional PRINCE2 stage controls with agile iterative reviews, providing an integrated view of progress.
Reference: PRINCE2 Agile Foundation Version 2, Section 7.1 "Progress Practice," and PRINCE2 Agile Study Guide, Chapter 7.
정답:
Explanation:
Personas in PRINCE2 Agile serve as fictional, archetypal users representing the needs, behaviors, and goals of real users. In the business case practice, personas are used to identify and articulate specific user benefits. This ensures the project focuses on delivering value that meets the actual needs of different user groups.
By understanding personas, teams can tailor product features and prioritize requirements that provide meaningful benefits, thereby strengthening the business case and increasing stakeholder buy-in. Personas help clarify who will use the product, what problems they face, and how the solution delivers value.
Personas go beyond demographic grouping (A); they are detailed profiles including motivations and pain points. They do not relate directly to timelines (B) or product version differentiation (D).
Using personas aligns with agile principles of customer focus and continuous stakeholder engagement embedded in PRINCE2 Agile.
Reference: PRINCE2 Agile Foundation Version 2, Section 7.1 "Using Personas in Business Case," and PRINCE2 Agile Study Guide, Chapter 7.
정답:
Explanation:
The Risk practice is specifically aimed at controlling uncertainties that could impact the achievement of the project’s objectives. In PRINCE2 Agile, risk management involves identifying, assessing, and controlling threats and opportunities to reduce negative impacts and maximize positive outcomes.
Effective risk management is a core theme and practice in PRINCE2 Agile and is crucial for agile environments where change and uncertainty are inherent. The practice ensures that risks are continuously monitored and appropriate responses are planned and implemented. This proactive management helps keep the project viable and aligned with business justification.
While plans support managing scope and resources, issues deal with current problems rather than potential future events, and quality ensures that products meet requirements, risk management uniquely focuses on uncertainty.
The PRINCE2 Agile guidance emphasizes integrating agile techniques such as frequent reviews and retrospectives to improve risk awareness and control.
Reference: PRINCE2 Agile Foundation Version 2, Section 8.3 "Risk Management Practice," and PRINCE2 Agile Study Guide, Chapter 8.
정답:
Explanation:
One of the significant challenges when merging traditional project management approaches like PRINCE2 with agile delivery methods is the lack of guidance on doing agile. While PRINCE2 provides a structured framework focusing on governance, control, and business justification, agile introduces flexible, iterative, and people-centered approaches. The integration of these requires clear guidance on how to implement agile practices effectively within the PRINCE2 framework.
PRINCE2 Agile acknowledges that while it offers a comprehensive method to combine governance and agility, many organizations and practitioners struggle with practical implementation, especially in how to “do agile” properly. This includes understanding how to adopt agile roles, ceremonies, and artifacts without losing control, as well as aligning agile delivery with PRINCE2’s management layers.
The challenge is compounded by the fact that agile methodologies emphasize adaptive planning and team autonomy, whereas traditional project management often focuses on upfront planning and command-and-control structures. PRINCE2 Agile aims to bridge this gap by providing detailed guidance, but a lack of practical ‘how-to’ agile advice remains a common issue.
Other options like terminology differences (A), unclear processes (B), and guidance at delivery level (C) are lesser challenges because PRINCE2 Agile provides a common vocabulary and defined processes that include delivery considerations.
Reference: PRINCE2 Agile Foundation Version 2, Section 1.4 "Challenges of Combining Agile and PRINCE2," and PRINCE2 Agile Study Guide, Chapter 1.
정답:
Explanation:
Trading/swapping is a technique used within the issues practice to manage and resolve conflicts or competing priorities by negotiating trade-offs. For example, scope items, resources, or deadlines may be traded or swapped between stakeholders to reach agreements that keep the project on track.
This collaborative negotiation supports flexible, pragmatic issue resolution, aligning with agile values of collaboration and customer focus. It enables project teams to balance competing demands while maintaining progress and business justification.
Objectives and key results (B) are goal-setting tools, refactoring (C) is a technical practice for code improvement, and delegation poker (D) is about decision-making authority ― none specifically target issue resolution.
Trading/swapping aligns with PRINCE2’s controlled management of issues and agile’s collaborative problem-solving approach.
Reference: PRINCE2 Agile Foundation Version 2, Section 8.4 "Issues Practice," and PRINCE2 Agile Study Guide, Chapter 8.
정답:
Explanation:
The product owner is responsible for preparing and maintaining the product backlog, ensuring it accurately reflects user requirements, priorities, and acceptance criteria. This role acts as the voice of the customer, maximizing product value by managing backlog items, ordering them to reflect business priorities, and clarifying requirements for development teams.
Monitoring stage progress (A) and managing project-level risks (B) are typically roles of the project manager or risk owner within PRINCE2 governance. The project backlog (C) contains higher-level requirements for the entire project and is not the product owner's direct responsibility.
The product owner bridges business and delivery, ensuring the team works on the most valuable features while maintaining clarity and quality of backlog items.
Reference: PRINCE2 Agile Foundation Version 2, Section 5.2 "Roles and Responsibilities," and PRINCE2 Agile Study Guide, Chapter 5.
정답:
Explanation:
The Agile Enablement Workshop provides a collaborative environment where teams and stakeholders define critical agile artifacts, including the Definition of Ready. This definition specifies the criteria a user story or product backlog item must meet before work can begin, ensuring clarity and readiness.
The workshop facilitates alignment on quality standards, scope, and expectations, reducing ambiguity and improving flow through development cycles. By involving all key participants, the Definition of Ready is meaningful and practical, tailored to the project's specific context.
While starting up (A), kickoff (B), and initiation workshops (C) focus on project foundation and planning, they do not specifically focus on agile readiness criteria.
This workshop is essential for embedding agile practices within PRINCE2 governance and fostering effective delivery.
Reference: PRINCE2 Agile Foundation Version 2, Section 6.7 "Defining Ready and Done," and PRINCE2 Agile Study Guide, Chapter 6.
정답:
Explanation:
Delegation poker is a collaborative game used to define and clarify decision-making authority within teams. It helps teams agree on who has the power to make decisions for specific areas, from the team level to senior management. Using cards representing different levels of delegation, team members discuss and align expectations, ensuring clarity and reducing conflicts.
This technique fosters transparency, shared ownership, and empowerment, which are critical for agile teams operating under PRINCE2 governance. It also helps balance autonomy and control, supporting the principle of manage by exception.
Other options: a team skills matrix documents competencies, personas represent user archetypes for design, and magic estimation is a sizing technique ― none focus on decision authority.
Delegation poker aligns well with PRINCE2 Agile’s emphasis on defined roles and empowered teams.
Reference: PRINCE2 Agile Foundation Version 2, Section 4.3 "Managing Roles and Responsibilities," and PRINCE2 Agile Study Guide, Chapter 4.
정답:
Explanation:
The Agilometer is a diagnostic tool used within PRINCE2 Agile to assess the agility maturity and identify risks associated with adopting or operating in an iterative and agile environment. It helps teams and organizations evaluate their current agile capabilities, cultural readiness, and potential challenges that may impact project delivery.
The Agilometer highlights risk areas such as resistance to change, lack of agile skills, unclear roles, or insufficient governance adaptation. By providing a structured assessment, it enables proactive risk management and targeted improvements to reduce uncertainties inherent in iterative approaches.
Other artifacts like the project backlog (A) track requirements, the risk management approach (C) defines the method of managing risks but does not specifically identify iterative risks, and the Definition of Done (D) clarifies completion criteria rather than risks.
The Agilometer supports continuous improvement and risk mitigation aligned with PRINCE2’s risk and quality practices, ensuring agile projects remain viable and controlled.
Reference: PRINCE2 Agile Foundation Version 2, Section 8.6 "Tools for Agile Risk Management," and PRINCE2 Agile Study Guide, Chapter 8.