this post was submitted on 05 Jun 2024
412 points (94.4% liked)

Programming

17354 readers
338 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Windex007@lemmy.world 28 points 5 months ago* (last edited 5 months ago) (2 children)

I'll rephrase them, except in good faith:

  1. Talking directly to the people about the work is better than a 95 state JIRA pipeline

  2. Document your finished working work, not every broken POC, because that's a waste of time

  3. If the contract isn't actually going to meet the desires of your stakeholders, negotiate one that will

  4. If you realize the plan sucks, make a better plan.

My company paid to have Kent Beck come to workshop with our Sr devs. I expected to dislike him, but he won me over pretty quick.

I don't remember what it was, but someone was like "Kent, we do X like you recommend in the manifesto, but it creates Y, and Z problem for us"

And he was like "So, in your situation it isn't providing value?"

Guy was like "No"

"Then stop doing it."

It's not hard. It's the most fucking common sense shit. I feel bad for them because these guys came from a world where there were these process bibles that people were following. So they wrote like, basically a letter saying "if your Bible doesn't serve you, don't follow it"

And all these businesses dummies were like "oh look, a NEW bible we can mindlessly follow"

[–] best_username_ever@sh.itjust.works 8 points 5 months ago* (last edited 5 months ago) (1 children)

It assumes that: devs can and have the right to talk to the final user, devs can negotiate anything, and devs can make plans. Where I've used agile, the whole circus was taken hostage by the managers and there was nothing you could do about it.

You'll tell me it's not real agile, but it's like real communism, I've never seen it.

[–] Windex007@lemmy.world 0 points 5 months ago

I mean, I've never seen a real platypus but I'm not going to use that as a justification for why they can't exist.

I don't know what to tell you. It's a spectrum. I've worked in shops that claimed to be agile but to them, that just meant JIRA and story points. I've worked at places where agile meant having daily standups.

And I've worked places where there actually was a genuine attempt, and that was an awesome place to work.

[–] atzanteol@sh.itjust.works 5 points 5 months ago

Agile development reminds me of the Life of Brian.

He's giving sensible and well meaning life advice but all the people want is to follow the gourd.