News for hackers. Stuff that matters.
Re:Ask HN: How to manage developers who aren't very good? by dragonwriter on Friday February 06, 2015 @06:09PM (#9012199)
Its essential to regularly update what tasks are done and what tasks are being worked on by whom, but if you use some other system to handle those updates and keep people aware of the updates (e.g., visual artifacts updated as items are completed and pulled for work, as in kanban), then you don't need to do that in the standup meeting.

Identifying issues encountered (both to share knowledge of how issues were resolved and to gather information on addressing barriers that haven't been resolved) is a pretty standard element of standup meetings even when they include progress updates, and certainly a good thing to keep them for if you've moved the status updates to another channel.

There are no comments on this comment yet.