Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

The main problem with the Agile industry is that the certificate mills give people the idea that they have to know nothing about software to work on/in software.

Also Scrum as outlined by people like Jim Coplien would probably be kind of fine for certain set ups, but only a few agile coaches, POs or SMs know Scrum that well, instead it's a weird mix of apocryphal, illogical practices and superficial knowledge that, coupled with an inexperienced dev team, is similar to a giant Molotow cocktail that will sooner or later explode.



view as:

Scrum is basically a set of necessary but not sufficient processes. I was sceptical about it, took the course, and aced the test.

Scrum itself is like the rules for holding a good meeting. It's good common sense advice that I don't think you can actually reasonably object to.

If it's not in the Scrum guide, it's not Scrum, truly find something objectionable in that: https://scrumguides.org/scrum-guide.html

But in achieving that flawesseness, they made it so broad and vague that you really need to add additional practices to it. And then you got to be careful, mature, and thoughtful or else it's gonna turn into a shitshow... but if you just do Scrum you'll end up as a shitshow anyway.

PS- to me personally the biggest flaw is that so much hinges on the definition of done being correct, and that is at least half the battle in dev and can almost single handedly save or sink an organisation in itself.


Legal | privacy