Which statement best describes the Sprint Backlog as the output of the Sprint Planning? (choose the best answer)
Correct Answer: D
Explanation The Sprint Backlog is the output of the Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work. The Scrum Guide states that "The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how)."1 The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned. The Sprint Backlog makes visible all the work that the Developers identify as necessary to meet the Sprint Goal.1 References: 1: The Scrum Guide2, page 15 2: The Scrum Guide
Question 72
It is allowed to change the scope during a Sprint.
Correct Answer: A
Question 73
You are the Scrum Master for four Scrum Teams working from the same Product Backlog Several of the Developers come to you complaining that work identified for the upcoming two Sprints will require full-time commitment from a specialist who is external to the teams. What should the Scrum Master consider in this situation? (choose the best two answers)
Correct Answer: B,D
According to the documentation of Professional Scrum Product Owner (PSPO I), the Scrum Master should consider the following two answers in this situation: B) The benefit of Developers figuring out a solution for themselves. D) The ability of the Scrum Teams to produce integrated Increments. The reason for choosing these two answers is that they align with the Scrum Master's role as a servant leader, coach, and facilitator of the Scrum Team12. The Scrum Master should not interfere with the team's autonomy and creativity, but rather support them in achieving their goals and delivering value to the stakeholders12. The Scrum Master should also ensure that the team can work together effectively and deliver a potentially releasable Increment at the end of each Sprint12. The other two answers are not as relevant or appropriate for this situation: A) The need to have enough work to keep all Developers busy. C) The desire to maintain a stable velocity. The need to have enough work to keep all Developers busy is not a valid reason for involving an external specialist in the Scrum Team12. The Scrum Team should be self-organizing and cross-functional, meaning that they can decide how to best accomplish their tasks without depending on external resources or expertise12. Moreover, having too much work can lead to scope creep, which can compromise the quality and value of the product12. The desire to maintain a stable velocity is also not a valid reason for involving an external specialist in the Scrum Team12. Velocity is a measure of how much work can be completed by the team in a given time period, such as a Sprint or a release cycle12. It is not a fixed or objective number, but rather depends on various factors such as team size, complexity, skills, motivation, etc.12. Therefore, having an external specialist does not guarantee that the team will maintain a stable velocity, but rather may introduce additional challenges such as communication barriers, coordination issues, dependency risks, etc.12. I hope this answer helps you understand how to apply your knowledge of Professional Scrum Product Owner (PSPO I) objectives and content in this situation. If you have any further questions or feedback, please let me know. Thank you for using Bing! Reference: Professional Scrum Product Owner (PSPO I) Study guide and documents https://www.scrum.org/assessments/professional-scrum-product-owner-i-certification?check_logged_in=1 https://www.scrum.org/professional-scrum-competencies/understanding-and-applying-scrum-framework https://www.scrum.org/resources/professional-scrum-competency-developing-people-and-teams https://www.scrum.org/professional-scrum-competencies/managing-products-with-agility
Question 74
How often should Scrum Team membership change? (choose the best answer)
Correct Answer: D
The Scrum Team membership should change as needed, but not too frequently, as it may affect the team's ability to deliver value and maintain a high level of collaboration and self-organization. The Scrum Guide states that "Optimal Development Team size is small enough to remain nimble and large enough to complete significant work within a Sprint. Fewer than three Development Team members decrease interaction and results in smaller productivity gains. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful."1 Therefore, the Scrum Team should consider the impact of changing its membership on its productivity and performance, and balance the need for stability and flexibility. Reference: 1: The Scrum Guide2, page 6 2: The Scrum Guide
Question 75
When can Developers cancel a Sprint? (choose the best answer)
Correct Answer: C
According to the Scrum Guide, a Sprint can be canceled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be canceled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be canceled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense. Developers cannot cancel a Sprint on their own, even if they face challenges or difficulties with the selected Product Backlog items, the functional expectations, the technical dependencies, or the Product Owner's availability. Instead, they should collaborate with the Product Owner and the Scrum Master to find the best way to deliver value within the Sprint and adapt to the changing situation. Reference: The Scrum Guide Understanding and Applying the Scrum Framework Professional Scrum Product Owner I Certification
