What is a downside of using the traditional Waterfall approach?
Answers
Answer:
It lacks detailed documentation, leading to misunderstandings and difficulties between the team members.
Explanation:
Downside of using the traditional Waterfall approach:
1. Waterfall is not suitable for projects where requirements are at a moderate to high risk of changing. Waterfall does not easily accommodate changes in requirements like new features or a change in the target market. Changes require rework and may impact the entire project plan.
2. The Waterfall approach does not allow for much reflection or revision.
Because the client is unable to see progress until a phase is completed, it does not allow for much reflection or revision.
3. The client tends to end up with a product that doesn’t meet their needs. While there’s nothing wrong with being decisive and knowing what you want, that can be a problem for the programmer that has to create something for you.
4. It can be a waste of resources if the product is useless to the client, who then needs to start over from scratch with a different vendor.
5. It’s expensive and slow because you need to get sign-off from the client after each phase of the project, which often leads to rework and wasted money and time. One of the biggest disadvantages of using a Waterfall approach is that it’s expensive and slow.
#SPJ2
https://brainly.in/question/3758350
https://brainly.in/question/10592061