5 ms·

Except that a stand up doesn’t actually solve the problem you are referring to. People don’t pay much attention to what you’re working on in stand ups since it’

Except that a stand up doesn’t actually solve the problem you are referring to. People don’t pay much attention to what you’re working on in stand ups since it’s most probably not relevant to what they’re working on at the time. It is unreasonable to expect people to have perfect foresight that what you’re working on is going to be relevant to them 2 weeks down the line. There are better ways to solve that problem but stand ups is not one of them.

jVinc 6y ago
> It is unreasonable to expect people to have perfect foresight that what you’re working on is going to be relevant to them 2 weeks down the line. I would understand if you said 2 years or 2 months. But if your road-maps and plans change so rapidly that you can't even assume that features coordinated one day will still be relevant 2 weeks after... then how on earth do you have a functioning team without daily communication? And if you do have daily communication, why not concentrate that to a single max 15 min period to reduce being interrupted in flow?
- machinelearning 6y ago
  The nature of changes is that you cannot predict them in advance. Even if you knew your roadmap for 2 months and were operating perfectly, something unpredictable could happen, as things do. Such things don’t give you any kind of notice before they happen. In such an event, you can’t be expected to remember something someone told you 2 weeks ago in passing anyway. Standups are a short but heavy information dump and are not good at facilitating recall as time goes on. This is true especially if you are operating in a rapidly changing environment such as a startup.
hinkley 6y ago
In another system, like XP, the standup might allow you to absorb a lot more info about your peers. Within the metronome of Scrum, too many people are under time pressure to save face and are likely to say their but and tune half of what everyone else says out entirely.

jVinc 6y ago

> It is unreasonable to expect people to have perfect foresight that what you’re working on is going to be relevant to them 2 weeks down the line. I would understand if you said 2 years or 2 months. But if your road-maps and plans change so rapidly that you can't even assume that features coordinated one day will still be relevant 2 weeks after... then how on earth do you have a functioning team without daily communication? And if you do have daily communication, why not concentrate that to a single max 15 min period to reduce being interrupted in flow?

machinelearning 6y ago
The nature of changes is that you cannot predict them in advance. Even if you knew your roadmap for 2 months and were operating perfectly, something unpredictable could happen, as things do. Such things don’t give you any kind of notice before they happen. In such an event, you can’t be expected to remember something someone told you 2 weeks ago in passing anyway. Standups are a short but heavy information dump and are not good at facilitating recall as time goes on. This is true especially if you are operating in a rapidly changing environment such as a startup.

hinkley 6y ago

In another system, like XP, the standup might allow you to absorb a lot more info about your peers. Within the metronome of Scrum, too many people are under time pressure to save face and are likely to say their but and tune half of what everyone else says out entirely.