Which of the following is true about Scrum?(choose all that apply)
Answer(s): A,B,D
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 OwnerTM II CertificationUnderstanding and Applying the Scrum Framework[The Scrum Guide]
The environment in which a product will be used changes and emerges continually. What is the effect on the Product Backlog?(choose the best answer)
Answer(s): B
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 stakeholders. 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 refined. 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 environment. 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 items.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 world. The Product Backlog items are not detailed or fixed upfront, but rather refined and clarified as they get closer to implementation. 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 matures. 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 learnings. The Product Backlog items are not discarded or replaced, but rather refined and updated as the product evolves and changes. 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 Backlog2: Product Backlog Management3: Empiricism4: Stakeholders & Customers5: Product Vision: Product Value: Evidence-Based Management: [Agile Manifesto]: [Product Roadmap]: Product Owner Accountabilities: Sprint Review: Product Backlog Refinement: [User Stories]: [Value Proposition]: [Experiments]
Which of the following are characteristics of a Product Goal?(choose all that apply)
Answer(s): A,B,C,E
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.
Professional Scrum Product Owner II AssessmentUnderstanding and Applying the Scrum FrameworkManaging Products with AgilityScrum Guide 2020 Update - Introducing the Product GoalThe Product Goal explained
In order to justify the price increase of a product, your primary objective should be to:(choose the best answer)
According to the PSPO II resources, a product owner should optimize the value of the product and the work of the Scrum Team. 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 customer. A price increase can be justified if the customer perceives that the product delivers more value than the cost. This can be achieved by enhancing the product quality, functionality, usability, or design, or by providing additional benefits or services to the customer. 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.
1: The Scrum Guide2: User Experience3: Value-Based Pricing4: 8 Techniques to Justify a Price Increase: Justification for a Price Increase: Positioning For Success
The smallest product Increment that is valuable enough to release is one that:(choose the best answer)
Answer(s): A
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 features. An outcome is a change in behavior,attitude, or situation that results from using the product. 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 Goal. 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 conditions.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 customer.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.
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
Post your Comments and Discuss Scrum PSPO II exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the PSPO II content, but please register or login to continue.