The daily status update has different role for different people (devs, scrum master, tech lead). It might be useless for devs but valuable for scrum master, for

The daily status update has different role for different people (devs, scrum master, tech lead). It might be useless for devs but valuable for scrum master, for example. The dynamics also depend on # of people involved - the fewer, the more effective. What we did in my last 2 teams to make standups better: Team 1: move it from 10 AM to 11h45 (just before the lunch). Advantages: 1) Not stressing out people who are late; 2) Not breaking the work of people who arrive early; 3) Keeping it short - since it's before lunch, it can't last forever because people want to eat. Team 2: move to slack e-standup. Advantages: 1) and 2) above; 3) Async, so you can do it early, late, or even the evening before; 4) It takes 2 min for each person, not 20 min and you don't have to stare in the floor while your mind is somewhere else; 5) Avoiding "ummmmm whaaat did I do yesterday ummmm let me think" x 10.