Commitment

Correct Answer: Encourage team self-organization to enhance ownership.

In the context of Scrum, encouraging team self-organization is fundamental to enhancing ownership and accountability among team members. When a team self-organizes, members naturally take more responsibility for the completion of tasks, as they have direct input into who does what, how work is managed, and how decisions are made. This leads to a higher level of commitment because team members are directly involved in the planning and execution process, making the outcomes more personal and meaningful to them. In contrast, assigning tasks to team members might clarify responsibilities but can also reduce ownership and motivation, as it takes away the team's autonomy to self-organize. Monitoring daily progress focuses more on oversight than on fostering accountability and commitment through empowerment. Proposing adjustments to the workload in the Sprint Planning is a task-oriented approach that does not directly address team dynamism or member accountability in the same way that encouraging self-organization does.

Correct Answer: Encourage the team to review and adjust their Sprint Planning process to ensure commitments are realistic based on past performance.

The correct answer promotes an adaptive and reflective approach, encouraging the team to learn from past Sprints and adjust their planning process to achieve a realistic commitment level. The wrong answers suggest practices that do not align well with Scrum principles. Increasing the duration of the daily Scrum could reduce efficiency and focus, as the purpose of this event is to quickly discuss what was done, what will be done, and identify impediments. Assigning work undermines the self-organizing nature of the Scrum Team, removing their autonomy over how to meet the Sprint Goal. Detailed hour-by-hour planning introduces a high level of micromanagement and detailed upfront planning that is contrary to the agile principle of responding to change over following a plan.

Correct Answer: The ScrumMaster should foster a safe and trusting environment for the team member to feel comfortable making commitments, perhaps discussing offline

The role of the ScrumMaster is to ensure that the Scrum framework is being adhered to by all team members. This includes fostering an environment where team members feel comfortable and safe in expressing their thoughts and making commitments. If a team member is unwilling to commit to a task during a Sprint Planning meeting, it's the ScrumMaster's responsibility to address this issue. They should work with the team member offline, to provide assurance or to figure out what is impeding the team member from making commitments. On the other hand, making the commitment for the team member or asking the Product Owner to make the commitment is contrary to Scrum principles. Every member of the team is expected to be self-organizing and make professional commitments. Ignoring the problem and moving on is also not an option as it does not resolve the underlying issue and does not promote transparency, one of the pillars of Scrum.