Beck, Kent. See also Extreme Programming Explained: Embrace Change (Addison-Wesley, 2000)
on activities, 16
C3 project and
exaggeration of success, 45
on importance of C3 project, 50
as part of, 36, 39, 46
scope creep and, 48
collective ownership and, 100 “101
on cost of changes curve, 296
customers and
error of single on-site customers and, 127
on on-side customer problems, 124
on deadlines, 257
design and on emergent design, 270, 278, 331
on up-front design, 187
Embracing Change with Extreme Programming (article), 296
Extreme Programming Explained as manifesto, 100
on fear, 110, 114, 256
on going home clean , 60
on interdependence of practices, 57, 61
optional scope contracts and, 263
Planning Extreme Programming , 108, 110, 111, 115
on the premise of XP, 5
on refactoring, 209, 218, 219
Refactoring: Improving the Design of Existing Code , 69, 207
on refactoring with an installed user base, 219
on releases, 254, 297
on requirements creep, 294, 303
roles in XP and, 19
on scalability, 328
on social changes with XP, 118
on TDD insufficiencies, 188
on teams , 10
Test-Driven Development:By Example (Addison-Wesley, 2002), 188
XP mystique and, 372
on YAGNI, 274, 276
on Zen and XP, 374 “375