If you want to understand what a standup is and how to do a good one you need to read the original paper that documented the daily standup Borland Software Craf

If you want to understand what a standup is and how to do a good one you need to read the original paper that documented the daily standup Borland Software Craftsmanship: A New Look at Process, Quality and Productivity (https://1pn8a8ult4o2bls5f2jxuel1-wpengine.netdna-ssl.com/wp-content/uploads/2013/07/borland-process.pdf https://1pn8a8ult4o2bls5f2jxuel1-wpengine.netdna-ssl.com/wp-...). The standup is a planning meeting, not a status meeting. If you feel your standup meeting is a status meeting, you are doing it wrong. The reason the standup became popular was because the Borland Quatro Pro team was EXTREMELY productive and it seemed standup helped the team be productive. Here is the relavant quote. The core architecture team met daily to hammer out C++ class interfaces, to discuss overall algorithms and approaches, and to develop the basic underlying mechanisms on which the system would be built. These daily meetings were several hours in duration; from what I heard,the project was made more of meetings than anything else. That's right, they had a 'standup' that could last hours. Yet they were extremely productive. I hope this sheds some light on what the daily standup should really be. Maybe people should sit down.