Revision as of 16:42, 12 January 2017 edit 208.81.212.224 (talk) Undid revision 759626485 by 182.71.178.190 (talk) edit test? ← Previous edit		Revision as of 16:54, 5 February 2017 edit undo Rob Bednark (talk \| contribs) 93 edits m simplified wording Next edit →
Line 9: it advocates frequent "releases" in short development cycles, which is intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted. Other elements of extreme programming include: programming [[Pair programming\|in pairs]] or doing extensive [[code review]], [[unit testing]] of all code, avoiding programming of features until they are actually needed, a flat management structure, code simplicity and clarity ~~in code~~, expecting changes in the customer's requirements as time passes and the problem is better understood, and frequent communication with the customer and among programmers.<ref name="UPenn49"> "Design Patterns and Refactoring", University of Pennsylvania, 2003, webpage:

Extreme programming: Difference between revisions