Just think of a scenario, where your requirement are fixed and scope will not expand with course of time, then you can use waterfall methodology.
Waterfall methodology includes the stages of SDLC into linear sequential manner. The stages are : Requirement elicitation and planning, Analysis and design (UML), Implementation, Testing, Release and deployment and Support and maintenance. All these steps are performed in sequential manner. As the team moves from one step to another, it is very difficult to go back to previous step. It is because the output of previous stage acts as input of next stage.
When to use waterfall methodology:
- When requirement are known in advance.
- Product or project definition are stable.
- Technology is well understood.
- New version of existing product.
- Porting and existing product to a new platform.
Weakness of waterfall methodology. are as follows:
- Big bang approach
- Cannot cope of with changing requirements.
- More time and effort consuming
- Linear approach
- Does not include risk factor into consideration.
The main point to see is when to use waterfall or agile methodology. The basic difference which is basic is when you the requirements well in advance you can go for waterfall methodology. But in this changing world only Government projects and few other projects have fixed requirements and known scope. Hence it is not feasible to use this traditional methodology. Therefore, Agile (adaptive methodologies) came into picture.
Every time the question is asked, What things are to be kept in mind when implementing the project using Agile methods? There is no direct answer to such question. It depends majorly on organization structure and culture that if it is feasible for adopting agile methodology or not. We are going to see the scrum framework in the next upcoming blog. Till then practice this framework for the project with fixed scope of requirements and approved budget and time.
For any query, please write in comment section or contact me through my email id.