this post was submitted on 25 Sep 2023
45 points (88.1% liked)

Programming

17364 readers
260 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 [email protected]



founded 1 year ago
MODERATORS
 

A quick rant about weaknesses of agile

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago (1 children)

The whole point of Scrum is to use the retrospective to stop doing what doesn't work and start doing what does.

That is only something useful if you can use the retrospective to through out Scrum. Otherwise it is yet another Scrum timewaster.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

@btaf45 in my case, we as a team could have done that, because we didn't have management dictating how we did anything. It was our choice to do what worked for us, and it was a valuable tool for dealing with whatever got thrown at us.

Now I'm working in a different place that dictates Agile and Scrum to be done Their Way, on top of a project that's largely waterfall-like to begin with, and I'm starting to see why people say it doesn't work.

It works, BUT, only when you're using it as the right tool for the right job and not when management decide to misapply it as a hot new planning methodology.

[–] [email protected] 1 points 1 year ago

@btaf45 tagging @programming so that this federates properly from Mastodon to Lemmy