Changes for page Waterfall In Software Development

Last modified by chrisby on 2024/05/20 08:43

From version 3.15

edited by chrisby
on 2024/05/05 09:13

Change comment: Update document after refactoring.

To version 3.16

edited by chrisby
on 2024/05/20 08:43

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -18,7 +18,7 @@
      * **No Room for Redesign**: After the design phase, there's minimal room for redesign, even if subsequent developments suggest the need.
      * **Wasting time in case of premature completion**: Time is wasted on planning and design, even though the tasks are completed due to fixed phase schedules.
  * **Prioritizing contracts over needs**: The waterfall model can sometimes prioritize contractual obligations over the evolving needs of the project, which can compromise the final product.
--* **Delivery delays**
++* A common consequence is **delivery delays**:
      * **Frequent deadline overruns**: The inflexible nature of waterfall, combined with the unpredictable nature of software projects, often results in missed deadlines, extended timelines and added stress.
      * **Late reporting of delays**: Due to the late feedback mechanism, delays are identified later, making it difficult to accurately estimate the actual project completion date.