3 ms·

Not the above poster, but I also do and like the yesterday/today slack standups (with a proper zoom meeting once every two weeks to review/strategize/etc). Usu

Not the above poster, but I also do and like the yesterday/today slack standups (with a proper zoom meeting once every two weeks to review/strategize/etc). Usually the "yesterday I worked on X, today I will also work on X" for me are a sign that I need to grab a second team member to get a second set of eyes on something. That is if X is specific enough, of course - but if working on something larger, I think it should always be if the standup message is to have any usefulness at all. So I'll try to always write something more in way of "Yesterday I was working on X, so I made X_1 and started on X_2, but had problems so I've skipped over to X_3. Today I'll be continuing working on X_2", with the numbered ones being subtasks or subsets of X. I'd probably do the same on actual spoken standups, but this is a kind of a meeting that could easily be a slack message, so I prefer slack :)

randomdata 5y ago
> Usually the "yesterday I worked on X, today I will also work on X" for me are a sign that I need to grab a second team member to get a second set of eyes on something. While I admittedly do not entirely understand why it requires writing that down to come to the realization that you need help, if that is what works for you, more power to you. But is external communication necessary? Writing that down in notepad.exe seems like it would trigger the same in you? Why bother your team with noise? Once you have realized, letting the problem be known to your team makes sense, sure, but that does not seem like something that happens on any kind of regular schedule. Pre-scheduling your chance to let your team know that you have a problem seems unnecessary at best. I've certainly never met a teammate who is unwilling to help with a problem without being given advanced scheduled notice, and I'm not sure a person with that kind of attitude should be on the team in the first place.
- saithir 5y ago
  It's only noise when all everyone ever writes in them is noise. In that case, yes, I fully agree - it'd be a pointless waste of time and you should stop. I do like knowing what others work on, as we're all remote. Our project owner likes knowing what we're working on as well. If it was a daily zoom meeting I'd probably be against it every single day. As a slack message in a separate channel it's not really a bother. > why it requires writing that down to come to the realization that you need help It helps avoid tunnel visioning on the problem too much, I guess. The standup provides a chance to do so every morning, why not use it? It's not like it's the only way of me communicating with the rest of the team and asking for help, not sure what ever gave you that idea...
  - randomdata 5y ago
    If it is reserved for when you have something interesting to tell, I can see the benefit. An expectation of fixed interval contribution is excessive. Then you just get the ridiculous "I worked on X yesterday. I will work on X today." out of lack of anything else to say.

randomdata 5y ago

> Usually the "yesterday I worked on X, today I will also work on X" for me are a sign that I need to grab a second team member to get a second set of eyes on something. While I admittedly do not entirely understand why it requires writing that down to come to the realization that you need help, if that is what works for you, more power to you. But is external communication necessary? Writing that down in notepad.exe seems like it would trigger the same in you? Why bother your team with noise? Once you have realized, letting the problem be known to your team makes sense, sure, but that does not seem like something that happens on any kind of regular schedule. Pre-scheduling your chance to let your team know that you have a problem seems unnecessary at best. I've certainly never met a teammate who is unwilling to help with a problem without being given advanced scheduled notice, and I'm not sure a person with that kind of attitude should be on the team in the first place.

saithir 5y ago
It's only noise when all everyone ever writes in them is noise. In that case, yes, I fully agree - it'd be a pointless waste of time and you should stop. I do like knowing what others work on, as we're all remote. Our project owner likes knowing what we're working on as well. If it was a daily zoom meeting I'd probably be against it every single day. As a slack message in a separate channel it's not really a bother. > why it requires writing that down to come to the realization that you need help It helps avoid tunnel visioning on the problem too much, I guess. The standup provides a chance to do so every morning, why not use it? It's not like it's the only way of me communicating with the rest of the team and asking for help, not sure what ever gave you that idea...
- randomdata 5y ago
  If it is reserved for when you have something interesting to tell, I can see the benefit. An expectation of fixed interval contribution is excessive. Then you just get the ridiculous "I worked on X yesterday. I will work on X today." out of lack of anything else to say.