Typical Borkzilla
Two possible values : short or long.
We're not talking about programming, medium should be possible.
In any case, short at 60 minutes is way too long. Short is 15 minutes, and all of us who have been working this past year know very well that hour-long meetings are 50% repeating what everyone already knows, 30% listening to inane comments, 15% telling someone that his microphone is muted and 5% actual information.
As a manager, if you need to block your team for an entire hour to inform yourself on progress, you're doing it wrong. There's a big chance that Sally doesn't need to know about Jack's problems, and is wasting time listening to them. You're the manager. Do a one-on-one with each member of your team to get updated, then write a summary memo for everyone. The entire team should only be present if you have an important global message to broadcast.
Meetings are generally very much a waste of everyone's time, and nowadays a golden opportunity for the feeble-minded among the higher-ups to make themselves feel important by dragging things along when they could pass the message in a concise manner. I cannot count the amount of time I've wasted in the past twelve months listening to inane babble instead of working, but it is starting to get on my nerves.