463
Scrum (media.mas.to)
all 39 comments
sorted by: hot top controversial new old
[-] anti_antidote@lemmy.zip 34 points 1 year ago

Agile is legitimately good and is the bar for how software should be built as a team. Enterprise scrum is objectively bad and I don't understand how anyone gets any amount of work done under it.

[-] quicken@aussie.zone 4 points 1 year ago

A good summary. Maybe enterprise any framework? SAFe, Spotify or whatever the agency has trademarked

[-] captcha@hexbear.net 27 points 1 year ago

Scrum is agile that puts the needs of management first.

[-] quicken@aussie.zone 14 points 1 year ago

The early days of scrum was very anti management. Self organising teams have no need for managers. But they soften all that and it took off

[-] wellnowletssee@sh.itjust.works 8 points 1 year ago

Correctly implemented its the exact opposite. But that seldomly happens, often due to management.

[-] fer0n@lemm.ee 17 points 1 year ago* (last edited 1 year ago)

I quite enjoyed reading Scrum: The Art of Doing Twice the Work in Half the Time. It’s not the book that people are mad at, it’s the shitty implementation of what management thinks scrum is. Because they never read the book.

[-] yogthos@lemmy.ml 13 points 1 year ago

Thing is that when practically everybody ends up with a shitty implementation of scrum, maybe it is a problem with the methodology after all. At the very least this indicates that it's hard to get right in practice. I've worked on teams with certified scrum masters who went through training courses, and it was still shit.

[-] fer0n@lemm.ee 10 points 1 year ago* (last edited 1 year ago)

I think the methodology is fine and it certainly isn’t complex. It’s just difficult to start using it when the corporate culture isn’t able to adapt and change it’s structures, that’s the hard part. Also a topic in the book.

Scrum is "bottom up" and the scrum master doesn’t manage anyone or anything, they are there to serve the team and get rid of obstacles. The team is empowered. If there’s a "manager" for the team, that’s already a mistake. That role doesn’t exist in scrum.

[-] space_comrade@hexbear.net 13 points 1 year ago* (last edited 1 year ago)

It’s just difficult to start using it when the corporate culture isn’t able to adapt and change it’s structures, that’s the hard part.

Yeah but that's almost every company ever. At what point do you blame the methodology then if it doesn't work properly almost anywhere?

I feel like scrum and agile in general are almost religions at this point, just blind belief in a system you haven't really seen work properly ever but you still believe in it.

[-] fer0n@lemm.ee 8 points 1 year ago* (last edited 1 year ago)

I get your point and maybe there’s a better alternative to scrum that keeps the culture and structure intact.

I might be wrong here, but as I see it scrum is fixing problems by changing the team structure itself. If that structure is really the main issue, you can’t not make that structure change, call it scrum when it actually has nothing to do with it, and then blame your inability to adapt on the methodology you’re not using. Because there are teams that are able to adapt and use scrum successfully.

[-] space_comrade@hexbear.net 7 points 1 year ago* (last edited 1 year ago)

I don't think you can truly change anything with these methodologies. At the end of the day most companies are still privately owned companies, and you as a developer will do what the owners and/or the managers tell you to do. The owners aren't going to delegate important decisions to developers unless it's a really technical thing. The part where "developers take control" in scrum is bullshit and always will be by necessity of how our economic system works.

I feel like Scrum and similar stuff just serves to obfuscate real material relations in the company that aren't going to change no matter how many story points you assign to this or that or how many scrum masters you have. Also it makes micromanagement easier I guess.

[-] fer0n@lemm.ee 4 points 1 year ago

If you haven’t already, I’d encourage you to take a look and read the book. At the very least it’s some interesting stories being told.

[-] space_comrade@hexbear.net 3 points 1 year ago* (last edited 1 year ago)

I don't read such books because they're almost always written by "consultant" grifters trying to make money off of proselytizing the latest bullshit corporate fad. And it's almost never based on actual data or a coherent theory, just gut feelings and a few anecdotes. My own felt experience and that of my colleagues is enough to confirm that it's all just corporate ideology bullshit.

[-] CloverSi@lemmy.comfysnug.space 5 points 1 year ago* (last edited 1 year ago)

You've never read the book in question... Because you think it's filled with gut feelings and anecdotes... Which you know, because of gut feelings and anecdotes...

[-] fer0n@lemm.ee 5 points 1 year ago* (last edited 1 year ago)

Okay different question then. Judging from your stance towards scrum, I’m assuming you have worked with it before and it didn’t go so well? What parts were terrible and how was it set up if I may ask?

[-] space_comrade@hexbear.net 2 points 1 year ago* (last edited 1 year ago)

I worked in a large company where they used scrum and I just don't see where it ever helped me. Sure I guess forcing you to write down in Jira or whatever all the features/bugs you worked and will work on is good practice but I can do that without scrum too.

Daily standups were annoying and rarely ever helped people resolve issues that wouldn't have been resolved by just talking to some people directly, which you would have done anyway regardless of the standup meeting.

Sprint plannings were useless and amounted to either taking 3-4 things off the top of the backlog or the manager forcing their priority feature in the sprint.

Story point estimation was awful, everybody pretends the points aren't just measures of time but rather this complex abstract of multiple factors and whatnot but everybody still just converts them to time in their head anyway because of fucking course they do because the time estimate is the most important thing to know and the only truly objective measure of task difficulty.

In the end management gets what it wanted when it wanted no matter our complaints because that's how things work in privately owned companies. Scrum for the manager at worst just becomes another bureaucratic hoop they need to jump through to get what they want.

This is also the experience of my colleagues from other companies, and also I read a lot of similar anecdotes online. I have literally never heard anybody seriously claim scrum works great in their company that also wasn't personally invested in the ideology like a "professional" scrum master or consultant or whatever.

[-] fer0n@lemm.ee 2 points 1 year ago

Developers don’t take control in scrum. They are empowered to work autonomously, which is a big difference. Devs provide the complexity of stories and the PO decides in what order the team is tackling them.

Scrum doesn’t mean everyone just does whatever they feel like.

[-] space_comrade@hexbear.net 4 points 1 year ago

They are empowered to work autonomously, which is a big difference.

That means nothing to me. Just platitudes. I've never felt "empowered to work autonomously" in scrum.

[-] fer0n@lemm.ee 2 points 1 year ago

They decide how to implement it themselves is what I mean by that, the user story doesn’t give technical implementation details and it doesn’t give a specific solution. It gives you the problem and reason

[-] space_comrade@hexbear.net 4 points 1 year ago

What's the difference between that and just receiving orders from managers, like every other office worker in any company ever?

[-] whitewall@lemmy.ml -3 points 1 year ago
[-] yogthos@lemmy.ml -2 points 1 year ago

You misspelled capitalism there.

[-] whitewall@lemmy.ml 2 points 1 year ago
[-] ensignrick@startrek.website 15 points 1 year ago* (last edited 1 year ago)

I scrum. You scrum. He she me scrum. Scruming. Scrumology. It's first grade SpongeBob.

I for one just look at my sprint and scrum meetings as pie in the sky goals and just keep working on the task I'm doing with the sprint goals as a "lol". If I was to follow the sprint goals and deadlines nothing would be working correctly.

[-] wellnowletssee@sh.itjust.works 2 points 1 year ago

This sounds like poor communication between dev and PO.

[-] jadegear@lemm.ee 4 points 1 year ago

Depends. I've had plenty of tough calls with management laying out the impossibility of desired schedules only to have the Jira board estimates fudged in their favor, or similar, which puts pressure on the team to deliver on timelines they never would have estimated for themselves.

Ultimately it's a question of who's working by whose estimates.

[-] wellnowletssee@sh.itjust.works 1 points 1 year ago

Management not admitting time estimates from dev, management not willing to understand dev estimates (to maybe find a smaller solution together) and/or dev committing to not reachable deadlines are not scrum problems.

[-] anarchist@lemmy.ml 14 points 1 year ago

Oh but you just aren't doing scrum tm right!!!!

/s

[-] entropicdrift@lemmy.sdf.org 10 points 1 year ago

Kanban is love, kanban is life

[-] wellnowletssee@sh.itjust.works 7 points 1 year ago

Scrum uncovers problems the organisation was not aware of before which is why it has such a bad reputation. „What do you mean I can’t push my feature requesting in to dev when ever I want? I thought we are agile?“

[-] PreviouslyAmused@lemmy.ml 4 points 1 year ago

This just became a fucking job …

this post was submitted on 25 Aug 2023
463 points (96.2% liked)

Programmer Humor

32490 readers
564 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS