Content deleted Content added
TwoTwoHello (talk | contribs) m Reverted edits by 131.228.32.167 (talk) to last version by 46.17.166.68 |
|||
Line 29:
===Incompleteness===
Many software development models, such as [[Extreme Programming]], use an incremental approach which stresses that the software must be releasable at the end of each iteration. Non-managed projects may have few [[unit testing|unit tests]] or working iterations, leaving an incomplete project unusable. As such, agile methodologies have been compared to cowboy coding but agile has formal processes, procedures, measurement, project management and other oversight while cowboy coding has none of this.<ref>{{cite web| url=http://www.stickyminds.com/sites/default/files/article/file/2013/XUS22546409file1_0.doc |title=Exploring Agile Development | work=Pragmatic Software Newsletter |issue=March 2007}}</ref><ref>{{cite web|url=http://www.stickyminds.com/better-software-magazine/dont-just-break-software-make-software|title=StickyMinds - Don't Just Break Software. Make Software|work=StickyMinds|accessdate=February 2, 2016}}</ref>
===Inconsistent quality===
Adhering to no agreed practices for testing quality (e.g. isolated testing) there is likely to be an increased number of defects in the software.
==Advantages==
| |||