• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Agile vs Spiral, which one is better and why?

 
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Which Software development methodology is better out of Spiral and Agile and why?
 
author & internet detective
Posts: 40211
816
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's not that one is better. They are different and make sense on different projects. According to wikipedia, the spiral model is best for large expensive complicated projects. Spiral is like little waterfalls. If the customer need to specify things in advance, it is better than true waterfall.
 
Rancher
Posts: 4686
7
Mac OS X VI Editor Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm not convinced that there is any real difference between them. It is often a distinction without a difference.

 
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
To answer your question

Which Software development methodology is better out of Spiral and Agile and why?


The sweet spots of a process framework depends on the context of a project.
Without context no sensible comparison can be made.

 
Ranch Hand
Posts: 62
Hibernate Spring Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

According to wikipedia, the spiral model is best for large expensive complicated projects. Spiral is like little waterfalls. If the customer need to specify things in advance, it is better than true waterfall.


The reason for this is that in Agile model you have short sprints, with concentration on working software incorporating frequent requirement changes developed by a self disciplined/proactive team. So it's iterative and incremental approach suits well for smaller sized but highly dynamic projects.
Spiral model on the other hand is sort of repetitive waterfall model. Where each cycle focuses on working software delivered using proper processes and documentation. There is slightly more micromanagement involved and requirement changes are not incorporated at any stage of the iteration.
 
expectation is the root of all heartache - shakespeare. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic