Thanks for replying. What I want to say mostly is, I don't like to see the agile process be the top level driver of the project development. Just imagine you are making a chair, do you know agile. Trust me, most of people who makes chair doesn't know agile at all. So my point is that you don't need agile to be successful, if you agree with that, then don't make the agile that the only way to success.

When you close a door, it might not be open again. So before you close it, maybe just close a little bit instead of closing it entirely down. I'm referring to waterfall. By the way I'm not favoring waterfall in the article either. I'm just saying if there're two ways, you shouldn't eliminate one of them completely. That's all.