Talk:Iterative and incremental development

message: Folks are mistakenly putting content here that should go to Agile Software Development
Text is not describing title, it is stating that it's a key part of Agile, then first section 
"The basic idea behind the agile method is", and many references listed here were lost
because they were agile so deleted as being Agile... People putting Agile content here is
a waste, put it where it will apply and be found.   
Markbassett (talk) 17:27, 28 August 2012 (UTC)
thread_title:  Move to Agile whatever is Agile and not about the Title topic 

message: What are the advantages of "V" Model over the other life cycle models. —The preceding unsigned comment was added by 209.78.112.253 (talk • contribs) 19:09, 19 January 2006  (UTC2)
The proper place to see that is in the article about v_model 
Markbassett (talk) 15:14, 28 August 2012 (UTC)
thread_title:  [[V model]] 

message: Agree with the merge of Incremental build model.
# A quick Googling of incremental build model shows that the term is hardly in use.
# The article is a stub, and is vague to the point of being useless.
# It is redundant to the text in this article.
—The preceding unsigned comment was added by 65.222.202.26 (talk • contribs) 18:45, 13 March 2006  (UTC2)
Perhaps a bit too much emphasis on methodology guideines. In particular, methodology is a bit redundant in the "guidelines" section.  I believe the incremental build model should be separate.  I concur with many of the contributors; the incremental build model is rarely utilized as a business process model. Does anyone in Software use or employ this methodology?  I am not aware of any such cases.  On the other hand, I do know of many references to the iterative approach in Technology Consulting.
A project iteration, especially in the DW business process, is not necessarily incremental development. —The preceding unsigned comment was added by 83.41.43.222 (talk • contribs) 00:37, 25 March 2006  (UTC2)
I can certainly understand the point of merging these two documents. However, as a student studying Software Engineering, I can recognize the differences. I think it would be beneficial to keep these two articles separate. I realize that there is an overlap in material, but there is also a vast amount of differences that the stub seems not to have taken account of. —The preceding unsigned comment was added by Blatyo (talk • contribs) 16:40, 6 April 2006  (UTC2)
I am also a student of Software Engineering, and we are currently doing research on building a specific model for incremental development.  It differs greatly from iterative development.  In ID, each iteration is like a mini-software lifecycle, with design, coding, and testing phases.  Incremental development involves adding features in small chuncks, where each change produces valid, working software.  The software is complete when all requirements are met.  I will add more to the Incremental Development article once research paper is completed. —Preceding unsigned comment added by 68.62.22.177 (talk • contribs) 2006-09-20T21:57:18 
----
Please sign your comments! --Bdoserror 22:15, 23 October 2006 (UTC)
thread_title:  Merge with [[Incremental build model]] 

message: Obviously the 'evil' rigid waterfall model wasn't incremental, but it was never really advocated. It seems to me that all software development models, spiral on, have been iterative whenever possible. Could someone add an example or examples of development methodologies that don't fit in this category? If there aren't any, what use does this term serve?
--Logomachist 03:40, 5 January 2007 (UTC)
replies: text: The waterfall model is apparently still used.  The distinction should probably be that other models are designed to be incremental/iterative, while the waterfall model is not designed this way, but since software is rarely 100% right first time... --Michig 19:17, 31 January 2007 (UTC)
thread_title:  What development models *aren't* iterative and incremental? 

message: The definition (the first sentence) is no definition. It only states why this topic exists and where it is used - but not what is ment by iterative and incremental development. --Sebastian Dietrich 09:23, 24 May 2007 (UTC)
thread_title:  Definition 

message: The deployment of course comes after the testing. It's not Windows or GTA we're talking about! ^^
— 88.77.140.123 (talk) 18:50, 25 September 2009 (UTC)
thread_title:  The image is ''wrong''! 

message: I did not find velocity (factor to calculate actual development time from workdays) in any software engineering topic. I think this is a very important term and should be explained somewhere (or rather, should even have its own topic). I'd be glad if someone could add this. Kind regards -- mafutrct (talk) 11:10, 11 November 2009 (UTC)
thread_title:  Velocity 

message: The image is rather a good illustration of an incremental development, and not iterative. We see increments within phases, we do not see iterations. 
It is quiet common procedure to execute more than just one iteration, in order to achieve the amount of software desired for one increment. This can not be seen here, and the first misleading impression can be, iteration and increment are the same.  — Preceding unsigned comment added by MarekLewandowski (talk • contribs) 08:20, 27 July 2011 (UTC)
thread_title:  The image of Iterative development may be misleading 

message: Another name for this development model is EVOLUTIONARY. Please, add this datum to the article.
https://dspace.mit.edu/bitstream/handle/1721.1/80490/42757317-MIT.pdF
https://www.geeksforgeeks.org/software-engineering-evolutionary-model/
George Rodney Maruri Game (talk) 06:24, 7 July 2023 (UTC)
thread_title:  Alternative name: EVOLUTIONARY 

message: That's some pretty broad statements there that have no evidence like Waterfall needing more human resources than incremental, and Waterfall being unsuitable for small projects. There are counterexamples in real life for these two and other points from this section. I'd add the evidence or delete the section. 2003:DB:4F0C:7196:9DB8:E58A:C6AB:D197 (talk) 16:38, 11 July 2023 (UTC)
thread_title:  "Contrast with Waterfall development" section is misleading