Revision as of 05:52, 11 November 2017 edit 202.167.250.43 (talk) →Disadvantages ← Previous edit		Revision as of 05:53, 11 November 2017 edit undo Walter Görlitz (talk \| contribs) Extended confirmed users, Pending changes reviewers 294,571 edits Reverted good faith edits by 202.167.250.43: Please keep the talk page a place to discuss the article, not the concept being discussed. Also, new comments go at the bottom. (TW) Next edit →
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 the verification of quality (e.g. isolated testing / [[unit testing]]) there is likely to be an increased number of defects in the software.~~ ==Advantages==

Cowboy coding: Difference between revisions