Correct Answer:

From a Scrum Master's perspective, replacing the Daily Scrum with a weekly update meeting isnot consistent with Scrumand would significantly weaken the team's ability to inspect and adapt effectively, regardless of the Sprint length.
First, Scrum explicitly defines theDaily Scrum as a required event. The Scrum Guide states that the Daily Scrum is a 15-minute event held every working day of the Sprint for the Developers. The length of the Sprint-whether one week or one month-does not change the purpose or necessity of this event. Therefore, by choosing not to have a Daily Scrum, the team wouldno longer be practicing Scrum, but rather a Scrum- like process.
Second, the Daily Scrum isnot a status meeting. Its primary purpose is to allow the Developers toinspect progress toward the Sprint Goal, synchronize their work, andadapt the Sprint Backlogas needed. A weekly meeting dramatically reduces the frequency of inspection and adaptation, delaying the discovery of issues such as integration problems, misalignment, or risks to the Sprint Goal.
Third, removing the Daily Scrum negatively impactstransparency, one of Scrum's three pillars of empiricism. Without daily synchronization, important information about progress, impediments, and discoveries becomes stale or hidden. This reduced transparency increases the likelihood that work will drift away from agreed standards, fail to integrate properly, or no longer support the Sprint Goal by the end of the Sprint.
Fourth, the argument that a one-month Sprint justifies less frequent inspection reflects a misunderstanding of empiricism. Longer Sprintsincrease risk, which makes frequent inspection and adaptation more important, not less. The Daily Scrum provides a regular opportunity to realign the team and respond early to emerging problems, thereby reducing waste and rework.
Finally, as a Scrum Master, my role is toteach and coachthe Scrum Team on the purpose and value of Scrum events. Rather than removing the Daily Scrum, I would help the Developers improve how they use it-for example, ensuring it focuses on progress toward the Sprint Goal and actionable planning for the next 24 hours, instead of turning into a reporting session.

Correct Answer:

A Development Team claiming self-organization as a reason to stop theDaily Scrumreflects a misunderstanding of bothself-managementand the purpose of Scrum events. As a Scrum Master, I would address this through teaching, coaching, and empiricism rather than enforcement.
Daily Scrum Is Mandatory in Scrum
First, it must be made clear that theDaily Scrum is a required Scrum event. The Scrum Guide defines it as a
15-minute event held every working day of the Sprint for the Developers. Choosing to eliminate it means the team isno longer practicing Scrum, regardless of how well they collaborate informally.
Self-Organization Does Not Mean Skipping Empiricism
Self-organizing (self-managing) teams decidehowto do the work, notwhetherto inspect and adapt. Scrum events exist to upholdempirical process control. The Daily Scrum specifically enables:
* Transparencyabout progress toward the Sprint Goal,
* Inspectionof the Sprint Backlog and current plan,
* Adaptationof work for the next 24 hours.
Informal collaboration throughout the day does not replace theshared, intentional inspection momentthat the Daily Scrum provides.
The Daily Scrum Is Not a Ritual or Status Meeting
If the Daily Scrum feels like a needless ritual, this is asignal that it is not being used correctly. It should not be a status report or a meeting for the Scrum Master or Product Owner. Instead, it is aplanning event for the Developers, focused on how to best achieve the Sprint Goal.
As a Scrum Master, I would coach the team toimprove the Daily Scrum, for example by:
* Centering the discussion on progress toward the Sprint Goal,
* Making impediments and risks explicit,
* Using different formats that suit the team's context.
Risks of Removing the Daily Scrum
Removing the Daily Scrum reducestransparencyand delays inspection and adaptation. Problems such as integration issues, misalignment, or threats to the Sprint Goal may surface too late, increasing risk and waste.
Over time, this undermines predictability and value delivery.

Correct Answer:

In Scrum, decisions to optimize value and control risk depend on theperceived state of the artifacts. If artifacts are not transparent, inspection and adaptation become ineffective, leading to poor decisions. Scrum therefore defines specificevents and practicesto improve transparency and support empirical decision- making.
Scrum Events That Improve Artifact Transparency
Sprint Planningimproves transparency by aligning the Scrum Team on the current state of theProduct Backlogand theProduct Increment. The Product Owner explains backlog ordering and objectives, while Developers assess what is feasible based on the current Increment and Definition of Done. This shared understanding reduces risk by creating a realistic Sprint Goal.
Daily Scrumimproves transparency of theSprint Backlog. Developers inspect progress toward the Sprint Goal and make visible emerging risks, dependencies, and impediments. Daily inspection ensures that deviations are discovered early, enabling fast adaptation and reducing delivery risk.
Sprint Reviewimproves transparency of theProduct IncrementandProduct Backlog. Stakeholders directly inspect the Increment and provide feedback. This exposes assumptions, validates value, and informs Product Backlog adaptation, helping optimize future value and reduce market risk.
Sprint Retrospectiveimproves transparency ofprocess-related aspectsthat influence the artifacts. By inspecting ways of working, tools, skills, and the Definition of Done, the team identifies improvements that increase artifact quality and reliability over time.
Practices That Improve Transparency
Aclear and shared Definition of Doneensures transparency of the Product Increment. It creates a common understanding of what "complete" means and prevents hidden work or misleading progress.
Product Backlog refinementimproves transparency by clarifying Product Backlog Items, making assumptions explicit, and reducing uncertainty. Although not a formal Scrum event, refinement supports better inspection and forecasting.
Frequent integration and testingimprove transparency by making the real state of the Increment visible early and often. This reduces the risk of late surprises and unintegrated work.
Visible metrics and information radiators(such as Sprint Goals, Sprint Backlogs, and progress toward objectives) help stakeholders and teams understand the state of work without relying on reports or interpretations.