Extreme programming practices: Difference between revisions

Revision as of 23:33, 15 April 2020

Revision as of 02:57, 26 September 2020

Line 136:

=== Design improvement ===

Because XP doctrine advocates programming only what is needed today, and implementing it as simply as possible, at times this may result in a system that is stuck. One of the symptoms of this is the need for dual (or multiple) maintenance: functional changes start requiring changes to multiple copies of the same (or similar) code. Another symptom is that changes in one part of the code affect lots ofmany other parts. XP doctrine says that when this occurs, the system is telling you to [[refactoring|refactor]] your code by changing the architecture, making it simpler and more generic.

=== Small releases ===