That is my point.

There is nothing wrong with the methodology itself. The question  is does it
apply to our projects  or not? My answer  is, in most cases; it does not.

The methodology should always be selected based on the nature of the
project. The question is who has that knowledge?

Reza made some comments about documentation. I wasn't talking about the
documentation. Documentation is part of the process. I was questioning the
validity of the documents produced within the process; which indirectly
questions the validity of the process  itself.

I am sure neither me nor Ara meant eliminating it. What I was trying to say
was that people usually spend a lot of time on making decisions on how to do
the things without actually doing it. The one and only goal of the software
development is to develop the software in a reasonable time. The software
needs to be valid and reliable. Do we usually follow this path?