Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Agree with the notion that turning standup into a static status meeting is a poor use of time. If you're blocked you should speak up. If the team wants to know the state of your work, they should defer to project management tool. That said, "standup" is less to do with what you did or immediate blockers. It's about planning for the day. "Here's what's going to get done today, and here's the relevant information for my team." It's a tool for synchronizing, getting on the same page, setting you and your team up for success on a daily basis.

If you don't feel like that's the case, you're probably right in that going async would be a better use of your time. I suspect this is a process dysfunction that has less to do with standup and more to do with a misunderstanding of the value proposition associated with a properly executed standup.

Edit: not everything is an immediate "oh sh*t" type of blocker. If you're working in a collaborative organization, you most like have "low tier" blockers or knowledge that can and should be shared with the team. Face to face makes this easy.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: