this post was submitted on 17 Jan 2026
569 points (98.5% liked)

Programmer Humor

28550 readers
1172 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Unleaded8163@fedia.io 32 points 1 day ago (3 children)

My only requirement for team processes is that they be mostly up to the team. Absolutely some type of structure is needed. If something isn't working for the team, they need to have agency to address that, whether it means adding, removing, or changing something.

[–] azertyfun@sh.itjust.works 39 points 1 day ago (4 children)

Well, yeah, that's what Scrum is. From the guide which takes maybe 10 minutes to read

Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are also self-managing, meaning they internally decide who does what, when, and how.

That's not a throwaway sentence - it is fundamental to how scrum works and that is reinforced throughout the scrum guide.

Every conversation about Agile and/or Scrum being "the worst", after some prodding it turns out that their company has refused to read or implement one or several of the fundamental principles, often without even being aware that was an essential requirement. You're baking a cake and you decided to not use any butter, that's on you champ, don't blame the fucking recipe.

The biggest valid criticism of scrum is that the thing that makes it so great - its structural empowerment of individual teams - is also what makes it structurally incompatible with any traditional top-down management style. The company must fundamentally be (re-)organized to have a flat corporate structure within its R&D department - most are simply incapable of mustering the necessary changes, if only because too many middle managers' jobs are at stake. So they call their middle managers "POs" or "Scrum Masters" and wonder why their version of Scrum sucks.

[–] RustyShackleford@programming.dev 1 points 5 minutes ago

So they call their middle managers "POs"

A. k. a., "Pieces Of shit".)

their company has refused to read or implement one or several of the fundamental principles

The companies I worked for just kept doing shit the same way they always had but renamed everything with terms borrowed from agile.

[–] Unleaded8163@fedia.io 5 points 1 day ago

I reached for the up button about five times reading this. I absolutely 100% agree. Agile, and all of it's little branches, were created by self managing teams. Each team did it differently so named what they were doing differently, we got XP, scrum, kanban, etc. Spoiler alert: it wasn't the specific flavour that led to success, it was the diverse, empowered, self managing team of mature, talented people. Get yourself a team like that and the rest will care of itself.

[–] n7gifmdn@lemmy.ca 2 points 1 day ago

As a PO I resemble this remark.

[–] ChickenLadyLovesLife@lemmy.world 7 points 1 day ago (2 children)

My favorite approach to team processes was to work entirely alone and do everything by myself.

[–] mojofrododojo@lemmy.world 4 points 1 day ago* (last edited 1 day ago)

a true team player. prob mvp too.

[–] Unleaded8163@fedia.io 4 points 1 day ago

I can get behind that sentiment.

[–] red_tomato@lemmy.world 13 points 1 day ago

This is what’s most important. Allow for experimentation!

What works well for one team might not work well for your team. What worked well for your team 1 year ago might no longer be what you need now.