11–20 of 125 posts
"Remember, they are not status meetings." Additionally, I think it is important to remember that standup is not a "justify my existence on the team" meeting. Having nothing to report is fine.
Conversely, this particular dysfunction of standups is a useful index of how much the corporate culture leads people to feel like they must justify their existence.
From the article:
- Make sure everyone is working on the right thing
- Help out other team members by taking work off their plate or helping them by sharing domain-specific knowledge
- Keeping everyone informed
How is that different from a status meeting? I've heard "standups are not status meetings" over and over from the agile community, but I don't get it. They sure seem to be quick status meetings that allow everyone to get a handle on the current status of the iteration?
What's a standup? I didn't see it defined in either post.
Some places don't manage standups well at all, and that is one of the big problems with standups in general - they become status meetings and take too long. When done right, they are very useful as you quickly know what everyone is working on and if someone might need your insights on something (which should then be a separate meeting and not covered in the standup).
Holy crap, he has 3 hours standups? They're called "STAND UPS" because you stand while giving them so that you're motivated to be quick! I actually try and follow the one-breath rule for what have I done, what am I doing, what are my blockers.
Standups would make more sense if the team did not communicate during the day. The reason I think they are pointless is that when a blocking issue arises, you drop what you're doing and walk straight over to the person who can help you. I've never seen or heard of someone waiting until the following day's standup to bring up the issue (which is supposedly what the standup is for, right?).
If you're doing Scrum, the only issues you should really be bringing to standups are those you can't solve within the team that you need the Scrum Master to sort out. Anything the team can fix for itself isn't blocking, it's business as usual.
"Remember, they are not status meetings." Additionally, I think it is important to remember that standup is not a "justify my existence on the team" meeting. Having nothing to report is fine.
Holy crap, he has 3 hours standups? They're called "STAND UPS" because you stand while giving them so that you're motivated to be quick! I actually try and follow the one-breath rule for what have I done, what am I doing, what are my blockers.
No, he is saying that a 6 person, 30 minute stand up takes 3 hours.