Skip to Content
Last modified by chrisby on 2024/05/20 08:43
From version 3.14
edited by chrisby
on 2024/05/05 09:13
Change comment: Renamed from xwiki:Software Engineering.Agile.Waterfall In Software Development2.WebHome
To version 3.16
edited by chrisby
on 2024/05/20 08:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Waterfall In Software Development2
1 +Waterfall In Software Development
Content
... ... @@ -18,7 +18,7 @@
18 18   * **No Room for Redesign**: After the design phase, there's minimal room for redesign, even if subsequent developments suggest the need.
19 19   * **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.
20 20  * **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.
21 -* **Delivery delays**
21 +* A common consequence is **delivery delays**:
22 22   * **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.
23 23   * **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.
24 24