KeywordsAssure Straw Prep Metaphor Folk
Unable to display preview. Download preview PDF.
- 1.Alistair Cockburn, Agile Software Development ( New York, NY: Addison-Wesley, 2001 ), p. 169.Google Scholar
- 2.Amr Elssamadisy, “XP On A Large Project—A Developer’s View,” http://www.xpuniverse.com/2001/pdfs/EP202.pdf paper presented at the 2001 XP Universe conference.
- 3.Ibid. We analyze the paper containing this quote and the last in the “Painting Over the Cracks” section in this chapter.Google Scholar
- 4.As we explored in Chapter 5, this has proved to be the case generally in XPGoogle Scholar
- 5.See the section “Extreme Programming in Theory” in Chapter 1 for a brief description of pair rotation. Also see Chapter 6.Google Scholar
- 6.Presentations are useful to bring the design to life and communicate it effectively to developers. Writing the design down (and keeping it up-to-date) can also save a lot of wasted work and misunderstanding.Google Scholar
- 7.Amr Elssamadisy, op. cit., p. 5.Google Scholar
- 10.At least, it’s vital in XP because the practices are taken to extremes.Google Scholar
- 11.Amr Elssamadisy, op. cit., p. 4.Google Scholar
- 14.The XP mantras “you aren’t gonna need it,” “Do The Simplest Thing That Could Possibly Work,” and “[Don’t do a] Big Design Up Front” are all described variously throughout this book.Google Scholar
- 15.The first 90% is always easy. Fear might be the mind-killer, but it’s that second 90% that is always the killer on software projects. To (mis)quote Marvin the Paranoid Android from Douglas Adams’ The Restaurant at the End of the Universe “The first 90% was the worst. The second 90%, that was the worst too. After that we went into a bit of a decline….”Google Scholar
- 16.Kent Beck posting to OTUG (http://www.rational.com), subject: “XP and the real world,” March 1, 1999.
- 17.Pete McBreen, Questioning Extreme Programming ( New York, NY: Addison-Wesley, 2002 ), p. 87.Google Scholar
- 19.One of Doug’s favorite mental images is to imagine emergent architecture on something like a really big jet-fighter project. Developed over a decade or so by multiple companies, with multiple teams participating within each company, all geographically distributed, building real-time embedded software that has to respond in the millisecond/microsecond time frame or people die—really quickly.Google Scholar
© Matt Stephens and Doug Rosenberg 2003