Daily for Dev Teams: What Wastes Everyone’s Time

Every workday, thousands of dev teams gather for a quick meeting to sync up. Yet many walk away wondering if the 15 minutes were worth it. Standups are arguably the most adopted Scrum event: 87% of Scrum teams hold daily standups, according to the Scrum Alliance’s State of Scrum survey. Popularity, though, does not equal effectiveness. In practice, some standups energize the team, while others feel like recycled status reports.

In this article, we explore what makes standup meetings genuinely useful for a dev team. We’ll also cover common pitfalls to avoid, along with hands-on tips for engineering managers and team leads running these meetings. Additionally, you will find here guidance for remote teams and an honest look at whether daily standups are needed at all.

What Is a Daily Standup Meeting for a Scrum Team?

You probably already know the answer – but, still, it’s useful to start with the definition to make sure we are on the same page.

A daily standup is a short, time-boxed meeting held every workday. In the Scrum framework, it is also called a daily scrum. Its purpose is to align the development team on the sprint goal, share plans for the day, and flag any blockers.

Most teams allocate about 10-15 minutes for scrum meetings. Many run them at the start of the day, when everyone is fresh and focused. The scrum master often facilitates, but the meeting belongs to the team. In mature agile teams, the daily scrum often runs without a dedicated facilitator.

Common Standup Meeting Formats

Different agile teams run their daily scrum in different ways. Here is how the most common approaches work in practice:

The best format depends on team size, seniority, and how much of the work is already visible in Jira. You can also combine different approaches – for example, round robin or asynchronous standups can follow the traditional three-question format.

As you can see from the table, each approach has its strengths, as well as weaknesses to watch out for. In the next section, we’ll explore other common issues you should know about.

6 Signs Your Daily Standup Meetings Might Need a Reset

To add more color, here’s a real-life example: I once attended a standup meeting that lasted over 2,5 hours… Well, actually, more than once. In one of my former teams, the manager was eager to resolve each blocker on the spot. This was well-meaning, but the meeting quickly turned into an extended peer review session, with discussing each task in depth, brainstorming ideas and directions, and even trying them out immediately. 

Although these collaboration sessions were meaningful, it’s rather hard to start every day with such a prolonged meeting when you already have your own to-do list to work on.

Hopefully, such extreme examples are rare for most agile teams. However, this is a vivid illustration of how standup meetings can easily become a burden for everyone when done wrong.

Here are the most common signs to watch for. You know your standup meetings need a reset when:

1. The meeting regularly runs past 15 minutes. Occasional overruns can happen, but a steady pattern points to a deeper issue. Usually, it means the standup is being used for problem-solving or discussions that belong in a separate call.
   
2. People multitask during the call. If engineers keep their laptops open or drift into Slack during the standup, the meeting is not landing for them. That is a clear sign that the content is either too generic or aimed at the wrong audience.
   
3. Blockers repeat for days without resolution. When the same blocker shows up morning after morning, the standup has become a reporting ritual. The point of naming a blocker is to trigger help, not to log it repeatedly.
   
4. The same person dominates the conversation. When one voice takes over the standup, the meeting is out of balance. Other engineers might hold back their updates, and useful information can remain unspoken.
   
5. People ask if they can skip the standup meeting. When team members start looking for excuses to opt out, the format has stopped serving them. That is usually a signal to reset the meeting, not to enforce attendance.
   
6. Debugging happens in the meeting. When two engineers dive into a technical problem while everyone else waits, the standup turns into an ad hoc working session. That conversation belongs in a follow-up call with only the relevant people.

Running standup meetings effectively is important – not because it simply must be done by the textbook, but because the cost of doing it wrong is tangible and rather high.

What is the Cost of a Bad Daily Standup?

A poorly run standup is more expensive than it looks. The time on the calendar is only the visible cost, while the real damage adds up across the whole development team in ways that are harder to spot on any single day:

• Loss of prime focus windows for developers. According to Microsoft’s 2025 Work Trend Index, half of all meetings land in the 9-11 am and 1-3 pm windows, exactly when focus is at its peak for most people. A tight, well-run standup fits neatly into that morning/afternoon slot, while a long and messy one bleeds into the deep work hours that follow.
• Blockers that surface too late. When the meeting loses focus, real blockers get buried under general status updates. By the time an impediment gets proper attention, the sprint may already be halfway lost.
• The sprint goal loses its shape. If the standup turns into a series of individual reports, the shared goal fades into the background. The team stops connecting daily work to the outcome they committed to at sprint planning.
• Erosion of trust between the team and management. When the standup becomes a manager-facing report, engineers feel monitored rather than supported. Over time, that shifts the meeting from a coordination tool into a compliance ritual, and trust suffers on both sides.
• Meeting fatigue and lower morale. Long, unfocused meetings drain energy before the workday even starts, which negatively affects performance and productivity.

Here’s how Rebecca Hinds, who founded The Work Innovation Lab at Asana, describes this problem, based on their State of Work Innovation report:

All these effects compound over time. The wasted meeting minutes are the obvious part. You can price them easily against your team’s blended engineering rate. Harder to estimate is the impact on team efficiency and overall productivity. Those losses rarely show up on a P&L, yet they quietly shape how a team delivers over time.

In the next section, we’ll talk about how to turn these meetings into a source of benefits rather than drawbacks.

How to Run Efficient Standup Meetings Everyone Loves

Good standup meetings are short, focused, and predictable. The team shows up, quickly aligns on the sprint goal, flags impediments, and gets back to work. The rest is a matter of format and discipline. Here are the practical rules that make the difference.

What You Should (and Should Not) Do in a Standup

Standup meetings work best when engineering managers and team leads take a step back. The team is the audience, not you. Your role is to observe patterns, remove obstacles, and give people room to coordinate with each other.

Do:

• Let people talk to each other, not to you. Sit slightly outside the circle if that helps
• Listen for repeated blockers – they can be a signal of systemic issues
• Watch for people who never speak up or who always dominate the conversation, taking up too much time
• Pay attention to patterns that emerge across sprints rather than just focus on individual updates. The value of attending as a manager comes from seeing how the team moves over time, not from noting who did what yesterday
• Ask for feedback on standup effectiveness during retrospectives. The team knows better than anyone whether the format is working. Retrospectives are the right place to adjust the rhythm, format, or attendee list

Don’t:

• Do not answer questions that team members can answer for themselves. Jumping in with answers trains engineers to defer to you. Give them the space to sort it out on their own.
• Do not turn the standup into a performance review. Judging updates in real time kills the psychological safety that the meeting depends on. Feedback belongs in one-on-ones, not in front of the team.
• Do not interrupt engineers mid-update with follow-up questions. Save them for after the standup so the meeting keeps its rhythm.

For more tips, please see the article How to Run Effective Daily Stand-Up Meetings.

How to Conduct Standup Meetings for a Distributed Dev Team

Remote teams face different challenges than colocated ones. Time zones, screen fatigue, and thinner informal communication all change the shape of a good daily scrum.

The trend is clear: 30% of meetings now span multiple time zones, up 8 percentage points since a few years ago, according to Microsoft’s 2025 Work Trend Index Annual Report. More distributed teams are trying to find a shared meeting hour that respects everyone’s working day.

Here are a few hands-on tips for effective standup meetings in a remote team:

• Rotate the standup time every quarter if your team is spread across different regions. That way, no single time zone always takes the inconvenient slot
• Turn on video by default. Faces build trust in a distributed team
• Keep an async fallback. For example, anyone who cannot attend live can post a written update on Slack
• Post a summary in the team channel immediately after each meeting, so that teammates who weren’t able to join can catch up at a glance
• Ask each engineer to post a one-line update before the call. That alone cuts standup time in half

Here’s one more practical tip from Oleksandra Sokol, Product Lead at TitanApps by Railsware:

It’s also worth mentioning that building an effective distributed dev team is a challenge in itself, but it can be mitigated by working with an experienced partner. Lemon.io helps startups and scaleups hire pre-vetted senior developers who are ready for remote-first work. Their vetting process focuses on both technical skill and remote work experience, so new hires can plug into your standups and sprint rituals without a long ramp-up.

For more on this topic, please see the article How to Manage Remote Developers in 2026.

How to Support Standup Meetings Inside Jira

Jira board is an important part of your standup meetings, so you need to make sure it’s configured well:

• Map columns cleanly to your Jira workflow. The board should reflect the actual stages your work moves through – this makes it easier to assess progress at a glance.
• Use swimlanes to group by assignee, epic, or feature. Grouping by theme helps your team discuss tasks by feature rather than by person, which shifts the conversation from status to progress.
• Add board filters for “at risk” or “blocked.” This will allow you to easily filter out problematic work items and focus on them during the meeting. 
• Keep the sprint board tidy and up to date. Stale work items slow the meeting down and blur the picture of what is really in flight.
• Use checklists to make progress on tasks visible. Complex or high-stakes tasks often hide their real state behind a single Jira status. It can stay “In Progress” for a long time, but how much progress has actually been made is unclear. Adding a checklist inside the work item breaks it down into concrete steps, so the team can see exactly how far the work has progressed and what remains. You can easily do this with Smart Checklist for Jira.

In this example, the Release Readiness Checklist is used to coordinate the dev and QA teams. It increases transparency and reduces the need for detailed explanations during the standup meetings. 

Smart Checklist for Jira allows you to add feature-rich checklists inside any work item. Each step on the list can have its own progress status, due date, assignee, priority, and an expandable field with details. The solution also enables you to save checklist templates for recurring tasks and add them to work items automatically based on custom conditions. Additionally, you can configure your Jira board to display checklist progress on work item cards.

Checklist templates are useful not only for multi-step tasks but also for enforcing quality standards. Some common use cases include the Definition of Done Checklist Template and the Code Review Checklist. They help you ensure that everyone goes through the same steps every time. This promotes consistency and helps your team maintain high-quality standards, which is especially important for distributed development teams.

In addition to its native automation features, Smart Checklist can also be used together with Automation for Jira.

To add such checklist templates to your Jira work items, install Smart Checklist from the Atlassian Marketplace.

Does Your Team Actually Need Daily Standup Meetings?

Not every team benefits from a daily standup. There are different perspectives worth weighing. Some voices in the industry argue that daily standups and agile meetings in general are overrated. In her interview on Lenny’s Podcast, Melissa Perri, founder and CEO of Product Institute and author of Escaping the Build Trap, put it bluntly:

The data backs up part of her point. Atlassian’s survey of 5,000 knowledge workers found that 78% feel expected to attend so many meetings that it hurts their real work.

Companies solve this in different ways. For example, Atlassian allows teams to pick their own rhythm. When describing standup meetings at Atlassian, they noted that some teams meet daily, while others meet three times a week. Some other companies handle standups fully asynchronously or use weekly meetings instead of daily syncs.

So, are daily standup meetings essential? The answer depends on your team size, your work style, and your context. Small, senior teams with strong async habits can often skip them, as well as small teams working in the same room, where it’s easy enough to stay synced during the day. At the same time, new teams, teams tackling complex user stories, or teams onboarding a new employee usually benefit from a daily rhythm. The best move is to evaluate your team’s real needs and adjust flexibly, rather than following the Scrum playbook to the letter.

Frequently Asked Questions About Standup Meetings for Dev Teams