雙人編程環境下人格特質與編程績效關係之研究

The Relationship between Personality Trait and Programming Performance under Pair: Programming Environment

10.6382/JIM.200907.0143

李有仁(Eldon Y. Li)；鄭江宇(C.Y. John Cheng)；嚴秀茹(H. J. Rebecca Yen)；林旭峰(Hsu Feng Lin)

人格特質 ； 雙人編程 ； 編程績效 ； Agile approach ； personality ； pair programming ； project managers

資訊管理學報

16卷3期（2009 / 07 / 01）

143 - 170

繁體中文

近年來敏捷軟體開發流程發展迅速，其中以雙人編程之協同概念最受到重視。然而到目前為止我們對於「什麼樣的人格特質組合得以提升編程績效」之議題仍缺乏相關了解，特別是在中小型軟體產業上。有鑑於此，本研究以人格特質量表(MBTI)、搭配不同之工作形態，試圖透過實驗設計方式來找出最佳配對組合。研究結果顯示：(1)專案經理必須了解，不同特質的雙人組合其編程績效比相同特質組合來得佳。(2)外部工作內容宜指派給具有外向特質的編程人員，而內部工作內容則適用於具有內向特質的編程人員。(3)感知式思考之編程人員較適合處理複雜度較低的工作，而複雜度高的工作則適合指派給直覺式思考之編程人員。

The growth of agile approaches has attracted considerable attention to collaborative programming. However, it is not clear what specific pairs of personality traits could be suitable for increasing performance in collaborative programming. To understand this better, we conduct an experiment with the dimensions of personality and task type. The results suggest: (1) Project managers should be aware that complementary composition of personality types tends to outperform the composition single personality type. (2) Tasks involving external interfaces are better assigned to extrovert programmers. Conversely, tasks concerning the internal logic of a system are better assigned to introverts. (3) For 'sensing' programmers, low-complexity tasks form the best choice. Conversely, high-complexity tasks are more suitable for 'intuitive' persons.

1. Beck, K.(1999).Embrace Change with Extreme Programming.IEEE Computer,32(10),70-77.
2. Bevan, J.,Werner, L.,McDowell, C.(2002).Guidelines for the User of Pair Programming in a Freshman Programming Class.Conference on Software Engineering Education and Training
3. Bradley, J.H.,Hebert, F.J.(1997).The Effect of Personality Type on Team Performance.Journal of Management Development,16(5),337-353.
4. Cockburn, A.,Williams, L.,Giancarlo Succi (eds.),Michele Marchesi (eds.)(2001).Extreme Programming Examined.Boston:Addison Wesley.
5. Constantine L.L.(1995).Constantine on Peopleware.Englewood Cliffs, N. J.:Yourdon Press.
6. Coplien, J.O.A,J.O. Coplien (Eds.),D.C. Schmidt (Eds.)(1995).Pattern Language of Program Design.Massachusetts, USA:Addison Wesley.
7. DeMarco, T.,Lister, T.(1999).Peopleware: Productive Projects and Teams.New York:Dorset House.
8. Gallis, H.,Arisholm, E.,Dyba, T.(2002).A Transition from Partner Programming to Pair Programming: an Industrial Case Study.17th Annual ACM Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA)
9. Gehringer, E.F.(2003).A Pair-Programming Experiment in a Non-Programming Course.ACM Press.
10. Gorla, N.,Lam, Y.W.(2004).Who Should Work with Whom?: Building Effective Software Project Teams.Communications of the ACM,47(6),78-82.
11. Guinan, P.J.,Cooprider, J.G.,Faraj, S.(1998).Enabling Software Development Team Performance during Requirements. Definition: a Behavioral versus Technical Approach.Information Systems Research,9(2),101-125.
12. Hair, J.F.,Black, B.,Babin, B.,Anderson, R.E.,Tatham, R.L.(2006).Multivariate Data Analysis.Prentice Hall.
13. Hedin, G.,Bendix, L.,Magnusson, B.(2005).Teaching Extreme Programming to Large Groups of Students.The Journal of Systems and Software,74(2),133-146.
14. Hohmann, L.(1997).Journey of the Software Professional: A Sociology of Software Development.New Jersey, USA:Prentice-Hall.
15. Howard, A.(2001).Software Engineering Project Management.Communications of the ACM,44(5),23-24.
16. Jeffery, D.R.,Votta, L.G.(1999).Guest Editor's Special Section Introduction.IEEE Transactions on Software Engineering,25(4),433-437.
17. Jeffries, R.E.,Anderson, A.,Hendricson, C.(2000).Extreme Programming Installed.Addison Wesley Longman.
18. Kircher, M.,Jain, P.,Corsaro, A.,Levine, D.(2001).in Proceedings of XP2001-eXtreme Programming and Flexible Processes in Software Engineering.Villasimius, Sardinia, Italy:
19. McCabe, T.(1996).Cyclomatic Complexity and the Year 2000.IEEE Software,13(3),115-117.
20. McDowell, C.,Werner, L.,Bullock, H. E.,Fernald, J.(2002).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)
21. McDowell, C.,Werner, L.,Bullock, H.E.,Fernald, J.(2006).Pair Programming Improves Retention, Confidence, and Program Quality.Communication of the ACM,49(8),90-95.
22. Molokken, K.,Jorgensen, M.(2003).Software Effort Estimation: Unstructured Group Discussion as a Method to Reduce Individual Bias.Proceedings of 15th Annual Workshop of the Psychology of Programming Interest Group
23. Myers, I. B.,McCaulley, M. H.,Quenk, N. L.,Hammer, A. L.(1998).MBTI® Manual: A Guide to the Development and Use of the Myers-Briggs Type Indicator®.Palo Alto, CA:CPP, Inc..
24. Nagappan, N.,Williams, L.,Ferzli, M.,Wiebe, E.,Yang, K.,Miller, C.,Balik, S.(2003).Improving the CS1 Experience with Pair Programming.Proceedings of the Thirty-Fourth Technical Symposium on Computer Science Education (SIGCSE 2003)
25. Nosek, J.T.(1998).The Case for Collaborative Programming.Communications of ACM,41(3),105-108.
26. Olson, J.,Teasley, S.,Covi, L.,Olson, G.,Hinds, P. (Eds.),Kiesler, S. (Eds.)(2002).Distributed Work.Cambridge, MA:MIT Press.
27. Payne, J.W.(1976).Task Complexity and Contingent Processing in Decision Making: an Information Search and Protocol Analysis.Organizational Behavior and Human Performance,16(2),366-387.
28. Rasch, R.H.,Tosi, H.L.(1992).Factors Affecting Software Developers Performance: An Integrated Approach.MIS Quarterly,16(3),395-413.
29. Schneider, J.G.,Johnston, L.(2005).eXtreme Programming-Helpful or Harmful in Educating Undergraduates?.The Journal of Systems and Software,74(2),121-132.
30. Sheth, J.N.,Sisodia, R.S.(2002).Marketing Productivity: Issues and Analysis.Journal of Business Research,55(5),349-362.
31. Sjoberg, D.I.K.,Anda, B.,Arisholm, T.,Dyba, M.,Jorgensen, A.,Karahasanovic, E.F.,Koren, E.F.,Vokac, M.(2002).Conducting Realistic Experiment in Software Engineering.Proceedings of International Symposium on Empirical Software Engineering (ISESE' 02)
32. Teasley, S.D.,Covi, L.A.,Krishnan, M.S.,Olson, J.S.(2002).Rapid Software Development through Team Collocation.IEEE Transactions on Software Engineering,28(7),671-683.
33. Thomas, L.,Ratcliffe, M.,Robertson.(2003).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)
34. Williams, L.,Kessler, R.R.(2003).Pair Programming Illustrated.Boston, Massachusetts:Addison Wesley.
35. Williams, L.,Kessler, R.R.(2000).All I Really Need to Know about Pair Programming I Learned in Kindergarten.Communications of the ACM,43(5),20-25.
36. Williams, L.,Kessler, R.R.,Cunningham, W.,Jeffries, R.(2000).Strengthening the Case for Pair Programming.IEEE Software,17(4),20-25.
37. Williams, L.,Upchurch, R.(2001).Extreme Programming in Software Engineering Education.Proceedings of ASEE/IEEE Frontiers in Education.
38. Yellen, R.E.,Winniford, M.A.,Sanford, C.C.(1995).Extroversion and Introversion in Electronically Supported Meetings.Information & Management,28(1),63-74.
39. Zhang, Y.(2004).Test-Driven Modeling for Model-Driven Development.IEEE Software,20(5),80-86.
40. Zikmund, W.G.(2002).Business Research Method.Ohio, USA:Thomson South-Western.
41. 台灣軟體產業現況與發展