Clashes between culture and software development methods: The case of the Israeli hi-tech industry and extreme programming

Proceedings - AGILE Confernce 2005

Volumn 2005, Issue , 2005, Pages 59-69

  Hazzan, Orit ^a   Dubinsky, Yael ^a  

^a TECHNION ISRAEL INSTITUTE OF TECHNOLOGY   (Israel)

Author keywords

[No Author keywords available]

Indexed keywords

EXTREME PROGRAMMING (XP); SOFTWARE DEVELOPMENT METHODS (SDM);

COMPUTER SYSTEMS PROGRAMMING; DATA STRUCTURES; LOGIC PROGRAMMING; MANUFACTURING DATA PROCESSING; REQUIREMENTS ENGINEERING;

SOFTWARE ENGINEERING;

EID: 33847724791     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ADC.2005.17     Document Type: Conference Paper

References (18)

1. Abrahamsson, P., Salo, O., Ronkainen, S. and Warsta, J. (2002). Agile Software Development Methods, Review and Analysis, ESPOO 2002, http://www.inf.vtt.fi/pdf/publications/2002/P478.pdf
2. Auer, K and Miller, R. (2001 A). Extreme Programming: Taming the Resistance, Addison-Wesley.
3. Auer, K. and Miller, R. (2001B). Extreme Programming Applied: Playing to Win, Addison-Wesley.
4. Beck, K. (2000). Extreme Programming Explained: Embrace Change, Addison-Wesley, 2000.
5. Beck, K. (with Andres, C., 2005, second edition). Extreme Programming Explained: Embrace Change. Addison-Wesley.
6. Brooks, F. P. (April 1987). No silver bullet: Essence and accidents of software engineering, Computer 20(4), pp. 10-19.
7. Hazzan O. (2002). The reflective practitioner perspective in Software Engineering education, The Journal of Systems and Software 63(3), pp. 161-171.
8. Hazzan, O. and Dubinsky, Y. (2003). Bridging cognitive and social chasms in software development using Extreme Programming, Proceedings of the Fourth International Conference on extreme Programming and Agile Processes in Software Engineering, pp. 47-53.
9. Highsmith, J. (2002). Agile Software developments Ecosystems, Addison-Wesley.
10. Kuhn, S. (1998). The software design studio: An exploration, IEEE software 15(2), pp. 65-71.
11. Kuhn, S. T. (1962). The Structure of Scientific Revolutions, University of Chicago Press.
12. Moore, G. A. (2000). Living on the Fault Line: Managing for Shareholder Value in the Age of the Internet. New York: HarperBusiness, 2000.
13. Mullet, D. (July, 1999). The Software Crisis, Benchmarks Online - a monthly publication of Academic Computing Services 2(7).
14. Sawyer S. and Guinan, P.J. (1998). Software development: Processes and performance, IBM Systems Journal 37(4), http://www.research. ibm.com/journal/sj/374/sawyer.html
15. Tomayko J. E. (1996). Carnegie-Mellon's software development Studio: A five-year retrospective, SEI Conf. on Software Engineering Education.
16. Tomayko, J. and Hazzan, O. (2004). Human Aspects of Software Engineering, Charles River Media.
17. Walenta, T. (2004). Managing cross-cultural issues inbglobal software outsouircing, Communications of the ACM47(4), pp. 62-66.
18. Yourdon, E. (1997). Death March: The complete software developer's guide to surviving "mission impossible"projects, N.J.: Prentice Hall PTR.