What antipattern might a scrum master fall into during planning poker?
Why this is the correct answer
A common antipattern a Scrum Master might fall into during Planning Poker is influencing the team's estimation. This occurs when the Scrum Master, either intentionally or unintentionally, suggests that a task should have a certain point value or makes comments that steer team members toward choosing a specific estimate. This can lead to biased estimates that do not accurately reflect the team's true perspective on the complexity or effort required for a task.
Another antipattern is allowing the discussion to become too lengthy or unfocused. The purpose of Planning Poker is to quickly reach a consensus on the estimates, but if the Scrum Master does not keep the discussion on track, it can drag on and become inefficient. This wastes valuable time and can cause frustration among team members. The Scrum Master should facilitate the discussion to ensure it remains productive and that the team can move on to other important activities.
Lastly, a Scrum Master might fall into the trap of not encouraging all team members to participate equally. In Planning Poker, it's important that everyone’s opinion is heard to get a well-rounded estimate. If the Scrum Master allows only the more vocal team members to dominate the discussion, quieter members might feel their input is not valued, leading to less accurate estimations and decreased team morale. The Scrum Master should actively ensure that everyone has a chance to contribute.