How much of the Sprint Backlog must be defined during Sprint Planning? (choose the best answer)
Correct Answer: A
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal1. The Sprint Backlog is a forecast by the Developers about what functionality will be in the next Increment and the work needed to deliver that functionality into a "Done" Increment2. The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum2. The Developers modify the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint. This emergence occurs as the Developers work through the plan and learn more about the work needed to achieve the Sprint Goal2. The Sprint Backlog is not a commitment to deliver a fixed scope of work, but rather a forecast of what the Developers believe they can do in the Sprint3. Therefore, the Sprint Backlog does not need to be fully defined during the Sprint Planning, but only enough so the Developers can create a realistic forecast of what they can do during the Sprint. Reference: 1: Sprint Backlog, 2: The Scrum Guide, 3: Commitment vs. Forecast
Question 12
When is the Sprint Backlog created? (choose the best answer)
Correct Answer: C
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. During Sprint Planning. * Verification: This is the correct answer. * Explanation and References: * Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the Scrum Framework - Scrum Events * Sprint Planning is the event where the Scrum Team collaboratively plans the work for the upcoming Sprint. Creating the Sprint Backlog is a key part of this event. * Professional Scrum Competency: Managing Products with Agility - Forecasting & Release Planning * The Sprint Backlog represents the team's forecast of what they believe they can deliver in the Sprint to achieve the Sprint Goal. This forecasting occurs during Sprint Planning. * Scrum Guide: The Scrum Guide states, "The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team. [...] Sprint Planning answers the following questions: What can be Done this Sprint? How will the chosen work get done?" The answer to the second question results in the creation of the Sprint Backlog. * A. During the Sprint. * Verification: This is incorrect. * Explanation and References: * Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the Scrum Framework - Scrum Events * While the Sprint Backlog can be updated during the Sprint as the Developers learn more, it is initially created before the Sprint starts, during Sprint Planning. * Scrum Guide: The Scrum Guide says "The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum." This means that Sprint backlog is already created before sprint starts. * B. Prior to Sprint Planning. * Verification: This is incorrect. * Explanation and References: * Professional Scrum Competency: Understanding and Applying the Scrum Framework - Applying the Scrum Framework - Scrum Events * The Sprint Backlog is created during Sprint Planning through collaboration between the Developers and the Product Owner. Before Sprint Planning, the Product Owner prepares a prioritized Product Backlog, but this is not the Sprint Backlog. * Scrum Guide: The Sprint Backlog emerges from the discussion and negotiation that happens during Sprint Planning. It is not pre-defined. * D. At the beginning of the project. * Verification: This is incorrect. * Explanation and References: * Professional Scrum Competency: Managing Products with Agility - Forecasting & Release Planning * The Sprint Backlog is specific to each Sprint and is created at the beginning of each Sprint, not at the beginning of the entire project. * Scrum Guide: Scrum is iterative and incremental. Planning the work for the entire project upfront is not in line with Scrum principles. The Sprint Backlog is created anew during each Sprint Planning event. In conclusion, the Sprint Backlog is created during Sprint Planning, where the Scrum Team collaboratively decides what work they will undertake in the upcoming Sprint and how they will accomplish it, aligning with the PSPO II competencies and the Scrum Guide.
Question 13
You are the Product Owner for a product with diverse stakeholders with differing opinions that sometimes conflict. Your Director of Marketing strongly believes that you should add a major new feature to reach a new market. Your CEO believes that the new feature is too expensive and thinks you should focus on other features to make existing customers happier. The CEO says that as Product Owner it is ultimately your decision. You think both perspectives have merit, but you cannot do both. How should you proceed? (choose the best answer)
Correct Answer: A
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. References := Scrum Guide, Managing Products with Agility, Evidence-Based Management
Question 14
Which preferred Product Owner stance helps people to align around the product vision and get people excited to join the case? (choose the best answer)
Correct Answer: A
Question 15
A Product Owner - Jame is working with the firm's stakeholders. All stakeholders confirm that their features are critical to the profit gain. They urge Jame for the release. What should Jame do? (choose the best answer)
