Agreed completely. I was (and still are) on couple of different companies and teams practicing "Agile" and those daily standups are more like daily blamefests. God forbid you get stuck somewhere and need someone's help. Then you have to apologize because everyone thinks that you're lazy or incompetent and holding everyone down. Also if people wanted to know what I did yesterday, they could have a peek at the tickets they want us to keep up to date but no, they want us to say it anyway. Also that stupid "do you have any blockers" question. No I don't have any blockers, it is this bullshit technology/service everyone wants to use today, and discard tomorrow which I somehow need to be an expert of with 30 min of looking at some incoherent manuals.

It seems to me, that all these buzzwords and meetings are just a way to always keep you "busy" (or at least looking busy), to always have some kind of fire below your feet so you don't "slack off" (or have a bit of free time to actually gain or sharpen the skills you need for the same company...). I'm just tired of this. In a way, good teams will be good, and bad teams will be bad, doesn't really depend on whatever process they have.

Agile lives and dies by communication. Both amplitude and SNR matter, and have always been present in the proper ratios in the best engineering.

Agile is very open to attack when it veers from a list of useful practices to try out in a given context and instead turns into dogma.

> workers are forced to enumerate what they did and delivered in a short time frame

This is one example how processes supercede people even though that is against the original agile manifesto.