Hacker News Reader

Comment by Bootwizard | Hacker News Reader

Well I gotta say, I've worked in Waterfall and now Agile and I couldn't even explain how much better it is. I feel like I can actually do my job now instead of worrying every day about process. You won't know how much better you're going to have it until you switch.

Waterfall is a shackle around your hands and feet keeping you from getting actual work done.

That being said, if you have an Agile consultant who is not able to convince you (because he doesn't sound like a nice person to work with) that sucks, and I hope you can find someone else.

View on HN

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

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.

I hear what you're saying but in my experience, waterfall vs. agile is rarely the core of the issue that the company is trying to solve for when they bring in these consultants to 'fix' things. It just leads to more dissonance.

I got taught waterfall at university and included iterations and being able to go back the way. The only real change with Agile is less specification (not necessarily good) and more frequent iterations (good).

Though as I have said on here before no one can actually agree on what Aglie actually is, so maybe whatever you are doing is working for you, so that's good.

Reply on news.ycombinator.com