Index_C

C

C2 Wiki. See Wiki (C2 Wiki site)

C3

effect of oral documentation on, 165

fear, and failure of, 112 “114

on-site customers and, 125 “126

overview, 33 “34

problems with, 53 “56

project life cycle, 34 “53

cancellation, 41 “44

DTSTTCPW, 37

hype and fanfare, 35 “36

illusion of success, 38 “39

introduction to, 34 “35

newsgroup s confusion, 46 “50

refactoring and, 40 “41

success claimed, 44 “46

unimportance claimed, 50 “53

Camden, Rich

Pair Programming Social Dynamics (VoXP), 140 “143, 158

XP from the Trenches (VoXP), 24

Camp Regretestskiy ( satire ), 194 “197

The Case Against Extreme Programming (article), 106, 109, 314, 350

case studies

ATLAS project, 314 “322

emergent design on, 320 “321

problems with, 315 “320

summary of, 321 “322

IEEE Software magazine software project, 252, 253

server tools project, 362 “368

framework, 366 “367

multiple masters, 367 “368

overview, 362 “363

sufficiency of XP and, 363 “366

change. See XP and change

Changes (song), 310

Chrysler Comprehensive Compensation Web site, 34, 40

Chrysler Knows It Ain t Easy (song), 31 “32

class structure and design, 281 “282, 283

coaches. See XP coaches

Cockburn, Alistair

Agile Software Development , 6, 79, 118, 368

on C3 project, 42, 45

on customers vs. programmers, 118

on failure of practices, 58

on feedback, 6

on pair programming, 146 “147

on scalability, 313

on software processes, 79

tailoring methodologies and, 368

on user stories, 236

code. See also perpetual coding

code hot spots, 208

code smell , defined, 204

coding as XP activity, 16

collective ownership of, 72 “75

communal coding rooms, 331

design and

ATLAS project problems and, 318

code as design, 168 “169, 212 “213

production code, defined, 13

refactoring and

design vs. refactoring, 202 “205

refactoring live code, 219

shielding from change, 223 “224

simplicity of code, 224

reviewing, 352

throwing away, 326

Code Hound (song), 99 “100

Code Together (song), 227

Coder s Little Helper (song), 147

coding standards

ATLAS project problems and, 317

collaborative, used to tame XP, 356 “357

extreme programming in theory and, 15 “16

collective ownership

ATLAS project problems and, 317

dangers of XP and, 72 “75

Elssamadisy, Amr on, 319

extreme programming in theory and, 13

failure of XP on large scale and, 329

vs. individual ownership, 72, 73 “75

Collective Ownership, Oral Documentation, and Scalability: The Perfect Storm (article), 360

Collins-Cope, Mark, 288 “289

colocated teams , 351

communication, as XP value, 6

contingency

defined, 341

vs. embellishment , 342 “343

encouraging, 339 “340

prevention of fragility and, 341

continuous integration

Camden, Rich on, 24

combined with test-first design, 354 “355

extreme programming in theory and, 15

frequent integration and, 354, 364

tweaked to tame XP, 354 “355

contracts. See optional-scope contracts

Cooper, Alan

About Face 2.0 , 297

on code as design, 213

The Inmates Are Running the Asylum, 297, 359

interaction design and, 297 “298

interaction designers and, 359

cost of change curve

and controversy over XP, 5

cost of fixing defects, 295 “297

dangers of XP and, 75 “76

Software Engineering Economics on, 296

courage, as XP value, 6

Cray, Seymour, 6

Cunningham, Ward, 103

Customer Involvement in Extreme Programming (report) burden on customers and, 118 “119

C3 failure and, 125

customer teams and, 128 “129

The Customer s a Beast of Burden (song), 120 “121

customers in XP. See also on-site customers

Cockburn on customers vs. programmers, 118

described, 10

design decisions and, 279 “280, 285

showing early prototypes to, 291

Cutter Consortium newsletter, 42 “43