Talk:Agile software development/Archive 2
 | This is an archive of past discussions about Agile software development. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
| Archive 1 | Archive 2 | Archive 3 |
Testing in agile and waterfall
Nothing, in any development methodolgy, advocates testing after development. Developers are supposed to always test their work. About the only thing that agile does is make it obvious who is not testing their code earlier. Also, I know people like to think there is only agile and waterfall, but there are many other methods. http://en.wikipedia.org/wiki/Software_development_methodology All should be considered for every project as they each have unique attributes that solve problems in ways that fit the problem. — Preceding unsigned comment added by 76.97.227.185 (talk) 03:59, 16 May 2012 (UTC)
Mattford63 (talk) 16:04, 22 March 2012 (UTC)
This looks incorrect.
Simplicity- The art of maximizing the amount of work not done - is essential — Preceding unsigned comment added by 64.129.150.234 (talk) 20:22, 25 September 2012 (UTC)
Neutrality
This article reads very much like a sales pitch and has very little in the way of tangible information. 195.46.249.229 (talk) 08:18, 27 February 2013 (UTC)
- Can you be more specific? Can you specify what information is missing? Can you suggest sources for this information? Can you give examples of statements that are promotional in nature? --Boson (talk) 09:08, 27 February 2013 (UTC)