[SeeDave]

I totally understand Waterfall vs Agile. Story points, grooming, estimates, continuous release, potentially shippable product, etc.

I actually agree with the Scrum Guide [0], so my problem isn't with Agile; it's with this specific Agile Consultant who doesn't seem to "get" that process is often a proxy for talent/trust/respect and is just winging-it/BSing us all.

Imagine Bill Lumbergh from Office Space with a ton of two-day CS[a-Z]+ certifications who has never written a single line of code, designed a relational database, spec'ed out an API, etc. micromanaging every meeting while fundamentally misunderstanding the concepts of "collaboration" and "cross-functional teams." He knows what to talk about but has such a superficial understanding that he doesn't know why it's useful or when to apply concepts. Google 'Cargo Cult Agile'

[0] https://www.scrumguides.org/scrum-guide.html

[Bootwizard]

Well that does suck. I had the opposite experience with Waterfall and Agile.

My previous job (Waterfall) used such a heavy process that I was coding 10% of the time. Which is what I was hired to do. I'm a software engineer. Coding 10% of the time is unacceptable. But everyone working there had been doing that, some of them for 20+ years. It was like a prison sentence.

Luckily I was able to escape and got a fantastic job working at a small game studio that loosely uses Agile. The process is the last thing on my mind, and most days I don't even look at our Jira board. Maybe once or twice a week I look at it.