Chapter 23. 20–80 Rule
The full value of XP will not come until all the practices are in place. Many of the practices can be adopted piecemeal, but their effects will be multiplied when they are in place together.
Software programmers are used to dealing with the 20–80 rule—80% of the benefit comes from 20% of the work. XP makes use of this rule itself—put the most valuable 20% of functionality into production, do the most valuable 20% of the design, rely on the 20–80 rule to defer optimization.
For the 20–80 rule to apply, the system in question must have controls that are relatively independent of each other. For example, when I tune the performance of a program, each possible place I could tune generally has little effect on the other places ...
Get Extreme Programming Explained now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
