You don't need Kanban, you just need to do Scrum right.
It seems most people who are complaining about Scrum, are really complaining about the lousy implementation of it in their company. Which tends to be the result of lousy management.
With lousy management, any process will be a pain. Doing Kanban with a manager behind your desk asking why your feature is not ready yet isn't a pleasure either.
There also seems to be some misunderstanding about speed of development and Scrum; some posters are complaining that Scrum slows them down. Yes it does! And this is on purpose. Scrum focusses on delivering business value, not on delivering lines of code that possibly nobody needs.
So there are moments in the development process when feedback is gathered from stake holders. This is important, because it gives them an opportunity to adjust what's being built, or even switch to a more important feature altogether.
The downside is that this takes time. But the upside is that you will have far greater chance of delivering something that is actually needed.
It is too vague. Compare to the ten commandments. Half of them are repeating detailed versions of "don't mess with your neighbour" to make things clear.
The Agile manifesto should have been written in a similar style ...
It seems most people who are complaining about Scrum, are really complaining about the lousy implementation of it in their company. Which tends to be the result of lousy management. With lousy management, any process will be a pain. Doing Kanban with a manager behind your desk asking why your feature is not ready yet isn't a pleasure either.
There also seems to be some misunderstanding about speed of development and Scrum; some posters are complaining that Scrum slows them down. Yes it does! And this is on purpose. Scrum focusses on delivering business value, not on delivering lines of code that possibly nobody needs. So there are moments in the development process when feedback is gathered from stake holders. This is important, because it gives them an opportunity to adjust what's being built, or even switch to a more important feature altogether. The downside is that this takes time. But the upside is that you will have far greater chance of delivering something that is actually needed.