Scrum Roles

In Scrum, the Product Owner is the main liaison between the stakeholders and the Development Team. The ScrumMaster should ensure this communication line is respected and uphold the principles of Scrum. They would educate the stakeholders to direct their queries through the Product Owner, as suggested in the first answer. The ScrumMaster wouldn't ignore the requests of the stakeholders, as the third answer suggests, since the stakeholders are important sources of feedback and input. The second answer isn't best because direct communication between stakeholders and the Development Team can risk distractions or misalignments. The last answer is also not ideal; while the ScrumMaster is a facilitator, actively passing queries between stakeholders and the Development Team breaks the established line of communication through the Product Owner and can thus create confusion.

Promoting cross-skilling and self-organization within the team can lead to a more versatile and resilient team. The correct answer suggests a collaborative approach to identify and seize learning opportunities, without forcing members into discomfort or disregarding their interests and current skill levels. The wrong answers either focus too much on maintaining productivity with current skills, enforce unnecessary rotations that might lead to demotivation, or propose an unrealistic expectation of proficiency in multiple areas without addressing the immediate concern of task allocation based on specialization.

The best approach to address a constantly absent product owner in a scrum team is by having the ScrumMaster, who is responsible for ensuring the team lives by the values and practices of Scrum, addressing the issue with the product owner or the person's supervisor. This solution keeps the roles clear and maintains the integrity of the Scrum process. The other options are not the best course of action. The ScrumMaster taking up the role of the Product Owner violates the principle that each role in Scrum is distinct and should not be combined, as different skills, knowledge, and techniques are needed. Having the Development Team continue with the work until the Product Owner can attend could result in work that does not meet the business conditions or the user's needs as the Product Owner represents the voice of the client. Lastly, having the ScrumMaster and the Development Team decide what to do could lead to the team taking a direction that is not aligned with the overall goals and strategy of the business.