Software is an intangible productsoftware . Therefore, it is difficult to understand its development process using our regular senses; the exact status of the development process is not always clear; misunderstandings may emerge. Consequently, it is sometimes difficult to establish trustful professional relationships, and team members may tend not to trust each other. This chapter focuses on how agile software development fosters trust among team members. We first explain how agile software development makes the development process more transparent and thus makes the process and the developed product more understandable. Then, using the “prisoner’s dilemma”prisoner's dilemma framework taken from game theorygame theory , we explain why and how a transparent process does indeed foster trust among team members. Based on this working assumption, i.e., that the transparent nature of agile software development fosters trust among team members, we focus on how agile software development enhances ethicalethics behavior and diversitydiversity in a way that improves process and product quality.
- Beck KBeck K, Andres CAndres C (2005) Extreme programming explained, 2nd ed. Addison Wesley, Reading, MAGoogle Scholar
- Florida RFlorida R (2002) The rise of the creative class. Basic BooksGoogle Scholar
- Hazzan O (2007) Agile software development and the nature of software development. Featured Frontier Columnist. System Design Frontier 4(3):28–32Google Scholar
- Hazzan O, Dubinsky Y (2005) Social perspective of software development methods: the case of the prisoner dilemma and extreme programming. Proceedings of the sixth international conference on extreme programming and agile processes in software engineering. Sheffield University, UK, pp 74–81CrossRefGoogle Scholar
- Smith MKSmith MK (2001, 2007) Robert Putnam: the encyclopedia of informal education. www.infed.org/thinkers/putnam.htm. Last update: November 05, 2007
- Thomas DThomas D (2004) Diversity as strategy. Harvard Bus Rev 98–108 (http://www.gpworldwide.com/quick/sep2004/art2.asp)