Revision as of 05:43, 2 February 2016 edit Walter Görlitz (talk \| contribs) Extended confirmed users, Pending changes reviewers 294,571 edits →Lack of release structure: another reference ← Previous edit		Revision as of 06:02, 2 February 2016 edit undo Walter Görlitz (talk \| contribs) Extended confirmed users, Pending changes reviewers 294,571 edits →Incompleteness: additional content and references Next edit →
Line 30: ===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>http://www.stickyminds.com/better-software-magazine/dont-just-break-software-make-software</ref> ==Advantages==

Cowboy coding: Difference between revisions