Extreme Programming Refactored: The Case Against XP
M
maintenance
requirements, and timing of maintenance mode, 310
XP and timing of, 219 “220, 295
Manifesto for Agile Software Development, 251
Martin, Robert C.. See also Extreme Programming in Practice (Addison-Wesley, 2001) on acceptance testing, 184, 228
C3 cancellation and, 46 “47, 51, 53
on customer s problems, 117
documentation
on oral documentation, 161, 170
on requirements documentation, 184
value of and, 172
on emergent design, 289
Extreme Programming in Practice , 20
on pair programming, 14, 136
requirements and
on requirements creep, 294
on requirements documentation, 184
on software schedules, 249 “250, 261
on user stories, 231
on XP s efficacy, 243
Marx, Karl
on collectivism, 72, 73
Marxist-Leninist approach to programming, 100 “101
XP as a people process and, 100 “101
McBreen, Pete. See Questioning Extreme Programming (Addison-Wesley, 2002) McConnell, Steve
code hot spots, 208
Rapid Development: Taming Wild Software Schedules , 208
metaphor
ATLAS project problems and, 318
large projects and, 318
system metaphor, 11 “12
tweaked to tame XP, 348
mixed-case hyperlinks , 103
modular design, 68
multithreading testing, 188 “189
The Mythical Man-Month, 78