News for hackers. Stuff that matters.
Re:How to distort Scrum until it no longer works by bgro on Friday October 07, 2022 @02:18PM (#33125039)
I'm probably doing standups wrong, but I find it useful for devs to (briefly) talk about what they're working on. Bring up something you're struggling on and maybe I can jump in and help. Let people know you're working on a hotfix today, so try to not bother you. Get early feedback on priorities from the PM if you're going down the wrong path or a customer changed their mind on something you didn't hear about.

I also like to have a casual dev text chat going throughout the day so you can post things like "Why isn't customer history appearing on this page?" "That page uses a one-off modified version of that query that doesn't grab history because we don't need to display it there. It used to increase load time by 30%."

Sometimes the flow of this is just easier in person, and a dedicated short meeting where everyone speaks up about their own work doesn't feel as much like backseat accusations.

It does require people actually feel comfortable asking for help, and it requires people to volunteer their guidance.

As I see more and more devs and different work places, I can't believe how common it is to just sit in your corner and struggle while refusing to ask for help and refusing to speak up when someone on your team is actually asking for help.

Is this communication failure the norm at your places of work? What's the deal?

Re:How to distort Scrum until it no longer works by troupe on Friday October 07, 2022 @02:40PM (#33125292)
Are you getting value from those meetings? Are you willing to try new things if someone has a suggestion that might make it better? If so you are doing it right..regardless of what anyone else says.
Re:How to distort Scrum until it no longer works by MartinCron on Friday October 07, 2022 @02:27PM (#33125135)
I'm probably doing standups wrong...

And then you describe some of the healthiest standup culture I've seen...

Re:How to distort Scrum until it no longer works by bgro on Friday October 07, 2022 @05:36PM (#33127152)
The ones I run sound like they technically match what people complain about. Sometimes I open with a brief joke during setup to ease people in. I never see people zoning out or getting distracted when I'm the main experienced dev.

Other teams and companies I've been at/on or read about do all these things people are complaining about. Either people drone on too much every day, or in some teams they're quickly yelled at by the scrum master if they ask any questions about a story or go into any real detail about their work. "Take it offline!"

Sometimes it's warranted but I'll tie it in with my next thought... I notice people who don't feel comfortable asking for help / offering help are often new people to the team or remote workers (pre-covid). I think they feel disconnected from the team so they don't know how to connect the same. Or as I said before, it feels like this may just not be a normal thing elsewhere?

That disconnect can lead to droning on about every unimportant thing you did to try to justify that you're actually working. I don't know how I'd get around this if someone didn't get the hint with the rest of the team's style after a few standups if they were the only one doing this... But it seems like it's everyone else.

I've had veteran devs join my standup before and talk over me to summarize what they think I was saying. When they do it to someone (usually a quieter person) on my team, I can intervene but it's harder when it's against myself in case I truly was droning on. (Why doesn't anyone else ever speak up and defend others when this happens?)

These people never really seem to adapt to the team vibes because they're never really integrated in. They usually try to turn it into the scrum very basics of what you did, any blockers, then abruptly move on. I notice my team often starts zoning out and feel afraid to ever speak up in fear of "wasting time" or getting a snappy 1 sentence solution that doesn't work thrown at them every time this happens.

I've also gotten screamed at by sitting-in tech leads from other teams for bringing in my laptop to discuss a technically confusing series of emergency hotfixes my team was working on that morning that nobody else was on the same page about. "This meeting is for brief updates! Not planning!"

There was another time I was running late where a project manager encouraged everyone to go around the room to do an offensive impression of me I later heard about.

I also had a standup where another senior dev turned it into a leetcode interrogation ambush for some reason. I think he was trying to make me look bad but I was able to answer everything... He kept escalating the questions while everyone quietly sat back.

I just don't understand why nobody except me seems to ever speak up about these sorts of bizarre situations. If you don't like how stand up is run, why don't you speak up about it? If people are wasting time in standup, talk to them or their boss or the whole team about it. Especially if these are people you've known for months and months and have a connection with.

I don't comprehend sitting quietly when the quiet person is constantly interrupted, or how nobody can speak up about a room of people ganging up on one person for an interrogation or to go around the room with edgy targeted jokes.

Re:How to distort Scrum until it no longer works by breakpete on Friday October 07, 2022 @04:03PM (#33126248)
You are not doing it wrong.

Standups can be traced back to the Scrum practice Daily Scrum. The Daily Scrum is a short (max 15 minute) synchronisation meeting for developers. It is explicitly not a status meeting for PMs. It eventually became known as a standup because people figured out that it was easier to keep the meeting short when you were not sitting down.

Scrum became popular, but it didn’t really make room for traditional project managers. So what to do with all the PMs? Teach them to be Scrum Masters.

This is where things started to go downhill. Most PMs just kept doing what they had always done, just using different names.

And so standups became hour long status meetings, inspect and adapt, sustainable pace and other good things were replaced with micromanagement and death marches. Dark Scrum was born.

This is of course greatly simplified. Agile Consultants and certification peddlers are also to blame.

Re:How to distort Scrum until it no longer works by qqtt on Saturday October 08, 2022 @02:16AM (#33130216)
> I'm probably doing standups wrong, but I find it useful for devs to (briefly) talk about what they're working on.

I agree, regular communication within a team is healthy, but the way stand ups tend to manifest themselves is a meeting every single day where people feel compelled to share a status update. It would be rare for an individual to be blocked every single day, and thus this becomes a wasteful ceremony of going through the motions of giving status updates.

If team communication is healthy, there really isn't a need of daily stand ups. Individual team members will know when to escalate being blocked, and loop in the right people at the right time. If you are inheriting a dysfunctional team, daily stand ups can be a way to get the team back on track. For new members of the team, having a mentor to do frequent, even twice daily check ins, can be helpful on getting them up to speed.

But for high performance teams who have been operating together for years, daily stand ups are often a waste of time, and a needless addition to the calendar.