Good article with great points. However...
"For C#, on the other hand, it has worked really well to formalize: every Monday, Wednesday, and Friday from 1:00 to 3:00, we have a regularly scheduled meeting. We have a living agenda. Issues bubble to the top, and we knock them off. We have a wiki now on the internal web with the issues list, resolutions for them, and so on." - Anders Hejlsberg - http://www.artima.com/intv/csdes.html
Have a clear purpose, come prepared, and end the meeting as soon as possible by summarizing action items, but don't force a productive meeting to stop just because 60 minutes have past.

How many meetings did you have today? This week? This month? Now ask yourself how many of those meetings were worthwhile, versus the work that you could have accomplished in that same time. This might lead one to wonder why we even have meetings at all. At GitHub we don't have meetings...