Scrum Roles

Correct Answer: It's the Development Team's responsibility to resolve their own technical issues and disagreements.

In Scrum, the Development Team is self-organizing, meaning it has autonomy to decide how to do its work. Therefore, the Development Team members are primarily responsible for resolving any technical difficulties or disagreements that arise. The other responses are not correct because the Product Owner's primary responsibility is to manage the product backlog, but not to dictate technical decisions. The ScrumMaster's role is to coach and support the team, but not to directly intervene in technical issues. Stakeholder's typically do not have a direct role in the day-to-day technical decision-making process. Team autonomy is an essential principle of Scrum, and any other interference in this space undermines the autonomy of the team.

Correct Answer: Explain the role of a ScrumMaster to the team and tell them it is important for you to focus on that.

The key role of a ScrumMaster in Scrum methodology is not to perform the task of a developer but to work as a facilitator who helps the team to remove impediments while following Scrum practices. Their main aim is to ensure that the team is fully functional and productive. Thus, the appropriate response here would be to explain the role of a ScrumMaster to the team and remind them it is important for you to focus on that role, rather than performing the tasks of a developer. The option of starting to code and develop along with the team is not recommended because it diverts from the actual role of a ScrumMaster. Similarly, refusing outright without explaining your role is not constructive and does not help educate the team about the Scrum framework. The option of agreeing but only developing during free time is also not feasible because a ScrumMaster's role demands full-time commitment intended for helping the team adhere to Scrum practices instead of coding.

Correct Answer: Schedule a dedicated session with the Product Owner to discuss the impact of their absences and collaboratively find a solution.

The primary approach should focus on resolving the issue by addressing the absence of the Product Owner directly and seeking a collaborative solution to ensure their participation in sprint planning. Assigning a proxy, prioritizing backlog items without the Product Owner, or deferring decisions are not ideal solutions as they can lead to misunderstandings, misplaced priorities, and reduced Product Owner accountability.