Good Read. I refrain from being a fanboy of any specific development methodolgies \ process (rather I stay extremely wary when someone says "only this is method is the best" or "this is the worst"). I am sure your heart is at the correct place and you are not 100% hating incremental development either (it can be used when apt).

I rather look at s/w development as a truck driver having to deliver parcels (features\bugfixes \or an entire app). As the truck driver let me chose which truck I use , let me choose how much load I carry, let me choose what gear\speed I drive at during different stages of the delivery depending on how hilly \flat the terrain is. Hell, there may be times when I choose to use a bicyle instead of a truck when going short distance for a small parcel !!! Unfortunately the management who inpret agile wrongly are obsessed with constant velocity, constant delivery load by conveniently assuming the terrain to have constant slope or worse still assuming they can predict every obstacle on the route!!! And that's where the friction lies between engineers vs management causing engineers to hate the processes forced on to them.

Articles like these will cropping up until engineers are being forced by management to blindly follow certain "processes" under the disguse of "being agile" and when engineers revolt via words , there will be an army of agile defenders claiming that : "Agile doesnt enforce this and you are not doing agile correctly" ...thats the infalliable weapon of defenders of agile (I already saw some of the comments to this article 😉 ).