매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
Professional Scrum Product Owner II 온라인 연습
최종 업데이트 시간: 2026년03월30일
당신은 온라인 연습 문제를 통해 Scrum PSPO-II 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 PSPO-II 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 120개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
The smallest product Increment that is valuable enough to release is one that delivers a single new or improved outcome for the customers or users of the product. This is because the outcome is the ultimate measure of value, not the output or the features1. An outcome is a change in behavior, attitude, or situation that results from using the product2. An outcome can be achieved by delivering a single feature, fixing a defect, or improving an existing functionality, as long as it meets the Definition of Done and the Sprint Goal3. Therefore, the best answer is A.
The other options are not correct because:
B. Adds a new feature. This is not a sufficient condition, as a new feature may not deliver a valuable outcome if it is not aligned with the product vision, the customer needs, or the market conditions4.
C. Fixes at least one defect. This is not a necessary condition, as a defect may not affect the value of the product if it is minor, rare, or irrelevant to the customer5.
D. Delivers all “must do” Product Backlog items. This is not a realistic condition, as the Product Backlog is a dynamic and emergent artifact that changes based on feedback, learning, and discovery. There is no fixed set of “must do” items that can guarantee the delivery of
value.
Reference: 1: Outcome vs. Output, 2: What is an Outcome?, 3: The Definition of Done, 4:
Feature vs. Outcome, 5: Defect vs. Value, : The Product Backlog
정답:
Explanation:
According to the PSPO II resources, a product owner should optimize the value of the product and the work of the Scrum Team1. One way to do this is to improve the value experienced by the customer, which is the perception and evaluation of the product by the customer2. A price increase can be justified if the customer perceives that the product delivers more value than the cost3. This can be achieved by enhancing the product quality, functionality, usability, or design, or by providing additional benefits or services to the customer4. The other options are not effective ways to justify a price increase, as they may either reduce the value experienced by the customer, or increase the cost without increasing the value.
Reference:
1: The Scrum Guide
2: User Experience
3: Value-Based Pricing
4: 8 Techniques to Justify a Price Increase
: Justification for a Price Increase: Positioning For Success
정답:
Explanation:
A Product Goal is a summary statement of the desired outcome or value that the product should deliver. It communicates the target future state of the product, which is aligned with the product vision and strategy. It enhances focus by providing a clear direction and purpose for the Scrum Team and the stakeholders. It is a commitment contained in the Product Backlog, which means that it is transparent, visible, and understood by everyone involved in the product development. It provides a long-term objective for the Scrum Team to plan against, which helps them to prioritize and refine the Product Backlog items and to craft the Sprint Goals.
Option D is not correct because the Product Goal does not need to have the approval of all stakeholders. The Product Owner is accountable for the value of the product and the Product Backlog, and therefore has the authority to define and communicate the Product Goal. The Product Owner may collaborate with the stakeholders to discover and validate their needs and expectations, but does not need to seek their consensus or permission for the Product Goal.
Option F is not correct because the Product Goal is not a contract with the business, but rather a flexible and adaptable guide for the product development. The Product Goal is not fixed and immutable, but rather emergent and dynamic. It can be changed or updated as the product evolves and the market conditions change. The Product Goal does not limit or constrain the changes that may occur during the product development, but rather enables and supports them.
Reference: Professional Scrum Product Owner II Assessment
Understanding and Applying the Scrum Framework
Managing Products with Agility
Scrum Guide 2020 Update - Introducing the Product Goal
The Product Goal explained
정답:
Explanation:
Option B is the best answer because it reflects the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is a living artifact that represents the current understanding of what the product needs to be most valuable for the customers and the stakeholders1. The Product Backlog is not a fixed or static document, but rather an emergent and dynamic one that adapts to the changing environment, needs, and feedback. The Product Owner is accountable for managing the Product Backlog and ensuring that it is transparent, ordered, and refined2. The Product Owner collaborates with the Scrum Team and the stakeholders to inspect and adapt the Product Backlog items based on the new insights, opportunities, and learnings that arise from the changing environment34. The Product Owner also uses various techniques, such as product vision, value proposition, user stories, experiments, and evidence-based management, to define, validate, and prioritize the Product Backlog items5.
Option A is not the best answer because it contradicts the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is not a requirements specification document, but rather a list of hypotheses and assumptions that need to be tested and validated in the real world5. The Product Backlog items are not detailed or fixed upfront, but rather refined and clarified as they get closer to implementation2. Updating the requirements specification document to ensure stability implies a plan-driven and predictive approach that does not embrace change and feedback, and that does not optimize value delivery.
Option C is not the best answer because it contradicts the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is not a project plan, but rather a product roadmap that guides the development of the product. The Product Backlog does not have a predefined end date or scope, but rather evolves and changes as the product grows and matures1. Keeping the Product Backlog the same until the end of the project implies a plan-driven and predictive approach that does not embrace change and feedback, and that does not optimize value delivery.
Option D is not the best answer because it contradicts the agile and empirical nature of Scrum and Product Ownership. The Product Backlog is not a disposable artifact, but rather a cumulative and iterative one that builds on the previous work and learnings1. The Product Backlog items are not discarded or replaced, but rather refined and updated as the product evolves and changes2. Archiving the Product Backlog and creating a new one implies a disruptive and wasteful approach that does not leverage the existing knowledge and feedback, and that does not optimize value delivery.
1: Product Backlog
2: Product Backlog Management
3: Empiricism
4: Stakeholders and Customers
5: Product Vision
: Product Value
: Evidence-Based Management
: [Agile Manifesto]
: [Product Roadmap]
: Product Owner Accountabilities
: Sprint Review
: Product Backlog Refinement
: [User Stories]
: [Value Proposition]
: [Experiments]
정답:
Explanation:
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. Scrum consists of three roles (Scrum Master, Product Owner and Developers), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective), and three artifacts (Product Backlog, Sprint Backlog and Increment). Each component of Scrum serves a specific purpose and is essential to the successful usage of Scrum. Scrum is not a methodology, where you can “pick and choose” which parts of Scrum you think will work for your environment. Scrum is a whole, and each part of Scrum complements the others. Scrum is based on empiricism, which means that knowledge comes from experience and making decisions based on what is observed. Scrum employs an iterative, incremental approach to optimize predictability and control risk. Scrum is not like traditional processes but with self-management to replace Project Managers. Scrum is a different way of working that requires a shift in mindset and culture. Scrum promotes self-organization, collaboration, transparency, inspection and adaptation.
Professional Scrum Product Owner™ II Certification
Understanding and Applying the Scrum Framework
[The Scrum Guide]
정답:
Explanation:
According to the Professional Scrum Product Owner™ II certification guide1, the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. This means that the Product Owner should collaborate with the Developers and the Scrum Master to find the best way to deliver value in the current Sprint, even if the initial forecast is not met. The Product Owner should not change or abandon the Sprint Goal, as it is a commitment made by the Scrum Team during Sprint Planning. The Product Owner should also not skip Product Backlog refinement activities, as they are essential for preparing the Product Backlog for future Sprints. The Product Owner should not end the Sprint prematurely, as it may cause more disruption and waste than delivering a potentially releasable Increment. The Product Owner should not inform management that more resources are needed, as it may imply that the Scrum Team is not self-organizing and cross-functional. The Product Owner should respect the Developers’ autonomy and professionalism and support them in finding the best solution to the problem. Therefore, the best answer is to reduce the scope of the Sprint, if possible, to still meet the Sprint Goal. This means that the Product Owner and the Developers should negotiate the scope of the Sprint Backlog within the Sprint, removing or adding Product Backlog items that are aligned with the Sprint Goal and the value delivery.
Reference: 1: Professional Scrum Product Owner™ II Certification | Scrum.org
정답:
Explanation:
= Based on the Evidence-Based Management (EBM) framework, your product has a high Current Value (CV), which means that it delivers value to the existing customers and meets their needs and expectations. However, it also has a high Unrealized Value (UV), which means that there is a large gap between the potential and actual use of the product in the market. This indicates that your product has a low awareness, reach, or appeal among the potential customers who could benefit from it.
To increase the business performance of the product, you need to reduce the UV and increase the Ability to Innovate (A2I), which is the ability to deliver future value. One way to do this is to improve the marketing of the product, which can help you to communicate the value proposition, differentiate the product from the competitors, and attract a greater number of customers. This can also provide you with more feedback and data to inform your product strategy and backlog prioritization.
The other options are not the best actions to take, because they either do not address the root cause of the high UV, or they may compromise the CV or A2I of the product. Increasing the number of product features may not necessarily increase the value or the demand for the product, and it may also increase the complexity and the cost of development. Releasing an identical product with a new name may confuse the customers and dilute the brand identity, and it may also create legal or ethical issues. Dropping the price for the product may not be a sustainable or profitable strategy, and it may also affect the perceived quality or value of the product. Reference: = Professional Scrum Product Owner™ II Certification, Managing Products with Agility, Evidence-Based Management
정답:
Explanation:
Frequent product releases are beneficial for several reasons. They enable teams to inspect and adapt more frequently, which means they can get faster feedback, validate their assumptions, and improve their product incrementally. They help teams better understand and meet customer needs, which means they can deliver more value, increase customer satisfaction, and build trust and loyalty. They help teams to learn how to correct and eliminate errors, which means they can reduce waste, improve quality, and prevent technical debt. Smaller, more frequent releases are less risky, which means they can reduce uncertainty, avoid big-bang failures, and enable faster
recovery123.
Reference:
1: Managing Products with Agility
2: Understanding and Applying the Scrum Framework
3: Evolving the Agile Organization
정답:
Explanation:
Sharing people with unique skills across multiple teams will likely result in teams having to wait more often for those people to be available, impeding the delivery of value. This is because those people will have to context-switch between different teams, products, and domains, reducing their focus and efficiency1. Moreover, sharing people with unique skills will create bottlenecks and dependencies in the delivery process, increasing the risk of delays and quality issues2. Furthermore, sharing people with unique skills will discourage teams from developing deep technical skills themselves, making them less cross-functional and self-organizing3. Therefore, the best answer is A.
The other options are not correct because:
B. Teams do not have to develop deep technical skills. This is not a desirable condition, as it contradicts the Scrum value of commitment and the principle of continuous improvement. Teams should strive to develop deep technical skills to deliver high-quality products and to respond to changing requirements and technologies4.
C. Costs are lower since expensive resources are shared. This is not necessarily true, as the costs of context-switching, waiting, and quality issues may outweigh the benefits of sharing
resources. Moreover, this option implies a resource-oriented mindset, rather than a value-oriented
mindset, which is not aligned with the Scrum framework and the Product Owner role5.
D. More work gets done since people are better utilized. This is not a valid measure of success, as the amount of work done does not reflect the value delivered. Moreover, this option implies a utilization-oriented mindset, rather than an outcome-oriented mindset, which is not aligned with the Scrum framework and the Product Owner role.
Reference: 1: Context Switching, 2: Bottlenecks and Dependencies, 3: Cross-Functional Teams, 4: Technical Excellence, 5: Resource vs. Value Orientation, : Utilization vs. Outcome Orientation
정답:
Explanation:
None of the options given are accurate descriptions of what an effective Product Owner must do. According to the PSPO II resources, an effective Product Owner must12345:
Develop and communicate a clear and compelling Product Goal that aligns with the organization’s vision and strategy.
Manage the Product Backlog by refining, ordering, and prioritizing items that deliver value to customers and users.
Collaborate with stakeholders and the Scrum Team to understand their needs, expectations, and feedback.
Empower the Scrum Team to make decisions and self-organize around the Sprint Goal and the Product Backlog items.
Experiment and validate assumptions using empirical evidence and data.
Optimize the value of the product and the work of the Scrum Team.
Continuously inspect and adapt the product and the process based on the outcomes and feedback.
Reference:
1: The Scrum Guide
2: Product Owner Learning Path
3: Product Owner Competencies
4: Evidence-Based Management
5: Product Strategy
정답:
Explanation:
The Product Backlog is an ordered list of what is needed to improve the product, and it is the single source of work undertaken by the Scrum Team. The Product Owner is responsible for ordering the Product Backlog items by value, risk, priority, and dependencies. The Product Backlog should be transparent and accessible to the Scrum Team and the stakeholders, so that everyone can understand the scope and progress of the product development. Therefore, options A and B are true statements about the Product Backlog.
Option C is not true because the Product Backlog items can be expressed in various formats, such as user stories, use cases, scenarios, or any other way that clearly conveys the intent and value of the item. User stories are a common and useful technique, but not a mandatory one.
Option D is not true because the Product Backlog is not a fixed and complete specification of the product, but rather an emergent and dynamic artifact that evolves over time. The Product Backlog items are refined and clarified by the Product Owner and the Developers throughout the product development process, and new items can be added or removed as needed. The Product Backlog does not need to be fully defined before the first Sprint begins, but only enough to support the first Sprint Planning.
Option E is not true because the Product Owner is not the only source of ideas and requirements for the product. The Product Owner collaborates with the Developers and the stakeholders to discover, validate, and prioritize the Product Backlog items. The Product Owner may delegate the authority to add items to the Product Backlog to others, but remains accountable for the ordering and the value of the Product Backlog.
Option F is not true because the Product Backlog does not replace the communication and collaboration between the Developers and the stakeholders. The Product Backlog represents the input of all stakeholders, but it is not a substitute for direct feedback and interaction. The Developers need to engage with the stakeholders to understand their needs, expectations, and feedback, and to deliver a valuable product increment that meets the Sprint Goal and the Definition of Done.
Reference: Professional Scrum Product Owner II Assessment
Understanding and Applying the Scrum Framework
Managing Products with Agility
[What is a Product Backlog?]
[Product Backlog Explained]
정답:
Explanation:
Option D is the best answer because it indicates that the Product Owner and the Scrum Team are not aligned on the vision, goals, and value of the product. The Product Owner is responsible for maximizing the value of the product and the work of the Scrum Team1. To do so, the Product Owner needs to work closely with the Scrum Team, communicate the product vision, provide clear and valuable Product Backlog items, collaborate on the Sprint Goal, and inspect and adapt the product based on feedback23. If the Increment presented at the Sprint Review does not reflect the Product Owner’s expectations, it means that there is a gap between what the Product Owner wants and what the Scrum Team delivers. This gap can lead to waste, rework, dissatisfaction, and missed opportunities. The Product Owner should work more with the Scrum Team to ensure that they have a shared understanding of the product and its value proposition, and that they deliver Increments that meet the Definition of Done and the acceptance criteria45.
Option A is not the best answer because it does not necessarily imply that the Product Owner needs to work more with the Scrum Team. People may leave the Scrum Team for various reasons, such as personal, professional, or organizational factors. While the Product Owner should care about the well-being and motivation of the Scrum Team members, and try to foster a positive and collaborative environment, the Product Owner is not accountable for the people management or the team composition1. The Scrum Master is more likely to address the issues that cause people to leave the Scrum Team, such as impediments, conflicts, or dysfunctions.
Option B is not the best answer because it does not necessarily imply that the Product Owner needs to work more with the Scrum Team. The Product Owner is expected to spend enough time with the Scrum Team to provide them with the necessary guidance and feedback2. However, the Product Owner also has other responsibilities, such as engaging with stakeholders, customers, and users, managing the Product Backlog, validating the product value, and aligning the product strategy with the business goals12. The Product Owner does not need to work full time with the Scrum Team, as long as they are available and accessible when needed, and they empower the Scrum Team to make decisions and self-organize.
Option C is not the best answer because it does not necessarily imply that the Product Owner needs to work more with the Scrum Team. The acceptance criteria for the Product Backlog items are the conditions that must be met for the items to be considered done and valuable. The Product Owner is accountable for defining and communicating the acceptance criteria to the Scrum Team1. However, the Product Owner can also collaborate with the Scrum Team and the stakeholders to refine and clarify the acceptance criteria, and to ensure that they are aligned with the Definition of Done and the Sprint Goal. The acceptance criteria for the Product Backlog items may not appear to be complete at the beginning of the Sprint, but they can be refined and updated throughout the Sprint, as long as they do not change the scope or the value of the items. The Product Owner should work with the Scrum Team to ensure that the acceptance criteria are clear, testable, and valuable, but they do not need to work more with the Scrum Team just because the acceptance criteria are not complete at a certain point in time.
1: Product Owner Accountabilities
2: Product Backlog Management
3: Product Value
4: Product Vision
5: Sprint Review
: Scrum Master Accountabilities
: Stakeholders and Customers
: Business Strategy
: Definition of Done
: Product Backlog Refinement
: Sprint Planning
: Sprint Backlog
정답:
Explanation:
As a Product Owner, you are accountable for maximizing the value of the product and the work of the Scrum Team. To do this, you need to collaborate with various stakeholders, user communities and other Product Owners to understand their needs, expectations and feedback, and to align them with the product vision and strategy. You also need to work with the Developers on Product Backlog refinement, which is an ongoing activity to add detail, estimates and order to Product Backlog items. This helps the Developers to understand what is valuable and feasible to deliver in the upcoming Sprints, and to plan and execute their work accordingly. These are typical and essential work for a Product Owner in a Sprint.
The other options are not typical or effective work for a Product Owner in a Sprint. Attending every Daily Scrum is not necessary, as the Daily Scrum is an event for the Developers to inspect their progress and plan their next steps. The Product Owner can attend the Daily Scrum if invited by the Developers, but should not interfere or answer questions that are not related to the Sprint Goal or the Product Backlog. Creating financial reporting upon the spent hours reported by the Developers is not a valuable activity, as it does not reflect the outcome or the value delivered by the product. It also goes against the Scrum values of trust and respect, as it implies that the Developers are not self-managing or committed to their work. Updating the work plan for the Developers on a daily basis is also not a good practice, as it undermines the autonomy and creativity of the Developers, and reduces their ability to inspect and adapt their work based on the empirical evidence. The Product Owner should not tell the Developers how to do their work, but rather focus on what is the most valuable outcome for the product.
Professional Scrum Product Owner™ II Certification
Understanding and Applying the Scrum Framework
Managing Products with Agility
정답:
Explanation:
According to the Professional Scrum Product Owner™ II certification guide1, the Sprint Goal is the single objective for the Sprint. It is a commitment made by the Scrum Team during Sprint Planning. The Sprint Goal provides guidance to the Developers on why it is valuable to build a coherent Increment. The Product Owner proposes how the product could increase its value and utility in the current Sprint. The whole Scrum Team then collaborates to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders. The Product Owner should not dictate the Sprint Goal, but rather collaborate with the Developers and the Scrum Master to create a shared understanding and alignment. The other options are not activities that a Product Owner should never do, because they are either part of the Product Owner’s accountabilities (A, C, D) or may be done in collaboration with others (A, D).
Reference: 1: Professional Scrum Product Owner™ II Certification | Scrum.org
정답:
Explanation:
= As a Product Owner, you are accountable for maximizing the value of the product and the work of the Developers. To do this, you need to have a clear vision of the product and its target users, as well as a validated understanding of the market opportunities and risks. You also need to collaborate with stakeholders and customers to align their expectations and feedback with the product goals and strategy.
In this scenario, you face a dilemma between pursuing a new market segment or satisfying the existing customers. Both options have potential value, but also uncertainty and trade-offs. The best way to proceed is to devise an experiment that will help you to test your assumptions and learn more about the new market and its potential. This could be a small-scale release, a prototype, a survey, or any other method that can provide you with empirical evidence and feedback. By doing this, you can reduce the risk of investing in a feature that may not deliver the expected value, and also gain insights that can help you to refine your product vision and backlog.
This approach is consistent with the principles of agile product management, which emphasize delivering value early and often, validating hypotheses with data, and adapting to changing customer
needs and market conditions. It also demonstrates your ability to apply the Scrum values of openness, courage, and respect, as you are willing to explore new possibilities, challenge your own opinions, and involve your stakeholders and customers in the decision-making process.
Reference: = Scrum Guide, Managing Products with Agility, Evidence-Based Management