5 ms·
Standups can however very easily become very uncomfortable in a dysfunctional environment. (As the original article unwittingly demonstrated.) Consider the sta
by onemorepassword 14y ago
Standups can however very easily become very uncomfortable in a dysfunctional environment. (As the original article unwittingly demonstrated.)
Consider the standup to be the canary in the coalmine. Most of the time people can ignore the dysfunction, work around it and pretend it isn't happening by just getting on with the job as much as possible.
But the standup will then become increasingly uncomfortable. Every single day.
In a healthy organisation, you can have perfectly pleasant standups, even without Scrum or Agile. I mean, what does a healthy team have to fear from standing around for a few minutes bringing each other up to speed?
It's a process that is very close to what often happens quite naturally around the time everyone on the team has arrived at the office (or online).
A standup can only become poisonous if the poison is injected from elsewhere. In Gareth's case abusing it for management status reports. In other cases it might be tension between team members, not having a clear goal, whatever.
The point is, you cannot have pleasant standup if there is that kind of stuff going on. Which is all the more reason to have a standup, unless it's your policy to ignore problems rather than dealing with them.
Standups aren't just not poisonous either: they are a very good poison detector.
- hobs 14y agoIt's a process that is very close to what often happens quite naturally around the time everyone on the team has arrived at the office (or online). This is exactly the behavior I have seen of well functioning teams. Usually there is a period when the person comes in, maybe after coming up to speed on their email where they get informed and up to speed on what is happening with everyone, if anyone needs anything, what people are working on, and then get to work! Standups are just a formalized approach to what can be a drawn out process for an individual, and in some cases may not be "normal" for your standard introvert dev types who sit at a computer all day and perceive meetings as multi-hour long chores that are inflicted on their participants instead of quick high quality bursts of information distributed in an efficient fashion (face to face).
- Evbn 14y agoThank you. Most of "agile" "process" serves one purpose: to shine light on every aspect of your team's functioning. What you do with what you see is up to you.