Jump to content

Talk:Agile software development/Archive 2

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by MiszaBot I (talk | contribs) at 00:41, 16 July 2012 (Robot: Archiving 1 thread from Talk:Agile software development.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
Archive 1Archive 2Archive 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)