Martin, J. (1981). Application Development Without Programmers. Englewood Cliffs, NJ:
Prentice-Hall.
Massol, V. and Husted, T. (2003). JUnit in Action. Greenwich, Conn.: Manning Publications Co.
Mills, H. D., O’Neill, D., Linger, R. C., Dyer, M. and Quinnan, R. E. (1980). ‘The Management of
Software Engineering’. IBM Systems. J., 19 (4), 414–77.
Moore, E. and Spens, J. (2008). ‘Scaling Agile: Finding your Agile Tribe’. Proc. Agile 2008
Conference, Toronto: IEEE Computer Society. 121–124.
Palmer, S. R. and Felsing, J. M. (2002). A Practical Guide to Feature-Driven Development.
Englewood Cliffs, NJ: Prentice Hall.
Parrish, A., Smith, R., Hale, D. and Hale, J. (2004). ‘A Field Study of Developer Pairs: Productivity
Impacts and Implications’. IEEE Software, 21 (5), 76–9.
Poole, C. and Huisman, J. W. (2001). ‘Using Extreme Programming in a Maintenance Environment’.
IEEE Software, 18 (6), 42–50.
Rising, L. and Janoff, N. S. (2000). ‘The Scrum Software Development Process for Small Teams’.
IEEE Software, 17 (4), 26–32.
Schwaber, K. (2004). Agile Project Management with Scrum. Seattle: Microsoft Press.
Schwaber, K. and Beedle, M. (2001). Agile Software Development with Scrum. Englewood Cliffs,
NJ: Prentice Hall.
Smits, H. and Pshigoda, G. (2007). ‘Implementing Scrum in a Distributed Software Development
Organization’. Agile 2007, Washington, DC: IEEE Computer Society.
Stapleton, J. (1997). DSDM Dynamic Systems Development Method. Harlow, UK: Addison-Wesley.
Stapleton, J. (2003). DSDM: Business Focused Development, 2nd ed. Harlow, UK: Pearson
Education.
Stephens, M. and Rosenberg, D. (2003). Extreme Programming Refactored. Berkley, Calif.: Apress.
Sutherland, J., Viktorov, A., Blount, J. and Puntikov, N. (2007). ‘Distributed Scrum: Agile Project
Management with Outsourced Development Teams’. 40th Hawaii Int. Conf. on System Sciences,
Hawaii: IEEE Computer Society.
Weinberg, G. (1971). The Psychology of Computer Programming. New York: Van Nostrand.
Williams, L., Kessler, R. R., Cunningham, W. and Jeffries, R. (2000). ‘Strengthening the Case for Pair
Programming’. IEEE Software, 17 (4), 19–25.
Chapter 3 ■ References 81