When not to use Waterfall Model
a thread...
(Part - 2/4)
a thread...
(Part - 2/4)
Before we proceed further,
I would highly recommend reading Part 1, where I've described the Waterfall Model.
I would highly recommend reading Part 1, where I've described the Waterfall Model.
Let's continue, and see a few popular reason why the waterfall is not used nowadays!
When the time to market is too long:
Why?
Suppose the software is completed after a year, within that time:
The market has changed a lot.
Competition has come up with some new & exciting features.
The user is no longer interested in the feature, etc.
Why?
Suppose the software is completed after a year, within that time:
The market has changed a lot.
Competition has come up with some new & exciting features.
The user is no longer interested in the feature, etc.
When Project is Big and Complex:
Complex and big projects many times bring in more changes in customers' requirements.
The waterfall is not good at accepting changes at the later stage.
Inherently, big projects have a longer time to market.
Complex and big projects many times bring in more changes in customers' requirements.
The waterfall is not good at accepting changes at the later stage.
Inherently, big projects have a longer time to market.
When the client does not know what they want:
In such a case, the client will keep iterating over and over many times the requirement.
After developing the whole thing he might ask to scrap everything and ask to work again.
This will lead to a waste of time and money.
In such a case, the client will keep iterating over and over many times the requirement.
After developing the whole thing he might ask to scrap everything and ask to work again.
This will lead to a waste of time and money.
I've only covered a few popular reasons!
What are the other reasons for not using the waterfall model?
Share me in the comments below! Let's discuss them.
What are the other reasons for not using the waterfall model?
Share me in the comments below! Let's discuss them.
Conclusion:
The waterfall is a very old technique. Due to the above problems, it is not popular nowadays.
The solution to all the above-mentioned problems is AGILE.
It's everywhere nowadays!
In the next thread on Friday, we will see an Intro to AGILE.
The waterfall is a very old technique. Due to the above problems, it is not popular nowadays.
The solution to all the above-mentioned problems is AGILE.
It's everywhere nowadays!
In the next thread on Friday, we will see an Intro to AGILE.
In this series of four thread, I'll be giving an "Intro to Agile and Scrum".
Starting from the Waterfall Model, It's Issues, then I'll talk about Agile and one of it's popular framework Scrum.
We'll be having super fun while learning don't miss out.
Starting from the Waterfall Model, It's Issues, then I'll talk about Agile and one of it's popular framework Scrum.
We'll be having super fun while learning don't miss out.
Namaste, I'm Vikas!
I write a thread every Mon, Wed & Fri about Java, Javascript & Fullstack Development.
To read all my future threads follow @vikasrajputin
I write a thread every Mon, Wed & Fri about Java, Javascript & Fullstack Development.
To read all my future threads follow @vikasrajputin
Part 3 - What is Agile? Is out now...
جاري تحميل الاقتراحات...