Estimation and Planning Game

Correct Answer: Evaluate the team's velocity and make projections based on historical data to set realistic expectations.

The correct answer involves using empirical evidence of what the team has been capable of achieving in the past (their velocity) to make informed decisions about future capacity. This reflects Scrum principles of transparency, inspection, and adaptation. The first wrong answer misguides by suggesting an increase in team size, which could disrupt team dynamics and is not a quick fix. The second wrong answer jeopardizes the product's value by proposing to cut corners on quality, contrary to Scrum's emphasis on maintaining quality. The third wrong answer, while appearing to be collaborative, incorrectly suggests initially agreeing to unrealistic goals with the intention to adjust later, which can lead to disappointment and loss of trust.

Correct Answer: Encourage the team to consider historical velocity as a benchmark while allowing for a constructive conversation about their capacity for more work.

The correct approach involves balancing respect for the team's perspective with a realistic understanding of past performance. Overcommitting can lead to burnout and compromised quality, thus encouraging a realistic, yet open-minded view on capacity is wise. Simply increasing velocity assumptions without basis, creating unrelated buffers, or relying on overly complex calculations detract from the focus on empirical evidence and team morale that Scrum emphasizes.

Correct Answer: Support the team in researching and experimenting with the #NoEstimates approach while ensuring it aligns with Scrum values of commitment, courage, focus, openness, and respect.

While exploring new approaches like #NoEstimates, it is essential to ensure they align with Scrum's fundamental values and principles, particularly around transparency, inspection, and adaptation. The correct answer supports the team in exploring new methods, provided they uphold Scrum values. The wrong answers suggest adopting specific techniques without considering the team's context or exploring their alignment with Scrum values, which may not address the underlying issue with estimation difficulties.