Index_F

F

failures

anticipating failure modes, 236 “236

fear as source of project failures, 108 “109

of large-scale XP, 328 “334

collective ownership and, 329

communal coding rooms and, 331

emergent design and, 331 “332

on-site customers and, 331

reasons for, 334

vs. small projects, 332 “333

solution, 334

story cards and oral

documentation and, 329

XP coaches and, 329 “331

of on-site customers

failure modes, 122

testing and, 131 “133

Fancellu, Dino

article on functional specifications, 238

on oral documentation, 176

fear

Beck, Kent on, 110, 114, 256

Extremo culture and, 108 “116

importance of fear, 114

satire and, 112 “114

as source of project failures, 108 “109

XPers assigning fear to others, 115 “116

failure of C3 and, 112 “114

Fear is the Mind Killer (article), 37

Hendrickson, Chet on, 110

It All Depends on the Fear (satire), 112

Jeffries, Ron on, 109

Planning Extreme Programming and, 108, 110, 111, 115

Rosenberg s parody on, 111 “112

as source of project failures, 108 “109

Feathers, Michael, 10

feedback, as XP value, 6

Fisher, Timothy, 162, 174

forty- hour week. See sustainable pace

Fowler, Martin

amount of up-front testing and, 185

documentation and, 172

on emergent design, 277

future of documentation and, 166 “167

Planning Extreme Programming , 108, 110, 111, 115

refactoring and on refactoring, 69, 209

usefulness of refactoring and, 207

Refactoring: Improving the Design of Existing Code , 69, 207

on releases, 297

on requirements creep, 294

fragility prevention, 340 “342

frameworks

frameworks design vs. business value, 279 “287

adding complexity, 281 “282

benefits emerge, 284 “285

framework design in XP, 279 “280

justifying to customers, 285 “286

services frameworks, 280

simplicity and, 280 “281, 282 “284

up-front design vs. emergent design, 286 “287

as project core , 365

server tools project and, 366 “367

frequent integration, 354, 364

functional specifications, defined, 238

functional tests, 8

fundamentals of XP. See XP