3 ms·
In the one job where standups went well, our limit was 15 minutes, for about 7 developers. > Standups are initially scheduled for the start of the development
by BeetleB 6y ago
In the one job where standups went well, our limit was 15 minutes, for about 7 developers.
> Standups are initially scheduled for the start of the development day.
There's no reason it should. We did not have it at that time.
If it's at a reasonable time (e.g. after all people have normally begun work), then have a low tolerance policy for those who come late. Sometimes our standups were about 5 minutes, because some people were on vacation and some were late. When the late people showed up, it would be to an empty room. We didn't wait for them beyond 1 minute.
There's no way we would tolerate 30 minutes, let alone an hour. If it was going beyond 15 minutes, many/most of the developers would abruptly leave. You have to have an idea what you're going to say before you enter the room, and not go into technical details - the standup is not a problem solving session. People who randomly droned in giving their update would be "coached".
For a while we had the manager in the room. Then we booted him out - he was no longer welcome (it was an amicable parting :-) ).
> but what I just described is the standup reality virtually everywhere.
I can believe your experience is more common than mine, but I can also say I wouldn't work with such sloppiness in the team. In our case, our team wasn't the standout. This discipline was drilled in at the organizational level and had support from the leaders.
It may sound bad the way I write it, but it was actually very easy to cultivate this culture, and everyone liked it. This was literally the easiest and simplest part of the work day.
Edit: Lest this come off as a pro-scrum comment, I assure you it's not. There are things I don't like about Scrum, and am not sure I'd like to go back to working scrum-style. However, the complaints in the parent post are not problems with scrum, but cultural problems. As one of the pro-scrum people in my company put it: "I'm not really sure Scrum does a great job in improving productivity. But it's excellent at exposing existing problems in teams."
- joseph_grobbles 6y agoIf you don't have it at the beginning of the day, then you're putting a hard gate on flow. This phenomena is well known, and the disruption of having a scheduled event mid-workday is significantly larger than the time of the disruption. Everyone is going to fade out of their work long before and won't re-engage for sometimes after. As to scrum exposing cultural problems, maybe that's true, but in some cases scrums are a clumsy attempt to solve cultural problems (as I said in another comment, agile was the failure mode for orgs stumbling with "waterfall"). Terrible progress visibility? Let's have a scrum! No team member communications? Scrum will fix it! People sandbagging or not doing their work? Don't worry, Scrum will save the day! On good teams we all know what each other is working on. We're all aware of the codebase. We see the commits. We are available when someone has a problem (and people know who is a good person to asynchronously ping when they have a problem in specific domains), and are open to the reality that everyone is imperfect and doesn't know everything. On good teams scrums serve absolutely no value, and are a redundant waste of time. On bad teams they are an attempt to bandage over all of the lack of those factors.
- pseudalopex 6y agoTalking about the beginning of the day assumes everyone starts at the same time. Having it just before most people go to lunch can be less disruptive. I agree scrum isn't helpful usually though.
- ianpurton 6y agoThis is exactly my experience with scrum too.
- tonfreed 6y agoWe had a client doing an "agile transformation" corporate style, ie they pulled the entire floor in to talk about everything for an hour every morning. Imagine 30-40 people, all from different teams, all huddled around a whiteboard talking about their work. It was a shitshow. I think we need to just kick all the suits out of the engineering process, because they insist on stupid shit like that and never address the core issues.