The ‘Daily Scrum’ definition from the 2013 Scrum Guide in cartoon form.

(from the 2013 Scrum Guide)

Daily Scrum

The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours. This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one. The Daily Scrum is held at the same time and place each day to reduce complexity. During the meeting, the Development Team members explain:

  • What did I do yesterday that helped the Development Team meet the Sprint Goal?
  • What will I do today to help the Development Team meet the Sprint Goal?
  • Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog. The Daily Scrum optimizes the probability that the Development Team will meet the Sprint Goal. Every day, the Development Team should understand how it intends to work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint. The Development Team or team members often meet immediately after the Daily Scrum for detailed discussions, or to adapt, or replan, the rest of the Sprint’s work.
The Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15-minute time-box.
The Scrum Master enforces the rule that only Development Team members participate in the Daily Scrum.
Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Team’s level of knowledge. This is a key inspect and adapt meeting.

Take the Quiz!

[WATUPRO 52]

About the speakers

About the speakers

Related videos

Related videos

Do you explain why you’ve deleted or updated an appointment? | Adam Cogan | SSW Rules

Ever wonder why a meeting was moved or cancelled? Adam Cogan explains the “Secret Ingredient” to professional scheduling: always include a version history and reason for change at the top of your appointments. Improve clarity, keep a record of changes, and hold participants accountable with this simple SSW Rule.

Chat first before changing others’ code | Adam Cogan

Changing someone else’s code? Don’t just dive in! Adam explains why it’s important to check the source history and talk to the original developer before making changes. A quick chat can save headaches and keep everyone on the same page. Perfect advice for devs working in teams!

SSW TimePro – Create a new tenant | Jeoffrey Fischer

Learn how to provision a new tenant in TimePro and sync it with an external Dynamics 365 CRM system.

How to Report Bugs in Seconds | Brady Stroud

Tired of tedious bug reporting? Watch how Brady uses YakShaver.ai to turn a quick screen recording into a professional PBI instantly.

White space – Tips for recording demo | Adam Cogan

Awkward pauses can ruin an otherwise good presentation. In this video, Adam shares a simple tip to handle white space during demos and recordings. By telling your audience what’s about to happen, you avoid silence, cut out useless fillers, and sound more confident. Perfect for product demos, meetings, or presentations on any stage.

Don’t throw things over the fence until you’ve done what you can | Adam Cogan

“Throwing it over the fence” means passing your work or problem to others. This short video delivers one clear message: before you hand something off, do what you can yourself. It’s a simple reminder about responsibility, effort, and ownership in work, teamwork, and daily life.

Why No One Can Agree on the “New” Button? | Adam Cogan

Struggling to juggle a hotfix while mid-feature without losing your flow?

SSW Strasbourg Office in Europe | Walkthrough with Jean

Hear from SSW Senior Software Engineer Jake Bayliss about the importance of providing context, showcasing your work and asking for questions & direction from Product Owners.

Liking Github issues when they are read | Adam Cogan

“Throwing it over the fence” means passing your work or problem to others. This short video delivers one clear message: before you hand something off, do what you can yourself. It’s a simple reminder about responsibility, effort, and ownership in work, teamwork, and daily life.

How to supercharge a company with AI | Ulysses Maclaren

Explore how AI is transforming businesses right now! In this video, Ulysses Maclaren from SSW walks us through the innovative ways AI is being used at Tina CMS. From automating customer interactions to analyzing vast amounts of data and even managing sales leads, AI is revolutionizing workflows