Professional Scrum Master Ii PSM Ii · Free Practice Question Medium

Question 20

During Sprint Planning, the Developers were not able to confidently forecast a Sprint Backlog. However, the Scrum team was able to create a Sprint Goal for the upcoming Sprint. What action should the Scrum Master take? (Choose the best answer)
  • A Postpone the Sprint in order for the Product Owner to refine the Product Backlog to the level needed.
  • B Forecast the most likely Product Backlog items to meet the goal, and discuss why this happened and what changes will make it less likely to happen again in the upcoming Sprint Retrospective.
  • C Extend the Sprint Planning timebox until the Developers can forecast enough items to begin the Sprint.
  • D Request assistance from the technical architect.
Reveal correct answer

Correct answer: B

Explanation

In Scrum, it's common practice for the Scrum Team, including the Product Owner and Developers, to forecast the most likely Product Backlog items to meet the Sprint Goal during Sprint Planning. This involves selecting and committing to a set of Backlog items based on their understanding of the goal and the capacity of the team. Additionally, during the Sprint Retrospective, the team reflects on their performance and identifies opportunities for improvement. Discussing why certain items were or were not completed as forecasted helps the team understand any impediments or challenges they faced during the Sprint. By analyzing these factors, the team can collaboratively determine what changes or adjustments can be made to increase the likelihood of meeting their commitments in future Sprints. Recommending that the Product Owner escalate the issue to higher management without attempting to address the client's concerns directly is wrong because it bypasses the fundamental principles of transparency and collaboration in Scrum. In Scrum, the emphasis is on open communication and problem-solving within the team. By escalating the issue without first attempting to resolve it directly with the client, the Scrum Master misses an opportunity for the team to understand the client's feedback and collaborate on finding solutions. Encouraging the Product Owner to ignore the client's complaints and focus solely on the team's progress disregards the importance of customer feedback in Scrum. The Product Owner's role includes representing the customer and ensuring that the product meets their needs and expectations. Ignoring client complaints can lead to a disconnect between the product and its users, ultimately hindering the team's ability to deliver value. Suggesting shifting the blame onto the Development Team for the product's poor performance contradicts the principle of collective accountability in Scrum. Blaming individuals or teams for problems undermines trust and collaboration within the team. Instead, the focus should be on identifying root causes and finding solutions collaboratively as a team. Advising the Product Owner to withhold information from the client to avoid further complaints goes against the principle of transparency in Scrum. Transparency is essential for building trust and fostering open communication between the Scrum Team and stakeholders. Withholding information can lead to misunderstandings and erode trust, ultimately harming the team's relationship with the client.

Discussion

Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.

You must be logged in to post a comment.

Preparing For

Your Certification?

255+ certifications
Detailed explanations
Free PDF samples

Has All The Questions You Need