As a Scrum Master, how should you handle this situation?

A Scrum Team has remote team members, after the 15 minute daily Scrum, Developers spend an additional 15-30 minutes every day discussing architectural designs, code designs, code reviews, high priorities bugs, and concerns.

As a Scrum Master, how should you handle this situation?
A . Tell the Developers that they cannot add events or meetings that are not part of the Scrum Framework.
B. Ask the Scrum Team to discuss everything needed in the Daily meetings within 15 minutes. Meetings outside the Scrum Events are not allowed. They are a waste of time.
C. Facilitate such meetings so Developers only spend 15 minutes on the Daily Scrum.
D. Allow the Scrum Team to self-manage and decide for themselves.
E. If needed, inform the Management about such meetings. Try to reduce such meetings as much as
possible so the Developers can get more time to develop.

View Answer

Answer: D

Explanation:

The Scrum Master will only act if requested or if they observe that there is a potential problem. Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are also self-managing, meaning they internally decide who does what, when, and how. The Daily Scrum is not the only time Developers are allowed to adjust their plan. They often meet throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint’s work. The Developers are solving complex problems, it is natural that they need to collaborate and make some decisions together. In the initial phases of the Product or new goals, they might need to align a lot on the architecture and designs. If the Developers find benefit in discussing these problems together every day for 30 minutes, that is part of their decision on how to build the Product. If the Scrum Master observes that this may not be a good use of the time or not the right way to address the problems, they can make powerful questions to challenge the reasons for these meetings and think of other alternatives. The Scrum framework, as outlined herein, is immutable. While implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices. On the other side, Scrum can be extended and enhanced as long as the improvements do not break the rules of the Scrum Framework.