The word “meeting” can bring to mind a room full of people discussing serious issues: some bored and uninterested, some struggling to follow the discussion, and others aggressively trying to prove their point. Deadlines, limited time, competition, and the need to stay ahead call for a more focused way to coordinate work. In Scrum, the Daily Scrum gives Developers that opportunity.
Insights from International Scrum Institute™
10 Tips to get the Best out of Your Daily Scrum Meetings

What are Scrum Meetings?
The Daily Scrum is a short, focused event for the Developers of the Scrum Team. It takes place every working day of the Sprint, at the same time and place, to inspect progress toward the Sprint Goal and adapt the plan for the next day. Some teams hold it in the morning and stand to keep it brief; standing and a morning schedule are optional, not Scrum rules. The following three questions are a familiar way to structure the conversation, but Developers can choose another format that serves the same purpose:
- What was done yesterday?
- What is to be done today?
- Are there any impediments?
These meetings can become too long or unfocused, defeating their purpose. Here are some practical tips for a successful Daily Scrum. Treat the suggested techniques as options for your team, not additional Scrum requirements:
1. Stick to the rule: Time is money…
Start at the agreed time every working day, even if someone is late. Some teams consider incentives for punctuality or penalties for lateness; these are optional team practices, not Scrum rules, and should be discussed openly rather than imposed. Keep the conversation short and to the point. The Daily Scrum has a 15-minute timebox.
2. Predefine the standard of the meeting:
Order and respectful turn-taking help a focused conversation. The Daily Scrum belongs to the Developers, who plan their work together rather than report to a “Scrum leader.” If the Product Owner or Scrum Master is actively working on Sprint Backlog items, they participate as Developers. Let one person speak at a time without interruption.
3. Do not lose focus:
Prepare the topics and priorities that matter to progress toward the Sprint Goal. Work in progress and approaching deadlines can be useful starting points. Keep the conversation relevant to the Developers’ shared plan; save unrelated topics for another discussion.
4. Keep the interest level high by raising the fun quotient:
Because the meeting is short, everyone needs to stay engaged. A joke, motivating quote, comic strip, or interesting image can help your team connect if it does not consume the timebox. A lottery to choose the next speaker can also give everyone a fair chance to contribute. These are optional techniques; use them only when they help your team.
5. No laptops or phones please… This is a tech-free zone…
It is hard to focus when people are checking messages, answering emails, playing games, or browsing code. An agreed tech-free approach can prevent distraction and show respect for teammates. Keep any technology needed for remote participation or accessibility available; the aim is attention, not a blanket ban on useful tools.
6. Consider standing when it works for everyone…
Some teams call the Daily Scrum a stand-up because standing can keep the conversation brief, focused, and energetic. Sitting comfortably can make it easier for a conventional meeting to drift, but standing is not a Scrum requirement. Choose a format that works for everyone, including colleagues who need to sit.
7. Raise the alarm if the meeting loses its purpose…
If the meeting becomes an unproductive status-update routine, take that seriously. Skipping it may make a dramatic statement that your time could be better spent on development, but the Daily Scrum remains a required Scrum event. Raise the problem with your teammates and Scrum Master, then restore a useful conversation about progress toward the Sprint Goal and the next day’s plan.
8. Use a ‘Parking Lot’ for unresolved issues
The Daily Scrum helps Developers inspect progress, coordinate what comes next, and identify impediments. Detailed problem-solving can happen afterward with the people directly involved. Keep a “parking lot” of issues needing a longer discussion, using a notebook or whiteboard if useful. Make it accessible outside the Daily Scrum so teammates can add topics without losing focus during the event. Afterward, arrange the necessary follow-up with the relevant people.
9. Be prepared ahead of time
With limited time, come prepared to discuss progress, the next steps, and difficulties affecting the Sprint Goal. Yesterday’s work, today’s plan, and impediments can help structure that conversation, but they are not a mandatory script. The Developers agree how to keep the event focused; the Scrum Master helps them understand its purpose rather than decide what reports to hear. Redirect off-topic discussion to a suitable follow-up.
10. Use scrum meetings to infuse team spirit
Include remote colleagues, including those working through an outsourcing arrangement. Video or conference calls can help the whole team coordinate. Choose a time that is reasonable for everyone rather than, for example, 1:00 a.m. for remote teammates. Encourage people to communicate with one another instead of directing every comment to the Scrum Master. Where practical, eye contact can help that connection. The goal is effective collaboration and a shared understanding across the team.
The final note!
You may know related coordination practices as daily huddles, morning roll calls, morning meetings, or stand-ups. In Scrum, the Daily Scrum has a specific purpose: inspecting progress toward the Sprint Goal and adapting the Developers’ plan. Discussing yesterday’s accomplishments and today’s intended work can build a clear, coordinated picture of what is done and what remains. It also supports accountability to one another: when someone says, “I will do this task today,” the team can inspect what happened and adapt the next day, rather than turn the event into a report to a manager.
