As I told you yesterday, now I am working on the methodology stuff and investigating which one is right for my company.
I prepared a note on the classic, predictive, rigid waterfall methodology and it is given below. This is based on my point of view on the methodology and may vary from yours!

Waterfall methodology is like a production line. Here, strict controls are placed on the deviations from the plan; to ensure what is produced is what was designed. The positive side of this approach is, it is supremely logical; think before you build, follow a plan, and keep everything organized as possible.
And the flipside is, this approach requires all good ideas come at the beginning of the SDLC where they can be incorporated into the plan/design – almost impossible!
This approach hinders innovation, project managers often try to categories the new ideas as scope creep and believe their job is to save the project from changes !
Since this is a resitance process it results in low quality mediocre products. The product will be only as good as the initial idea, not the best.
Home ground for waterfall / plan driven development methodology is
- High criticality of the work
- Jr developers as the project team
- Large no of developers and co-location is not easy
- Culture that demands order