Except from this image, what is wrong with scrum? I have seen people shitting on it in here, that's why I ask. To me it looks like a more dynamic way of translating requirements into measurable results.
The only negative thing I think of is it does take a bit of fun out of programming
There was a long thread discussing agile development a few months ago, but the board spam killed it.
Nothing wrong with agile if its used the right way, and you have an engaged client. It's an effective way to do iterative development.
Pretty much that, if the requirements are unclear and that the client doesn't even know what it wants, or some other tricky part, it's better to have a tight iterative loop.
Otherwise it can have 1 week-1 month loop.
It might work in cases where you have developers with similar work ethics and level of motivation. Without that, and combined with weak management it can rapidly descend into a parasite/worker drone scenario.
Isn't that the case no matter what formal development method you choose?
This right here is the problem: in practice, most clients barely know what they want.
When the development team is doing agile but the business team is doing waterfall and there are sixteen "lead" designers that can't fucking finalize a single fucking mockup and over thirty business "owners" who can't fucking reach a consensus on features. Everybody wants agile timeframe with waterfall requirements and all that leads to is the dev team sitting on their asses for months on end until finally getting some god damn fucking requirements two weeks before the deadline.
The point of agile is to break up tasks into small and quick-to-deliver tasks. The point is that when requirements (inevitably) change during the progression of development, the team can quickly change direction as compared to other development models with longer iteration periods.
Good job user! You parroted the words! That is indeed the point of agile. The other user was making the point that that rarely happens.
Zig Forums posters tend to be on the worker end of software development, which means we would really like to have mostly-stable requirements. You'll find a lot of people with the opinion that if a customer dosn't know what they want, they have no business getting software built.
I see a lot of posts that just parrot the words on Zig Forums. What the fuck is up with that? Do they think that they'll impress someone with their definition reading?
Anyway, I worked on a project with Agile and I hated it. I had no creative control over it whatsoever and was as boring as can be.