The Daily Scrum is a time-boxed event that allows the Developers to inspect progress toward the Sprint Goal and adapt their plan as necessary. This daily inspection and adaptation ensure the team stays aligned and on track to meet their objectives.

According to the 2020 Scrum Guide :

The Developers inspect how progress is trending toward completing the work in the Sprint Backlog.

They adapt their work plan based on challenges, progress, or new information.

Why the other options are incorrect:

B. Assign tasks: Tasks are not assigned in Scrum. Developers are self-organizing and decide collaboratively how to accomplish their work.

C. Demo the changes to Stakeholders: Demos occur during the Sprint Review, not the Daily Scrum.

D. Estimate the pending work: While work may be discussed, the Daily Scrum is not used for estimation purposes.

The Scrum Master is accountable for ensuring Scrum is understood and enacted. They are responsible for coaching the Scrum Team and the organization in adopting Scrum practices and principles. The Scrum Master acts as a servant leader, guiding the team and stakeholders in understanding and applying Scrum effectively to deliver value.

According to the 2020 Scrum Guide , the Scrum Master is accountable for:

Establishing Scrum as defined in the Scrum Guide.

Helping everyone understand Scrum theory and practice.

Removing impediments and fostering an environment where Scrum can thrive.

Why the other options are incorrect:

A. Developers: Developers are accountable for creating the Increment but not for ensuring Scrum is understood across the organization.

B. Product Owner: The Product Owner is responsible for managing the Product Backlog and ensuring value delivery, not for ensuring Scrum adoption.

D. Project Sponsor: There is no role of "Project Sponsor" in Scrum.

When a team member refuses to participate in Sprint Planning, the Scrum Master should first meet individually to address their concerns . Understanding the root cause of their reluctance can help the Scrum Master guide them toward recognizing the value of the event. This approach demonstrates respect and a willingness to resolve the issue constructively.

According to the 2020 Scrum Guide , the Scrum Master is responsible for:

Coaching team members on the importance of Scrum events, such as Sprint Planning.

Fostering collaboration and ensuring all team members understand their role and responsibilities in achieving the Sprint Goal.

Why the other options are incorrect:

A. Ask for management's assistance: Involving management should be a last resort. The Scrum Master should first attempt to resolve the issue directly with the team member.

B. Mandate attendance: Forcing participation without addressing the underlying concerns could lead to disengagement and resentment.

C. Discuss the importance of team work: While teamwork is important, addressing the individual's specific concerns first is a more targeted and effective approach.

When Developers ask for help or admit they do not know something, they demonstrate Courage , one of the five Scrum Values. It takes courage to be open about challenges or limitations and seek assistance, as it fosters collaboration, transparency, and trust within the team.

According to the 2020 Scrum Guide , the Scrum Values include:

Commitment : Dedicated to the team’s goals and delivering value.

Focus : Concentrating on the Sprint Goal and avoiding distractions.

Openness : Transparent about work and progress.

Respect : Valuing each other's contributions and perspectives.

Courage : Taking risks, speaking up, and tackling challenges.

Why the other options are incorrect:

A. Respect: Respect is about valuing team members' contributions, but asking for help reflects personal courage.

C. Commitment: Commitment relates to dedication to achieving goals, not specifically asking for help.

D. Focus: Focus involves prioritizing and working toward the Sprint Goal, not addressing knowledge gaps or challenges.

The Scrum Master works with the Scrum Team and other involved parties (such as stakeholders) to ensure that artifacts are transparent . Transparency is one of the three pillars of empiricism in Scrum and is critical for effective inspection and adaptation. If artifacts (e.g., Product Backlog, Sprint Backlog, Increment) are not transparent, it can hinder decision-making and progress.

According to the 2020 Scrum Guide , the Scrum Master is responsible for ensuring that everyone involved understands:

The purpose of the artifacts (e.g., Product Backlog, Sprint Backlog, Increment).

The Definition of Done , to ensure shared understanding of what constitutes a completed work item.

Why the other options are incorrect:

A. End users: While feedback from end users is important, they are not directly responsible for ensuring transparency of artifacts.

C. Management team: Management is not directly involved in artifact transparency, as this is primarily a collaboration between the Scrum Team and relevant stakeholders.

D. Project Manager: There is no role of "Project Manager" in Scrum.