Product Backlog

Correct Answer: Encourage the team member to seek assistance through pair programming or swarming techniques.

The correct approach is to promote collaboration within the team by encouraging techniques like pair programming or swarming, as both practices align with the empirical and team-centric nature of Scrum. Assigning the task to another team member could undermine self-organisation and lead to knowledge silos. Halting work on the feature goes against the principle of continuous progress. Presenting an unresolved issue at the Sprint Review is not appropriate, as the focus of the Review is on showcasing completed work and discussing feedback to guide future work.

Correct Answer: Coach the Product Owner on effectively refining and prioritizing the backlog, engaging the team for insights.

As a Scrum Master, facilitating the understanding and effectiveness of the Scrum framework within the team is crucial. Coaching the Product Owner on maintaining a refined and prioritized Product Backlog is a part of this role, ensuring transparency and clarity for the Development Team. Updating the backlog independently or ignoring its current state undermines the collaborative and self-organizing principles of Scrum. Organizing a full-day workshop may seem beneficial but can overwhelm the team and divert focus from ongoing work without addressing the root cause of the backlog being outdated.

Correct Answer: Suggest the team uses the next backlog refinement session to create a more detailed user story, ensuring alignment with the Product Owner.

The correct approach in Scrum involves tackling unclear items in the backlog proactively by the team, ideally in refinement sessions, with a strong emphasis on collaboration and clarity from the Product Owner. Encouraging guesses, delaying clarification, or bypassing the Product Owner's input conflicts with Scrum principles, which strive for clear, continuous communication, and collaboration among the Scrum Team and stakeholders.