Waterfall model vs Agile in ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2020 09:33 AM
Can anybody explain which methodology is better to follow in ServiceNow and why? In terms business,flexibility perspective

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2020 09:38 AM
Hi Nick,
Both methodology has its own use case please check below link to understand the difference
https://www.guru99.com/waterfall-vs-agile.html
Please mark correct and Helpful if it helps
Thanks and Regards
Himanshu Dubey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2020 09:47 AM
ServiceNow is specifically built to run both methodologies. Further it is built to facilitate both methods running together on the same project.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-28-2020 10:25 AM
- Waterfall is a Liner Sequential Life Cycle Model whereas Agile is a continuous iteration of development and testing in the software development process.
-Agile methodology is known for its flexibility whereas Waterfall is a structured software development methodology.
-Agile follows an incremental approach whereas the Waterfall methodology is a sequential design process.
-Agile performs testing concurrently with software development whereas in Waterfall methodology testing comes after the “Build” phase.
-Agile allows changes in project development requirement whereas Waterfall has no scope of changing the requirements once the project development starts.
Waterfall Model followed in the sequential order and so project development team only moves to next phase of development or testing if the previous step completed successfully.
Agile methodology is a practice that helps continuous iteration of development and testing in the software development process. In this model, development and testing activities are concurrent, unlike the Waterfall model. This process allows more communication between customers, developers, managers, and testers.