Extreme Programming Refactored: The Case Against XP
E
early prototyping, vs. emergent design, 289 “291
The Economist Technology Quarterly, 32, 46
Eight Builds a Week (song), 57
Elssamadisy, Amr
on collective ownership, 319
on metaphors, 318
on pair programming, 319
on scalability, 313
on unit testing, 320
embellishment
vs. contingency, 342 “343
defined, 341
Embracing Change with Extreme Programming (article), 296
emergent architecture. See emergent design
emergent design, 269 “292
Arizona Daily Star on, 257
building infrastructure with, 277 “289. See also frameworks, design vs. business value
introduction to, 277 “278
poor architecture and XP, 278 “279
described, 12
vs. early prototyping, 289 “291
emergent entropy, defined, 295
example of, 324 “326
interdependence of practices and, 62
introduction to, 269 “274
emergent design basics, 270
The XP Society s Annual Picnic ( satire ), 271 “274
large XP projects and, 320 “321, 324 “326
negative aspects of
dangers of, 77
failure of XP on large scale and, 320 “321, 331 “332
illusion of progress and, 325
problems with, 290
positive aspects of, 291 “292
summary of, 291 “292
vs. up-front design, 286 “287, 287 “289
YAGNI, 274 “276
emergent entropy, defined, 295
emotions vs. logic, and XP problems, 78 “80
Estimation and Short Time Frames (VoXP), 258 “260
ethereal wizardry
in action, 372 “373
appropriate uses of XP and, 381 “382
bad advice as, 374 “375
complexity of evaluating XP and, 379 “381
more about, 373 “374
Packaged Dogma (VoXP), 376 “379
evolutionary design, defined, 166
evolutionary development, 19 “20
exploration, defined, 20
eXtreme Building (XB) (satire), 288 “289
extreme programming. See also XP
in practice, 23 “28
activities and, 27
introduction to, 23
knocking down and rebuilding, 26
refactoring and, 27 “28
values and, 26
XP from the Trenches (VoXP), 24 “25
theory, 4 “21
activities, 16 “18
central premise of XP, 5
coding standards, 15 “16
collective ownership, 13
continuous integration, 15
emergent design, 12
life cycle, 19 “21
pair programming, 13 “15
planning game, 9
practices outlined, 7 “8
refactoring, 12 “13
roles, 18 “19
simple design, 12
small releases, 11
sustainable pace, 15
system metaphor, 11 “12
test-driven development, 8
values, 5 “7
whole team, 10
Extreme Programming Explained: Embrace Change (Addison-Wesley, 2000). See also Beck, Kent
activities of software development and, 16
book review Web site, 101
customers and acceptance tests and, 131
embracing change and, 295
extremes of XP and, 377 “378
fixed-scope contracts and, 261
going home clean and, 60
on-side customer problems and, 124
pair programming and, 14, 15
productivity of pair programming and, 147
refactoring with an installed user base and, 218, 219
roles in XP and, 19
roles of XP, 18
small releases and, 11
teams and, 10
timing of publication, 93
YAGNI and, 276
Extreme Programming in Practice (Addison-Wesley, 2001), 20
Extreme Programming Installed (Addison-Wesley, 2000). See also Jeffries, Ron
changing requirements and, 49
customers and acceptance tests and, 130 “131
design and, 18
ethereal wizardry in action and, 373
frameworks and, 277
refactoring and, 40
symbiosis of XP and, 58
eXtreme Road Building (VoXP), 257
Extremo culture, 85 “116
acronyms and, 103 “104
C2 Wiki site and, 103
criticizers of XP and, 104 “108
introduction to, 104 “106
This Extremo Inquisition (satire), 107 “108
fear and, 108 “116
assigning fear to others, 115 “116
Extremos and, 109, 110 “112
importance of fear, 114
satire and, 112 “114
as source of project failures, 108 “109
hacking and XP and, 86 “88
mixed-case hyperlinks and, 103
summary of, 116
XP and the dot-com boom and, 92 “94
XP as a people process, 94 “101
agile methods , 94 “96
blaming programmers or XP, 96 “97
extremes of, 98
Marxist philosophy and, 100 “101
snack food and, 99 “100
XP goes mainstream, 88 “92
design and XPers, 89 “90
documentation and XPers, 91
introduction to, 88 “89
XP in the mainstream, 91 “92
XP terminology, 101 “102
The Extremo Inquisition, Round 2 (satire), 126 “127
The Extremo Inquisition (This May Sound Familiar) (satire), 107 “108