3 ms·

What information does a standup monologue convey that couldn't be expressed more clearly and with persistent links to context than a comment on a Trello card?

What information does a standup monologue convey that couldn't be expressed more clearly and with persistent links to context than a comment on a Trello card? My team don't do daily standups. They're pointless ceremony. Yesterday I worked on… Yes we know. We can see the Trello card you worked on. Today I am working on… Yes we know. We can see what you've currently assigned yourself on Trello. I am blocked by… Why the hell are you waiting until now to bring this up?!

onion2k 7y ago
I am blocked by… Why the hell are you waiting until now to bring this up?! ...because, as the author of the article notes, developers don't like interruptions. You can't have it both ways - either you can have distraction-free work time so issues like blockers have to wait until the next scheduled communication time or you get distractions when important things happen. You can't reasonably state that people shouldn't interrupt you and they shouldn't wait until the next meeting to tell you stuff. Those things are opposed to each other.
- yakshaving_jgt 7y ago
  > You can't reasonably state that people shouldn't interrupt you and they shouldn't wait until the next meeting to tell you stuff You absolutely can, and we do it all the time. You didn't interrupt me by replying to my comment here. If I was busy working on something, I wouldn't have read/replied to this right now. If I am working on something, it's highly likely that I'll be finished and take a break to check what else is happening in the team well before a morning meeting the following day. If something is truly time-critical and deserving of interruption, then its a moot point.
- erik_seaberg 7y ago
  For me to interrupt you has a lower cost than for me to be stuck all day. But we need to fix something if it happens to me every day, or I can't figure out who to interrupt without affecting every member of the team.

onion2k 7y ago

I am blocked by… Why the hell are you waiting until now to bring this up?! ...because, as the author of the article notes, developers don't like interruptions. You can't have it both ways - either you can have distraction-free work time so issues like blockers have to wait until the next scheduled communication time or you get distractions when important things happen. You can't reasonably state that people shouldn't interrupt you and they shouldn't wait until the next meeting to tell you stuff. Those things are opposed to each other.

yakshaving_jgt 7y ago
> You can't reasonably state that people shouldn't interrupt you and they shouldn't wait until the next meeting to tell you stuff You absolutely can, and we do it all the time. You didn't interrupt me by replying to my comment here. If I was busy working on something, I wouldn't have read/replied to this right now. If I am working on something, it's highly likely that I'll be finished and take a break to check what else is happening in the team well before a morning meeting the following day. If something is truly time-critical and deserving of interruption, then its a moot point.
erik_seaberg 7y ago
For me to interrupt you has a lower cost than for me to be stuck all day. But we need to fix something if it happens to me every day, or I can't figure out who to interrupt without affecting every member of the team.