I think it worth to distinguish the concept of iterative development (basic idea behind all agile methods), agile methods (sets of rules and practices which can be used to do iterative development) and particular implementations of these methods. Idea is fine (after all requirements are still changing just like almost 50 years ago). Agile methods are more or less fine too, after all they usually a summary of experience. But just like any other idea in this world, they can be misunderstood, misinterpreted or intentionally screwed. This is what usually happens during particular implementations.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think it worth to distinguish the concept of iterative development (basic idea behind all agile methods), agile methods (sets of rules and practices which can be used to do iterative development) and particular implementations of these methods. Idea is fine (after all requirements are still changing just like almost 50 years ago). Agile methods are more or less fine too, after all they usually a summary of experience. But just like any other idea in this world, they can be misunderstood, misinterpreted or intentionally screwed. This is what usually happens during particular implementations.