> Teams that work together on the same project should regularly get together in a synchronous conversation. This generalization is clearly not strictly true, b

> Teams that work together on the same project should regularly get together in a synchronous conversation. This generalization is clearly not strictly true, but people stick to it anyway without thinking. Who should get together, exactly? When should they? Why? What is the goal, and are they meeting that goal? Almost every single recurring meeting I've been in has not considered these things seriously. It's just generic people making a generic meeting to talk about generic things to make it feel like work is getting done, when usually, at the end of the meeting, you realize the entire meeting could have been an e-mail. The only useful purpose of a generic, purposeless, recurring intra-team meeting is to reinforce social working relationships. They aren't going to solve a bug or ship a new feature or solve a design decision in one of these meetings. They exist solely to talk about work without doing work, because the interaction between humans smoothes the social dynamics of doing work. But nothing actually gets done.