I set the policy early on in my company (we follow very complete Agile and XP) for all engineering related meetings: immediately after lunch or not at all. Stan

I set the policy early on in my company (we follow very complete Agile and XP) for all engineering related meetings: immediately after lunch or not at all. Standups, Iteration planning and review, Manager 1-on-1s, you name it. Lunch interrupts everyone and people are rarely doing their most incisive thinking while food digests...if we're going to be unproductive anyway, might as well have a meeting. I put in this policy for the same reasons PG talks about, and feel like it pretty completely handles the problem. Do people agree or disagree? Is there any reason I shouldn't be treating 1-2:30 as talking time, and the rest as coding time?