Generally people are incapable of communicating efficiently.
A standup should cover:
1) what did you do yesterday
2) what are you doing today
3) do you have an issues?
This should take less than one minute per person. "Issues" should be resolved offline.
I once worked on a team where the "scrum master" would update Jira for each person's status. This resulted in a 30 second update turning into 2 or 3 minutes of detailed status.
I also worked on a 15 person team that had a giant stand up for the entire team. The resulted in a 30 to 45 minute stand up.
Sure, those are bad. That doesn't mean standups are bad though. One thing I found successful was to push for the standup to start 15 minutes before lunch. That gives ample time for the standup (2-3 minutes per person is longer than one should need, but my team likes to take notes during the standup, which while lightweight does delay things a bit) and a bit of followup, and deciding where to eat.
Also doing it just before lunch means everyone is in the office, you aren't breaking anyone out of flow unnecessarily, and everyone has a decent idea of what they will actually be working on today (since they are already in the context), so you don't have the issue of "hmm I don't remember what I was doing" or "uhhhh....oh right I'm planning to work on X" delaying things.
This should take less than one minute per person. "Issues" should be resolved offline.
I once worked on a team where the "scrum master" would update Jira for each person's status. This resulted in a 30 second update turning into 2 or 3 minutes of detailed status.
I also worked on a 15 person team that had a giant stand up for the entire team. The resulted in a 30 to 45 minute stand up.