Why should the Product Owner care that the Developers adhere to the Definition of Done?
(choose the best two answers)
To influence the Total Cost of Ownership of the product.
To have transparency into what has been done at the end of each Sprint.
To be able to reprimand the team when they do not meet their velocity goal forthe Sprint.
To ensure the Developers achieve a high level of productivity over time.
A. To influence the Total Cost of Ownership of the product: Adhering to the Definition of Done ensures that the product meets the required quality standards, which can influence the Total Cost of Ownership1.
B. To have transparency into what has been done at the end of each Sprint: The Definition of Done provides a shared understanding of what work was completed and what standards were met as part of the Increment2. This creates transparency and allows the Product Owner to understand what has been accomplished at the end of each Sprint12.
Which of the following statements is true about the Product Vision?
(choose the best answer)
It evolves as the Scrum Team learns more about customers and their needs.
It is the shared responsibility of the Scrum Team to develop and evolve.
It must be completely free from discussions about strategic technology choices.
All of the above.
None of the above.
Option A is the best answer because it reflects the agile and empirical nature of Scrum and Product Ownership. The Product Vision is a concise and inspiring statement that describes the purpose, direction, and value proposition of the product1. The Product Vision 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 creating and communicating the Product Vision to the Scrum Team and the stakeholders2. The Product Owner collaborates with the Scrum Team and the stakeholders to inspect and adapt the Product Vision based on the new insights, opportunities, and learnings that arise from the changing environment34. The Product Owner also uses various techniques, such as product discovery, user research, market analysis, and experiments, to validate and refine the Product Vision5 .
Option B is not the best answer because it contradicts the accountability of the Product Owner. The Product Owner is the sole person responsible for managing the Product Backlog and maximizing the value of the product and the work of the Scrum Team. The Product Owner is also the sole person responsible for creating and communicating the Product Vision to the Scrum Team and the stakeholders2. The Product Owner may seek input and feedback from the Scrum Team and the stakeholders, but the final decision and authority on the Product Vision belongs to the Product Owner. The Scrum Team and the stakeholders are not accountable for developing and evolving the Product Vision, but they are expected to understand and support it .
Option C is not the best answer because it contradicts the reality and complexity of product development. The Product Vision is not a technical specification, but rather a strategic and business-oriented statement that guides the development of the product1. The Product Vision does not prescribe how the product should be built, but rather why and what the product should achieve. However, the Product Vision is not completely detached from the technical aspects of the product, as the technology choices may have an impact on the feasibility, desirability, and viability of the product. The Product Owner should be aware of the strategic technology choices and their implications, and discuss them with the Development Team and the stakeholders, as part of the product discovery and validation process .
1: Product Vision
2: Product Owner Accountabilities
3: Empiricism
4: Stakeholders and Customers
5: Product Discovery
Product Backlog Management
The Scrum Guide
Scrum Team
Product Value
Product Feasibility
Product Validation
[Agile Manifesto]
[User Research]
[Market Analysis]
[Experiments]
The only person who can abnormally terminate a Sprint is?
(choose the best answer)
The Developers.
The Scrum Master.
The Product Owner.
The Stakeholders.
The Scrum Guide specifies that only the Product Owner has the authority to cancel a Sprint. This is because the Product Owner is responsible for maximizing the value of the product and may decide to cancel a Sprint if the Sprint Goal becomes obsolete or if they foresee that the current direction will not lead to a valuable outcome
The smallest product Increment that is valuable enough to release is one that:
(choose the best answer)
Delivers a single new or improved outcome.
Adds a new feature.
Fixes at least one defect.
Delivers all " must do " Product Backlog items.
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. References: 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
My job as a Product Owner should focus on the following:
(choose the best two answers)
Clearly communicating product progress and strategies to customers and stakeholders.
Writing clear, transparent User Stories.
Being with the Developers all the time, just in case they need me to clarify a requirement.
Collaborating with customers and stakeholders to identify the most important product requirements.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. A major part of that accountability is working with stakeholders and making sure the Scrum Team is focused on the most valuable work.
Why A is correct:
A Product Owner must actively engage with stakeholders and ensure transparency around the product. While the Scrum Guide does not prescribe a specific reporting style, it clearly places the Product Owner in the role of managing value, aligning stakeholder needs, and making sure the Product Backlog reflects what is most important. Communicating product direction, priorities, and progress to customers and stakeholders is a key part of that responsibility.
Why D is correct:
This is one of the strongest descriptions of Product Owner work. The Product Owner collaborates with customers and stakeholders to understand needs, determine value, and order the Product Backlog accordingly. The Product Owner is accountable for effective Product Backlog management, which includes developing and explicitly communicating Product Backlog items and ordering them to best achieve goals.
Why B is not the best answer:
The Scrum Guide does not require User Stories. Scrum only requires that Product Backlog items be clear enough and ordered appropriately. User Stories are a common technique, but they are not mandated by Scrum. Therefore, “writing clear, transparent User Stories” is not an official Product Owner duty as defined by Scrum.
Why C is incorrect:
The Product Owner should be available to support clarity and decision-making, but Scrum does not say the Product Owner should be with Developers all the time. Scrum promotes self-managing teams, and the Product Owner is one member of the Scrum Team, not a constant on-demand requirement clarifier sitting with Developers at all times.
Which phrase best describes a Product Owner?
(choose the best answer)
Go-between for the Developers and customers.
Requirements engineer.
Team manager.
Value maximizer.
According to the Scrum Guide, the Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team1. This means that the Product Owner is responsible for defining, prioritizing, and delivering the features and functionalities that create the most value for the customers, users, and stakeholders of the product2. The Product Owner does this by managing the Product Backlog, collaborating with the Developers and the Scrum Master, validating the product assumptions and hypotheses, and measuring the outcomes and impacts of the product3. The Product Owner is not just a go-between, a requirements engineer, a team manager, or any other traditional role, but rather a value maximizer who drives the product vision and strategy, and ensures that the product delivers the desired benefits and solves the real problems4
Given only the information in the following three statements:
. Product A has a greater potential market than Product B.
. Product A has lower customer satisfaction than Product B.
· Product B produces more revenue at the present time.
Which investment strategies should you consider for these two products?
(choose the best answer)
For both products, continually measure the impact of any new investments ormarketing.
Invest in Product A to increase its market share, customer satisfaction, and revenue.
Investigate an increase in marketing for Product B to grow its market share.
All of the above.
The Professional Scrum Product Owner™ II (PSPO II) emphasizes the importance of a strategic approach to product management. According to the PSPO II resources, it is essential to:
Continually measure the impact of new investments or marketing efforts for both products (Option A). This aligns with the PSPO II focus on evidence-based management and making decisions based on empirical data.
Invest in Product A to increase its market share, customer satisfaction, and revenue (Option B). The PSPO II materials suggest that a product with a greater potential market but lower customer satisfaction requires attention to improve its standing and capitalize on its market potential.
Investigate an increase in marketing for Product B to grow its market share (Option C). Even though Product B is currently generating more revenue, the PSPO II guides recommend exploring opportunities to expand its market share, which could lead to even greater revenue.
Therefore, a comprehensive investment strategy that includes all the above actions is recommended for managing products with agility, as per the PSPO II guidelines. This approach ensures that both products are given the opportunity to maximize their market potential while maintaining a focus on customer satisfaction and revenue growth. It’s a holistic strategy that considers the different strengths and opportunities of each product.
You work for a large financial institution. Your products have many interdependencies: you have
mobile, web, and ATM product interfaces to financial products like savings, checking, spending,
electronic payments, credit cards, and investments. When any of these financial products
change, the changes ripple throughout the mobile, web, and ATM clients, and maintaining
consistency is challenging. What should you do to reduce this problem?
(choose the best answer)
Form products that are as independent as possible and let each product determinetheir own release plans, but ensure coordination.
Create a centralized, coordinated cross-product Development Plan to ensureconsistency.
Appoint a Project Lead to oversee all the products.
Ensure that the PMO manages the inter-product dependencies.
All of the above.
A is correct because forming products that are as independent as possible reduces the complexity and dependency of the product development, and allows each product to deliver value faster and more frequently1. Coordination among the products is still necessary to ensure alignment and consistency, but it should not be centralized or imposed by a higher authority2. B is incorrect because creating a centralized, coordinated cross-product Development Plan goes against the principles of empiricism, self-organization, and agility that Scrum promotes3. C is incorrect because appointing a Project Lead to oversee all the products undermines the accountability and autonomy of the Product Owners and the Scrum Teams4. D is incorrect because ensuring that the PMO manages the inter-product dependencies creates a layer of bureaucracy and control that hinders the collaboration and innovation of the Scrum Teams5. E is incorrect because it includes all the wrong answers.
When should the Product Owner update the project plan?
(choose the best answer)
After the Daily Scrum to ensure an accurate daily overview of project progress.
The project plan must be updated prior to the Sprint Retrospective.
The Product Backlog is the plan in Scrum. It is updated as new information andinsights emerge.
Before the Sprint Planning to know how much work will have to be done in the Sprint.
In Scrum, there is no separate artifact called a project plan. The Product Backlog is the plan for the product development, and it contains all the features, requirements, enhancements, and fixes that are needed to deliver a valuable product. The Product Backlog is not a static or fixed document, but rather an emergent and dynamic one. It is constantly updated and refined by the Product Owner and the Developers as they learn more about the product, the users, the market, and the technology. The Product Backlog is updated whenever new information and insights emerge, which can happen at any time during the product development process. Therefore, option C is the best answer.
Option A is not correct because the Daily Scrum is not a status meeting, but rather a time-boxed event for the Developers to inspect their progress towards the Sprint Goal and adapt their Sprint Backlog accordingly. The Product Owner does not need to update the Product Backlog after the Daily Scrum, unless there is a significant change in the product vision, strategy, or value proposition that affects the Product Backlog items.
Option B is not correct because the Sprint Retrospective is not a time to update the Product Backlog, but rather a time-boxed event for the Scrum Team to inspect their way of working and identify potential improvements. The Product Owner does not need to update the Product Backlog before the Sprint Retrospective, unless there is a need to communicate a change in the Product Goal or the product roadmap that affects the Product Backlog items.
Option D is not correct because the Sprint Planning is not a time to know how much work will have to be done in the Sprint, but rather a time-boxed event for the Scrum Team to collaborate on selecting and planning the Product Backlog items that will deliver the Sprint Goal. The Product Owner does not need to update the Product Backlog before the Sprint Planning, unless there is a need to reorder or clarify the Product Backlog items that are the most valuable and relevant for the upcoming Sprint. References:
Professional Scrum Product Owner II Assessment
Understanding and Applying the Scrum Framework
Managing Products with Agility
What is a Product Backlog?
Product Backlog Explained
Who is accountable for clearly expressing Product Backlog items?
(choose the best answer)
The Developers.
The Scrum Master.
The Scrum Master, or the Scrum Master may have the Developers help.
The Product Owner, but the Product Owner may appoint a proxy on the Scrum Team to do the work.
The Scrum Master, or the Scrum Master may have the Product Owner do it.
The Product Owner is accountable for effective Product Backlog management. The 2020 Scrum Guide states that this includes creating and clearly communicating Product Backlog items .
So the accountable person is clearly the Product Owner .
Why D is the best answer:
Option D identifies the Product Owner , which is the key official answer. However, the wording about a “proxy” is not the exact Scrum Guide wording. The Scrum Guide says the Product Owner may delegate the responsibility to others , but the Product Owner remains accountable . So while the option is not perfectly phrased, it is still the best available answer because it correctly names the Product Owner as the accountable person.
Why A is incorrect:
Developers may help refine, clarify, and break down Product Backlog Items, but they are not the accountable role for clearly expressing them.
Why B is incorrect:
The Scrum Master is not accountable for clearly expressing Product Backlog Items. The Scrum Master helps the Scrum Team understand Scrum and supports effectiveness, but Product Backlog accountability belongs to the Product Owner.
Why C is incorrect:
This wrongly assigns accountability to the Scrum Master. That is not supported by the Scrum Guide.
Why E is incorrect:
Again, this incorrectly makes the Scrum Master accountable.
Important correction to the option wording:
The official Scrum wording is not “appoint a proxy.” The correct concept is:
The Product Owner may delegate the work , but remains accountable .
An analysis of the customers for your product reveals that you have several different kinds of customers that use your product in very different ways. What should you do with this insight?
(Choose the best answer)
Evaluate building different products to better serve each group.
Do nothing: invest in future features to attract new customers and drive revenue growth.
Keep a single product, but market to the groups differently.
Keep a single product, but make sure each release has something for each group.
In Scrum, the Product Owner is responsible for maximizing the value of the product by understanding and addressing customer needs effectively. When faced with multiple customer segments using the product in different ways, the best approach is to market the product differently to each group rather than fragmenting the product into multiple versions or ignoring existing customers.
Option A (Evaluate building different products): While segmentation can sometimes justify creating multiple products, it adds complexity in development, maintenance, and resource allocation. Scrum focuses on delivering incremental value in a single product rather than splitting efforts across multiple versions unless there ' s a strong business case.
Option B (Do nothing and invest in future features): This is a risky and reactive approach. Ignoring existing customer groups and only investing in attracting new customers can lead to customer churn and dissatisfaction. A Product Owner should aim for continuous engagement with existing customers to ensure long-term success.
Option C (Keep a single product, but market differently to each group) [Correct Answer]: This aligns with Agile and Scrum principles because it allows the Product Owner to maintain a single product backlog while tailoring marketing messages for different user segments. It helps maximize value delivery without increasing complexity. Instead of fragmenting the product itself, communication and positioning strategies are adjusted to better resonate with different customer types.
Option D (Ensure each release has something for each group): While inclusivity in releases is valuable, forcing every release to cater to all groups can lead to inefficient backlog prioritization. Instead, the Product Owner should balance priorities based on value delivery and strategic goals rather than trying to satisfy all user segments in every release.
What things might a Product Owner focus on to ensure the product is useful and delivers value? (Choose all that apply)
How swiftly and easily the product can be consumed and used by the customers.
The size of the product in " lines of code " .
How much of the functionality of the product is being utilized.
Direct customer feedback.
Minimizing changes to project scope.
A Product Owner’s primary responsibility is to maximize the value of the product by ensuring that it is useful, relevant, and meets customer needs. The correct focus areas include usability, functionality, and customer feedback.
Analysis of Answer Choices:
A. How swiftly and easily the product can be consumed and used by customers. (Correct)
A usable, accessible product enhances customer satisfaction and adoption.
Ease of use is a key factor in delivering value.
B. The size of the product in " lines of code " . (Incorrect)
Code volume does not determine value. More lines of code may indicate inefficiency, not quality.
The focus should be on delivering meaningful functionality, not measuring size.
C. How much of the functionality of the product is being utilized. (Correct)
Tracking feature usage helps determine which functionalities provide real value.
Low usage may indicate unnecessary features or poor usability, guiding future improvements.
D. Direct customer feedback. (Correct)
Customer feedback is crucial for validating assumptions and guiding product development.
Frequent interaction with customers helps ensure the product meets real needs.
E. Minimizing changes to project scope. (Incorrect)
Agility requires adaptability. Changes to scope are often necessary to meet evolving market demands.
A Product Owner should welcome changes if they enhance product value.
Key Scrum Guide Principles Supporting These Answers:
" The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. "
" The Product Backlog is a dynamic artifact that evolves as the product and its environment change. "
" Empirical process control relies on regular customer feedback to inspect and adapt. "
Conclusion:
A Product Owner should focus on usability, functionality usage, and customer feedback to ensure the product is valuable and useful. Minimizing scope changes or measuring code size are not valid strategies in Agile product development.
Why does a Scrum Team need a Sprint Goal?
(choose the best answer)
A Sprint Goal ensures that all the Product Backlog items selected for the Sprint are implemented.
A Sprint Goal only gives purpose to Sprint 1.
The Scrum Team is more focused through a common yet specific goal.
Sprint Goals are not valuable. Everything is known from the Product Backlog.
Let ' s break down why the correct answer is C and why the others are incorrect, referencing the Professional Scrum Product Owner™ II (PSPO II) objectives and associated competencies:
C. The Scrum Team is more focused through a common yet specific goal.
Verification: This is the correct answer and aligns perfectly with the purpose of a Sprint Goal as defined in the Scrum Guide and emphasized within the PSPO II competencies.
Explanation and References:
Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the Scrum Framework - Empiricism
The Sprint Goal promotes transparency within the team about what they are trying to achieve during the Sprint.
It provides a basis for inspection during the Sprint, allowing the team to adapt their plans based on progress toward the Sprint Goal.
Professional Scrum Competency: Managing Products with Agility - Forecasting and Release Planning
The Sprint Goal helps the team focus on achieving a specific, valuable outcome each Sprint.
It provides a basis for forecasting what can be achieved in the Sprint.
Professional Scrum Competency: Managing Products with Agility - Product Value
The Sprint Goal should be aligned with maximizing product value, providing a clear link between the work done in the Sprint and the overall product vision.
Scrum Guide: The Scrum Guide states, " The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Developers 1 on why it is building the Increment. 2 [...] During Sprint Planning the Scrum Team also crafts a Sprint Goal. The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. " 3 This clearly emphasizes that the Sprint Goal provides focus and guidance.
A. A Sprint Goal ensures that all the Product Backlog items selected for the Sprint are implemented.
Verification: This is incorrect.
Explanation and References:
Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the Scrum Framework - Empiricism
Scrum acknowledges that the plan for the Sprint (what Product Backlog items are chosen) may change as the team learns more during the Sprint.
The Sprint Goal is the commitment, and while the team strives to complete the selected Product Backlog items, the primary focus is on achieving the Sprint Goal, even if it means adapting the plan.
Scrum Guide: While the selected Product Backlog items are the initial plan, the Scrum Guide states, " The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. " This implies that the focus is on the coherent function (represented by the Sprint Goal), not necessarily the completion of every single Product Backlog item.
B. A Sprint Goal only gives purpose to Sprint 1.
Verification: This is incorrect.
Explanation and References:
Professional Scrum Competency: Managing Products with Agility - Forecasting and Release Planning
Every Sprint should have a Sprint Goal, providing ongoing direction and focus for the team.
Scrum Guide: The Scrum Guide explicitly states that a Sprint Goal is crafted during Sprint Planning, implying that it ' s a necessary component of every Sprint, not just Sprint 1.
D. Sprint Goals are not valuable. Everything is known from the Product Backlog.
Verification: This is incorrect.
Explanation and References:
Professional Scrum Competency: Managing Products with Agility - Product Value
Sprint Goals are crucial for maximizing product value by providing focus and ensuring the team is working on the most important aspects in each Sprint.
Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the Scrum Framework - Empiricism
The Sprint Goal provides context and purpose beyond the individual Product Backlog items. It helps the team understand the " why " behind the work.
Scrum Guide: The Scrum Guide ' s emphasis on the Sprint Goal throughout the Sprint lifecycle (planning, daily Scrum, review, retrospective) demonstrates its importance.
In conclusion, the Sprint Goal serves as a unifying and focusing mechanism for the Scrum Team, promoting commitment to a specific outcome within each Sprint and is, therefore, a crucial element for successful Scrum implementation, aligning perfectly with the PSPO II competencies and the Scrum Guide.
Which activities will a Product Owner likely engage in during a Sprint?
(choose the best three answers)
Reorder items in the Product Backlog.
Answer questions from the Developers about items in the current Sprint.
Update the Sprint burndown chart.
Prioritize the Developer ' s tasks.
Gather information and opinions from stakeholders.
Run the Daily Scrum.
A. Reorder items in the Product Backlog: The Product Owner is responsible for ordering the Product Backlog to maximize value12.
B. Answer questions from the Developers about items in the current Sprint: The Product Owner is engaged throughout the sprint, answering questions on how things are supposed to function and look4.
E. Gather information and opinions from stakeholders: Gathering information and opinions from stakeholders is a key activity for the Product Owner, as it helps in understanding the value and ordering the Product Backlog
If a Scrum Team uses Product Backlog refinement, when should it occur?
(choose the best two answers)
The Product Owner takes the time between the Sprints to do it.
Business Analysts in the organization should do this work for the Scrum Team 1-2 Sprints ahead of the development Sprints.
The Product Owner and the Developers can refine the Product Backlog duringany Sprint as needed, ideally in advance of the upcoming Sprint.
The Product Owner must do this as essential work in Sprint 0.
The Product Owner and the Developers do it in the current Sprint if they havebeen unable to do it in preceding Sprints.
Product Backlog refinement is an ongoing activity that can occur at any time during a Sprint, as needed. The Product Owner and Developers collaborate on this task, ideally in advance of the upcoming Sprint to ensure clarity and readiness of the work ©. If refinement has not been done in preceding Sprints, it should be done in the current Sprint to maintain the flow of valuable work (E). This approach is consistent with the Scrum principle of continuous improvement and the iterative, incremental nature of Scrum12.
You have more ideas for new products than you have money to invest. What should you do?
(choose the best answer)
Fund small experiments to test the proposed ideas and assumptions, then evaluateresults.
Rank proposals by market potential (Unrealized Value) and fully fund as many as youcan.
Invest in the proposals that have the highest projected Current Value for the nextyear.
Invest in all of them, but at proportionally lowered amounts, and see how they allperform.
According to the Professional Scrum Product Owner™ II guide, one of the key competencies of a Product Owner is to validate product assumptions and hypotheses using empirical evidence1. This means that instead of investing a lot of money and time into building a product based on unproven ideas, the Product Owner should conduct small experiments to test the viability, desirability, and feasibility of the product2. These experiments can take various forms, such as prototypes, mockups, surveys, interviews, landing pages, etc. The goal is to gather feedback from real or potential users and customers, and measure the outcomes against predefined success criteria3. Based on the results of the experiments, the Product Owner can then decide whether to persevere, pivot, or terminate the product idea4. This approach helps to reduce the risk of wasting resources on products that nobody wants or needs, and to focus on the most valuable and promising ideas.
As Sprint Planning progresses, the workload is getting to be greater than the Developer ' s
capacity to meet the Sprint Goal. Which actions make the most sense to take?
(choose the best two answers)
Potentially remove or change selected Product Backlog items.
The Developers ensure that the Product Owner is aware, start the Sprint andmonitor progress.
Cancel the Sprint.
Start the Sprint and recruit additional Developers.
Ask the Developers to work overtime for this Sprint and promise that it will nothappen again.
According to the Scrum Guide, the Developers are accountable for creating a plan for the Sprint, which includes selecting the Product Backlog items that they can deliver in the Sprint1. If they realize that the workload is too high, they have two options: either reduce the scope or increase the capacity. Reducing the scope means removing or changing some of the Product Backlog items, in agreement with the Product Owner, so that the Sprint Goal can still be achieved2. Increasing the capacity means adding more Developers to the team, but this is not recommended, as it can disrupt the team dynamics, lower the quality, and increase the communication overhead3. Therefore, the best actions to take are A and B, as they respect the self-organization and collaboration of the Scrum Team, and allow them to deliver a valuable and potentially releasable Increment at the end of the Sprint4.
A " cone of uncertainty " can be used to do what?
(choose the best answer)
Represent the relative level of difficulty for predicting the velocity of individual teammembers.
Rapidly identify and prioritize all uncertainties.
Determine whether to cut quality, similar to the " Iron Triangle " of projectmanagement.
Visualize the uncertainty of the potential value that a Scrum Team delivers over time.
A “cone of uncertainty” is a graphical representation of the evolution of the amount of uncertainty during a project. It shows that at the beginning of a project, there is a high degree of variability and unpredictability in the estimates of the scope, cost, time, and value of the product. As the project progresses, more information and feedback are gathered, and the uncertainty decreases, reaching zero when the product is delivered and validated. A “cone of uncertainty” can be used to visualize the uncertainty of the potential value that a Scrum Team delivers over time, and to guide the empirical process of inspection and adaptation. By using a “cone of uncertainty”, a Scrum Team can:
Align the expectations of the stakeholders and customers with the reality of the complex and dynamic environment.
Avoid making premature or unrealistic commitments based on inaccurate or incomplete estimates.
Embrace change and experimentation as opportunities to learn and deliver more value.
Inspect the actual value delivered and the feedback received, and adapt the product vision, strategy, and backlog accordingly.
Forecast the range of possible outcomes and the level of confidence for each Sprint and release.
The other options are not valid uses of a “cone of uncertainty”. A “cone of uncertainty” does not represent the relative level of difficulty for predicting the velocity of individual team members, as velocity is a measure of the amount of work done by the whole Scrum Team, not by individuals. A “cone of uncertainty” does not rapidly identify and prioritize all uncertainties, as uncertainties are not always known or quantifiable, and may change over time. A “cone of uncertainty” does not determine whether to cut quality, similar to the “Iron Triangle” of project management, as quality is not a variable that can be traded off in Scrum, but a non-negotiable aspect of the Definition of Done and the value proposition of the product.
Professional Scrum Product Owner™ II Certification
Managing Products with Agility
Cone of Uncertainty - Wikipedia
A user satisfaction gap exists when there is a difference between:
(choose the best two answers)
The total market size.
The user ' s desired outcome.
The market share of the product.
The user ' s actual experience.
A user satisfaction gap exists when there is a difference between what the user expects from a product or service and what the user actually experiences12. The user’s desired outcome is the goal or benefit that the user wants to achieve by using the product or service3. The user’s actual experience is the perception and evaluation of the product or service by the user4. If the user’s actual experience does not meet or exceed the user’s desired outcome, the user will be dissatisfied and may switch to a different product or service. References:
1: Identifying and Closing the Customer Satisfaction Gap
2: Find the Gaps in Your User Experience
3: [Outcome-Driven Innovation]
4: [User Experience]
: Measure Business Opportunities with Unrealized Value
A Product Owner is needed for every:
(choose the best answer)
Product.
Portfolio.
Program.
All of the above.
The Product Owner is the sole person accountable for managing the Product Backlog and ensuring the value of the work the Scrum Team performs. The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner1. The Product Owner is responsible for the product and its outcome2.
A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers. A product could be a physical product, a software product, a service, a project, or something else3. A product has a product vision, which is the overarching goal of the product, the reason for creating it, and the impact it should have on its customers and users4.
A portfolio is a collection of products or projects that are aligned with a strategic goal or an organizational unit5. A program is a group of related projects or products that are managed in a coordinated way to obtain benefits and control not available from managing them individually. A portfolio or a program may have a portfolio or program manager, who is responsible for overseeing the alignment, prioritization, and governance of the portfolio or program . However, these roles are not equivalent to the Product Owner role, as they do not have the same accountabilities and authorities as the Product Owner.
Therefore, the correct answer is that a Product Owner is needed for every product, not for every portfolio or program. References: 1: Scrum Guide 2: Understanding and Applying the Scrum Framework 3: Managing Products with Agility 4: [Product Vision] 5: [Portfolio] : [Program] : [Portfolio Management] : [Program Management]
What are the accountabilities of a Tester on a Scrum Team?
(choose the best two answers)
Finding bugs to assure quality.
Creating code coverage reports for the test manager.
Checking the work of the Developers.
There is no specific tester role.
Everyone on the Scrum Team is accountable for the quality of the product.
According to the Scrum Guide, the Scrum Team consists of one Scrum Master, one Product Owner, and Developers. There is no distinction between different types of Developers, such as testers, programmers, designers, etc. The Developers are the people who deliver a potentially releasable Increment of “Done” product at the end of each Sprint. They are accountable for creating and adhering to the Definition of Done, ensuring technical excellence and good design, and collaborating with the Product Owner to maximize value1. Therefore, everyone on the Scrum Team is responsible for ensuring the quality of the product, and there is no specific tester role. However, this does not mean that testing skills are not needed or valued. On the contrary, testing is an essential activity that supports the team and critiques the product throughout the development process2. A professional tester can contribute to the Scrum Team by coaching the team on testing techniques, tools, and practices, helping the team to define clear and unambiguous acceptance criteria, challenging the team to consider different scenarios and edge cases, creating and executing test plans, and providing feedback on the product’s usability, performance, security, and other aspects3. A professional tester can also collaborate with the Product Owner to ensure that the product meets the expectations and needs of the stakeholders and users.
An effective Product Owner must:
(choose the best answer)
Ensure that every stakeholder need is met.
Be the " expert " opinion for all Product Backlog items.
Ensure that the team is as productive as possible.
Be the single point of contact for all stakeholders.
All of the above.
None of the above.
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. References:
1: The Scrum Guide
2: Product Owner Learning Path
3: Product Owner Competencies
4: Evidence-Based Management
5: Product Strategy
Choose the two measurements which provide the best indicator to the Product Owner that
value is being delivered.
(choose the best two answers)
Customer satisfaction.
On-time release trends.
Velocity.
Frequency of feature use.
Scope implemented.
According to the Professional Scrum Product Owner™ II (PSPO II) guidelines, the best indicators of value delivery are those that reflect the product’s impact on customers and its usage in the market.
Customer satisfaction (Option A) is a direct measure of how well the product meets customer needs and expectations. High customer satisfaction is a strong indicator that the product is delivering value1.
Frequency of feature use (Option D) provides insights into which features are most valuable to users by showing how often they are used. This metric helps Product Owners understand user behavior and prioritize features that deliver the most value1.
On-time release trends (Option B) and velocity (Option C) are more about the process and efficiency of the development team rather than direct indicators of value to the customer. Scope implemented (Option E) measures the amount of work done but does not necessarily correlate with customer value. Therefore, options A and D are the best choices for measuring value delivery as per the PSPO II resources.
You have been a Product Owner at a new company for a few weeks. It has become clear to you
that many people, both inside and outside the Scrum Team, expect close involvement in the
decisions that you, as a Product Owner, are accountable for.
As a result, you find that it takes too long to make decisions. Which of the following are
reasonable options you could take?
(choose the best three answers)
Start making all the decisions without consulting the others who have expressedinterest.
Allow other members of the Scrum Team and stakeholders to continue makingdecisions they are not accountable for; documenting which decisions do notdeliver the intended value.
Create and share a delegation board that displays your decision-making areasand work with your Scrum Team to clarify decision making accountability andresponsibility.
Work with your Scrum Master to better understand what next steps you can taketo move the company ' s understanding of product ownership up in the maturitycurve towards Entrepreneur.
Demonstrate, with the help of data, how long it is taking you to make decisionsand the impact that the long decision-making cycle has on delivering value to thecustomer.
As a Product Owner, you are responsible for making decisions that maximize the value of the product and align with the product vision and strategy. However, you also need to collaborate with the Scrum Team and the stakeholders, and respect their input and feedback. Making decisions without consulting them or allowing them to make decisions they are not accountable for can lead to confusion, conflict, and waste. Therefore, options A and B are not reasonable.
Option C is a reasonable option because it helps you communicate your decision-making areas and delegate some decisions to the appropriate level of the organization. A delegation board is a tool that shows who has the authority to make which decisions, and how much involvement is expected from others. By creating and sharing a delegation board, you can clarify your role as a Product Owner, empower the Scrum Team and the stakeholders, and reduce the time and effort spent on decision making.
Option D is also a reasonable option because it helps you improve the company’s culture and mindset towards product ownership. As a Product Owner, you need to act as an entrepreneur, who is able to innovate, experiment, and validate assumptions. However, not all organizations are ready to support this kind of product ownership, and some may have a more traditional or bureaucratic approach. Working with your Scrum Master, you can identify the gaps and barriers that prevent you from being an effective Product Owner, and take steps to overcome them. For example, you can educate and coach the organization on the benefits of agile product management, create a shared product vision and roadmap, and foster a culture of trust and transparency.
Option E is another reasonable option because it helps you demonstrate the value of your decisions and the cost of delay. As a Product Owner, you need to use data and evidence to support your decisions and measure their impact. By showing how long it is taking you to make decisions and how that affects the delivery of value to the customer, you can justify your choices and persuade others to support them. You can also use data to identify the most important and urgent decisions, and prioritize them accordingly. This way, you can avoid analysis paralysis and focus on delivering value faster and more frequently.
As an investor or shareholder, which of the following measures might give you insight about
whether a product is delivering value?
(choose all that apply)
Revenue per Employee.
Market Share.
The average selling price as compared to close competitors.
Product profitability.
The weekly velocity of the Developers.
A, B, C, and D are correct because they are all measures of the value that a product delivers to the customers and the organization1. Revenue per Employee indicates the efficiency and productivity of the product development2. Market Share shows the competitive advantage and customer satisfaction of the product3. The average selling price as compared to close competitors reflects the perceived value and quality of the product4. Product profitability measures the financial return and viability of the product5. E is incorrect because the weekly velocity of the Developers is not a measure of value, but a measure of output and capacity. Velocity does not indicate whether the product is meeting the needs and expectations of the customers and the stakeholders.
You are the Product Owner at a small company with a single product. You have authority over
pricing, promotion, and how much is invested in new features or capabilities. Your product has:
. High Current Value - as indicated by high customer satisfaction.
. High Unrealized Value - as indicated by low market share.
Using those two data points, what is the first action you should take to increase the business
performance of the product?
(choose the best answer)
Increase the number of product features to attract a greater number of customers.
Release an identical product to market, but give it a new product name.
Drop the price for the product to attract a greater number of customers.
Improve the marketing of the product to attract a greater number of customers.
= 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. References := Professional Scrum Product Owner™ II Certification, Managing Products with Agility, Evidence-Based Management
When the Product Owner is too busy to work with all of the teams in a multi-team product
development effort, which strategy will help them?
(choose the best answer)
Add component team Product Owners.
Communicate a clear Product Goal and delegate some activities to the Developers.
Enlist the Program Management Office to help coordinate work.
Assign sub-Product Owners to each Scrum Team.
All of the above.
The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. They are also accountable for effective Product Backlog management, which includes clearly expressing Product Backlog items, ordering them to best achieve goals and missions, ensuring that the Product Backlog is transparent, visible and understood. The Product Owner may do the above work or may delegate the responsibility to others. However, the Product Owner remains accountable1.
When working with multiple Scrum Teams on the same product, the Product Owner should ensure that there is a shared understanding of the Product Goal among all the teams and stakeholders. The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next2. The Product Owner should also collaborate with the Developers to create and refine Product Backlog items that are valuable, feasible, and testable. The Developers are accountable for creating a plan for the Sprint, the Sprint Backlog1. The Product Owner should trust the Developers to self-organize and deliver the most valuable increments possible.
The other options are not recommended strategies for the Product Owner, as they may introduce unnecessary complexity, confusion, and waste. Adding component team Product Owners, enlisting the Program Management Office, or assigning sub-Product Owners may create silos, dependencies, and conflicts among the teams and stakeholders. These roles may also undermine the authority and accountability of the Product Owner, and reduce the transparency and alignment of the Product Backlog. The Product Owner should work with the Scrum Master and the Developers to find ways to optimize the value delivery and collaboration across the teams, rather than creating intermediaries or proxies34. References: 1: Scrum Guide 2: Understanding and Applying the Scrum Framework 3: Managing Products with Agility 4: Evolving the Agile Organization
Copyright © 2014-2026 Certensure. All Rights Reserved