|
1.Adler, L., “Systems Approach to Marketing,” Harvard Business Review, May-June 1967, pp. 105-118. 2.Alshayeb M. and Li W., “An empirical study of system design instability metric and design evolution in an agile software process”, The Journal of System and Software, issue 74, 2005, pp. 269-274. 3.Anderson, A., Beattie, R., Beck, K. et al., “The C3 Team, Chrysler Goes to "Extremes"”. Distributed Computing. October 1998, pp.24-28. 4.Armitage J., “Are agile methods good for design? ” ACM Press, pp. 14-23, Volume 11, Issue 1 January + February 2004. 5.Beck, K. and Andres, C., Extreme Programming Explained : Embrace Change (2nd Edition), Boston, Addison-Wesley, 2005. 6.Beck, K., Extreme Programming Explained, Addison Wesley Longman, 2000. 7.Berry, D., “How Marketers Use Microcomputers - Now and in the Future,” Business Marketing, 68, December 1983, pp. 44, 48-49, 52-53. 8.Bevan, J., Werner, L., McDowell, C., “Guidelines for the Use of Pair Programming in a Freshman Programming Class,” presented at the Conference on Software Engineering Education and Training, Kentucky, 2002. 9.Bradley, J. H., Hebert, F. J., “The effect of personality type on team performance,” Journal of Management Development, 16:5, 1997, pp. 337–353. 10.Cockburn, A., Agile Software Development. Addison-Wesley, 2001. 11.Cockburn, A. and Williams, L., ”The Costs and Benefits of Pair Programming,” in Giancarlo Succi and Michele Marchesi (eds.) Extreme Programming Examined. Boston: Addison Wesley, 2001, pp. 223-243. 12.Constantine L.L., Constantine on Peopleware, Yourdon Press, Englewood Cliffs, N.J., 1995. 13.Fagan, M. E., “Advances in Software Inspections to Reduce Errors in Program Development,” IBM Systems Journal, vol. 15, 1976, pp. 182-191. 14.Faraj, S. and Sproull, L., “Coordinating expertise in software development teams.” Management Science, 46, 12 (Dec) 2000, pp. 1554-1568. 15.Frederick P. Brooks, The Mythical Man-Month: Essays on Software Engineering, 20th Anniversary Edition, Addison-Wesley, 1995. 16.Frederick P. Brooks, The Mythical Man-Month: Essays on Software Engineering, 20th Anniversary Edition, Addison-Wesley, 1995. 17.Gehringer, E.F., “A pair-programming experiment in a non-programming course.” ACM Press, pp. 187-190, 2003. 18.Gorla, N. and Lam, Y. W., “Who should work with whom?: building effective software project teams,“ Communications of the ACM, vol. 47, No. 6, June 2004, pp. 79-82. 19.Hedin, G., Bendix, L., and Magnusson, B., “Teaching extreme programming to large groups of studemts,” The Journal of Systems and Software, pp. 133-146, 74 (2005). 20.Kircher, M., Jain, P., Corsaro, A., and Levine, D., “Distributed Extreme Programming.” Proceedings of XP2001 - eXtreme Programming and Flexible Processes in Software Engineering, Villasimius, Sardinia, Italy, May 21-23, 2001. pp. 66-71. 21.Jeffries, R. et al., Extreme Programming Installed, Addison Wesley Longman, 2001. 22.Lindstrom, L., and Jeffries R., “Extreme Programming and Agile software development methodologies.” Information Systems Management, pp. 41-52, Summer 2004. 23.McDowell, C., Werner, L., Bullock, H., and Fernald, J., “The Effects of Pair Programming on Performance in an Introductory Programming Course,” Proceedings of the Thirty-Third Technical Symposium on Computer Science Education (SIGCSE 2002), ACM Press, 2002. 24.Myers, I. B., McCaulley, M. H., Quenk, N. L., & Hammer, A. L., MBTI® manual: A guide to the development and use of the Myers-Briggs Type Indicator® (3rd ed.). Palo Alto, CA: CPP, Inc., 1998. 25.Nagappan, N., Williams, L., Ferzli, M., Wiebe, E., Yang, K., Miller, C., and Balik, S., “Improving the CS1 Experience with Pair Programming,” Proceedings of the Thirty-Fourth Technical Symposium on Computer Science Education (SIGCSE 2003), ACM Press, 2003. 26.Nosek, J.T., “The Case for Collaborative Programming,” Communications of ACM, Vol. 41, No. 3, 1998, pp. 105–108. 27.Quenk, N. L., Essentials of Myers-Briggs Type Indicator® Assessment. New York: Wiley, 2000. 28.Rasch, R.H., Tosi H. L., “Factors Affecting Software Developers Performance: An Integrated Approach.” MIS Quarterly, September 1992, pp. 395-413 29.Russell, G. W., “Experience with Inspection in Ultralarge-Scale Developments,” IEEE Software, vol. 8, no. 1, 1991, pp. 25 -31. 30.Sawyer S., “Software Development Teams-Considering three software development team archetypes and their implications.” Communications of the ACM, December 2004/ Volumn47. No 12, pp. 95-99. 31.Schneider, J.G., Johnston, L., “eXtreme Programming – helpful or harmful in educating undergraduates?“ The Journal of Systems and Software, pp. 121-132, 74 (2005). 32.Thomas, L., Ratcliffe, M., and Robertson, A., “Code Warriors and Code-a-Phobes: A Study in Attitude and Pair Programming,” Proceedings of the Thirty-Fourth Technical Symposium on Computer Science Education (SIGCSE 2003), ACM Press, 2003. 33.Weinberg, G. M., The Psychology of Computer Programming Silver, Anniversary Edition. Dorset House Publishing, 1998. 34.Weller, E. F., “Lessons from Three Years of Inspection Data,” IEEE Software, vol. 10, no. 5, 1993, pp. 38-45. 35.Williams, L., Pair Programming Questionnaire, http:// limes.cs.utah.edu/questionnaire/questionnaire.htm, 1999. 36.Williams, L., Kessler, R., Pair Programming Illustrated. Boston, Massachusetts: Addison Wesley, 2003. 37.Williams, L., and Kessler, R. R., "All I Really Need to Know about Pair Programming I Learned In Kindergarten," Communications of the ACM, May 2000, pp. 20-25. 38.Williams, L., Kessler, R.R., Cunningham, W., and Jeffries, R., “Strengthening the Case for Pair Programming,” IEEE Software, July/August 2000, pp. 20-25. 39.Williams, L., Upchurch, R., “Extreme programming in software engineering education.”, Proceedings of ASEE/IEEE Frontiers in Education, Reno, Nevada, October 2001. IEEE. 40.Williams, L., Yang, K., Wiebe, E., Ferzli, M., and Miller, C., “Pair Programming in an Introductory Computer Science Course: Initial Results and Recommendations,” presented at the OOPSLA Educator’s Symposium, Seattle, Washington, 2002. 41.Zhang Y., “Test-Driven Modeling for Model-Driven Development,” IEEE Software, September/October 2004, pp. 80-86.
|