Dear Bob ... I think I'm at a good point in my project to have daily standup meetings (start of integration testing). What drives the topics at these: bug lists? Critical setup issues? Everything that "should happen today"? - Standing, but quietly Dear Standing ... My first reaction is that you're asking the question backward. Ask yourself what project communication is best handled through this format rath Dear Bob …I think I’m at a good point in my project to have daily standup meetings (start of integration testing). What drives the topics at these: bug lists? Critical setup issues? Everything that “should happen today”?– Standing, but quietly Dear Standing …My first reaction is that you’re asking the question backward. Ask yourself what project communication is best handled through this format rather than starting with the format.In general, I prefer weekly status meetings for projects as they let the daily ebb and flow of work average out without letting issues age too long. I think of daily standups more for operations, where it makes sense to review how the previous day’s production went so any problems can be wrapped into the schedule. It also occurs to me that when a project transitions from development to test, and then implementation, it probably does make sense to dispense with weekly status meetings and replace them with daily standups. This lets you create a “punch list” of open items necessary to wrap the project which can be reviewed and refreshed daily. I’d think it would be a very good idea – it keeps everyone current and maintains both a sense of urgency, and a sense that the finish line is approaching.– Bob ——– Technology Industry