• Orit Hazzan
  • Yael Dubinsky
Part of the Undergraduate Topics in Computer Science book series (UTICS)


Leadership is the ability to influence people, encouraging them to behave in a certain way in order to achieve the group’s goalsgoals . Leadership is independent of job titles and descriptions; usually, however, in order to lead, leaders need the power derived from their organizational positions. There are different leadership stylesleadership , such as task-oriented versus people-oriented, directive versus permissive, autocratic versus democratic. While leaders can shape their leadership style according to circumstances, followers might prefer different leadership styles depending on their situation. Agile software engineering adopts a leadership style that empowers the people involved in the product development process. For example, instead of promoting the idea that “leaders should keep power to themselves in order not to lose it,” the agile approach fosters the idea that “leaders gain power from sharing it.” This idea is expressed, among other ways, by the transparency of the agile development process that makes information accessible to anyone and enables each team member to be accountable for and fully involved in the development process.


Team Member Software Development Team Leader Leadership Style Software Development Project 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. Augustine S,Augustine S Payne BPayne B, Sencindiver FSencindiver F, Woodcock SWoodcock S (2005) Agile project management: steering from the edges. Commun ACM 48(12):85–89CrossRefGoogle Scholar
  2. Beck K,Beck K Andres CAndres C C (2004) Extreme programming explained: embrace change, 2nd ed. Addison-Wesley, Reading, MAGoogle Scholar
  3. Bruce A,Bruce A Langdon KLangdon K (2000) Project management. Dorling Kindersley, New YorkGoogle Scholar
  4. Ciulla JBCiulla JB (1998) Ethics: the heart of leadership. Praeger, Westport, ConnecticutGoogle Scholar
  5. Cockburn A,Cockburn A Highsmith JHighsmith J (2001) Agile software development: the people factor. IEEE Software 34(11):131–133Google Scholar
  6. Cooper CLCooper CL (2005) Leadership and management in the 21st century: business challenges of the future. Oxford University Press, New YorkGoogle Scholar
  7. Drath WHDrath WH (1998) Approaching the future of leadership development. In: McCauley CD, Moxley RS, Van Velsor E (eds) The center for creative leadership: handbook of leadership development. San Francisco, CA, Jossey-Bass, pp 403–432Google Scholar
  8. Dubinsky Y, Hazzan O (2003) eXtreme programming as a framework for student-project coaching in computer science capstone courses. Proceedings of the IEEE international conference on software—science, technology & engineering. Herzelia, Israel, pp 53–59Google Scholar
  9. Dubinsky Y, Hazzan O (2006) Using a role scheme to derive software project quality. J Syst Architect 52(11):693–699CrossRefGoogle Scholar
  10. Goleman DGoleman D (1998) What makes a leader? Harvard Bus Rev 76(6):93Google Scholar
  11. Hazzan O, Dubinsky Y (2005) cognitive and social perspectives of software development methods: the case of extreme programming. Proceedings of the 6th international conference on extreme programming and agile processes in software engineering, pp 74–81Google Scholar
  12. Huff AS,Huff AS Moeslein KMoeslein K (2005) An agenda for understanding individual leadership in corporate leadership systems. In: Cooper CL (ed) Leadership and management in the 21st century: business challenges of the future. Oxford University Press, New York, pp 248–270Google Scholar
  13. Hughes B,Hughes B Cotterell MCotterell M (2002) Software project management, 3rd edition. McGraw-Hill, New YorkGoogle Scholar
  14. Humphrey WSHumphrey WS (2000) Introduction to the team software process. Addison-Wesley, Reading, MAGoogle Scholar
  15. Mayrhauser VAMayrhauser VA (1990) Software engineering methods and management. Academic Press, New YorkzbMATHGoogle Scholar
  16. Nirenberg JNirenberg J (2002) Global leadership. Capstone Wiley, New YorkGoogle Scholar
  17. Pulford K,Pulford K Combelles KA,Combelles KA Shirlaw SShirlaw S (1996) A quantitative approach to software management—the ami handbook. Addison-Wesley, Reading, MAGoogle Scholar
  18. Putnam LH,Putnam LH Myers WMyers W (1997) Industrial strength software—effective management using measurement. IEEE Computer Society Press, Silver Spring, MDGoogle Scholar
  19. Sommerville ISommerville I (2001) Software engineering, 6th ed. Addison-Wesley, Reading, MAGoogle Scholar
  20. Topping PATopping PA (2002) Managerial leadership. McGraw-Hill, New YorkGoogle Scholar

Copyright information

© Springer-Verlag London 2008

Authors and Affiliations

  • Orit Hazzan
    • 1
  • Yael Dubinsky
    • 2
  1. 1.Department of Education in Technology and Science TechnionIsrael Institute of TechnologyHaifaIsrael
  2. 2.Department of Computer Science TechnionIsrael Institute of TechnologyHaifaIsrael

Personalised recommendations