Why do a lot of developers dislike Agile?
Sometimes Agile can hold up you, or the company's progress if it was over-used. let's take this example, If I have a startup, a small team, and a clear plan for my startup I would definitely go for WaterFall Technique because you sometimes you have to _"Move fast, Break Things", _Once you are there, and all of your developers got the idea and aim for the startup they are working for, hold them down, take a deep analysis of what's been done, and how can we learn from the mistakes done so far.
Move then to (Agile) because once the project has gone big, you can't control all of the areas of your startup, and all of the written code and business logic with Waterfall.
Agile has its pros and cons. I do like agile for several reasons but I also don't like a couple of things about it:
I think everyone wants to move fast, isn't it? That being said, I fail to understand why we are so much hung up on terminology.
I believe in keeping things simple; and the following, IMHO is the best process to follow.
All we are doing is either building a feature, or fixing bugs. When you do the former, you are ought to have something like a design document with the tasks broken into small steps, each of which should ideally take a maximum of a day. If you for some reason don't finish your micro-task, you explain why and move on, and try to get it done the next day.
What's also important is assigning the correct priority to our issues. It's important to build just one feature at a time before jumping onto fixing something else just because it's out there or easy to fix. When you move around too much, it adds to the pressure and you end up shipping nothing.
stuff ;)
j
stuff ;)
Because they don't understand it and most companies implement it wrong.
I had to read up on it and watch a lot of talks to stop disliking it. The ideas behind the agile-manifesto are great. Ownership to the devs, working together, small iterations, ....
But than consultants came in :) and all of the sudden there is a market and not principles and ideas, but structure and 1 solution to rule them all.
The idea of small iterations gets raped to micro management, the scrum master is not for the team but a PM in disguise or a power hungry colleague; who doesn't understand that he should be there to help, not to control, you.
..... It's still a lot better than waterfall but it doesn't feel like it. Change is always long an complicated.
That's for scrum and lets be honest .... scrum is the only one that made it into big business. So it's the only thing that will be hated .... Bad implementation, egos and so on .... that's my experience with it.
The problem is .... as always the move from "idea/believe" to "religion" an idea/believe is allowed to change and to adapt. Religion is an dogmatic institution that has no room for change because it has a power structure.
If the devs were allowed to actually just pick what they need for their team instead of "doing it the right way", whatever that means. The whole "agile" BS would be nice.