What is a downside of using the traditional Waterfall approach?
A. It requires a larger commitment for collaboration between project team members than Agile.
B. It prevents the development team from quantifying the effort, time, and cost of delivering the final product.
C. It can increase costs and delays if updates are incorporated in the development process after the planning stage.
D. It lacks detailed documentation, leading to misunderstandings and difficulties between the team members.
E. I don't know this yet.
Answer: Option D)
The downside of using the traditional waterfall approach is that it lacks detailed documentation, leading to misunderstandings and difficulties between the team members.
Explanation: It lacks detailed documentation, leading to misunderstandings and difficulties between the team members. The drawback of the waterfall effect is that it does not permit much thought or modification. As the application is in the testing phase, it is very challenging to go around and change something that was not well-documented in the conception phase. The other options are incorrect to the given question. Hence, Option D) is the correct answer.