A: Opportunities to inspect and adapt the Sprint Backlog are reduced. Re-aligning is bound to become even more difficult. This is a valid concern, as the Daily Scrum is an event where the Developers can inspect the progress toward the Sprint Goal and adapt the Sprint Backlog accordingly. If the Daily Scrum is held less frequently, the Developers may miss some opportunities to adjust their plan and collaborate effectively.

C: Less progress information will be shared, causing the plan for the Sprint to become inaccurate and transparency over progress toward the Sprint Goal is reduced. This is a valid concern, as the Daily Scrum is an event where the Developers can share their work status, challenges, and dependencies with each other. If the Daily Scrum is held less frequently, the Developers may have less visibility and awareness of what is going on in the Sprint, and may face more surprises or risks.

D: Impediments are raised and resolved more slowly which might impact productivity and progress. This is a valid concern, as the Daily Scrum is an event where the Developers can identify and communicate any impediments or issues that hinder their work. If the Daily Scrum is held less frequently, the Developers may have to wait longer to get help or support from their peers or the Scrum Master, and may lose some momentum or efficiency.

References:

Scrum Guide 2020, page 11: “The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.”

Scrum Guide 2020, page 12: “The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work.”

Professional Scrum Master II Course, page 14: “The Daily Scrum is a key opportunity for inspection and adaptation at the team level. It helps the team to synchronize their work, identify impediments, and collaborate on solutions.”