Daily stand-ups are very useful and productive to the entire team if done the correct way.
The correct way:
- Everyone gets only one minute to talk.
- They say what they did, what they're going to do, and what help they need.
- While they talk, everyone addresses the rest of the team and not the scrum master.
- No suggestions and solutions seeking.
- The scrum master notes down impediments and follows up offline.
The not so correct way:
- It's a status update, team members address a manager (typically the scrum master).
- People try to tell what they achieved rather than what they did.
- We see a problem and try to solve it right now.
- Discussions tend towards design and/or requirement discussions.
- Your legs start hurting (that's why it's a stand-up: you stand too long and it starts hurting).
If it's extending to an hour, you're surely doing it the incorrect way. Yet, I voted "No" to be truthful to the question that was asked. Stand-ups are not useful to the day-to-day life of the programmer, who typically is impatient, wants to back to his or her terminal and fix that pesky bug or work on that incredible idea.
But they are very useful for the team as a whole, the project and the sprint, and finally the long term success of a programmer (as opposed to day-to-day life).