Belbin's Company Worker, The Self-Perception Inventory, and Their Application to Software Engineering Teams

Software engineering often requires a team arrangement because of the size and scope of modern projects. Several team structures have been defined and used, but these structures generally define only the tasks and jobs required for the team. Various process and product metrics seek to improve quality, even though it is generally agreed that the greatest potential benefit lies in people issues. This study uses a team-based personality profiling tool, the Belbin Self-Perception Inventory, to explore the characteristics offered by the Company Worker, one of the team roles defined by Belbin.

[1]  Steve Blinkhorn,et al.  Spuriouser and spuriouser: The use of ipsative personality tests , 1988 .

[2]  Gerald M. Weinberg,et al.  Psychology of computer programming , 1971 .

[3]  Maurice H. Halstead,et al.  Elements of software science (Operating and programming systems series) , 1977 .

[4]  R. Cattell,et al.  Handbook for the sixteen personality factor questionnaire (16 PF) , 1970 .

[5]  T. Capers Jones,et al.  Estimating software costs , 1998 .

[6]  Ruth C. Carter,et al.  Principles , 2003, Law’s Reality.

[7]  T W Kent,et al.  Team building. , 1974, Dental clinics of North America.

[8]  J. A. Salvato.  John wiley & sons. , 1994, Environmental science & technology.

[9]  Capers Jones,et al.  Programming Productivity , 1986 .

[10]  Lowell Jay Arthur,et al.  Improving Software Quality: An Insider's Guide to TQM , 1992 .

[11]  Denis Johnson.  In Palo Alto , 1982 .

[12]  Robert L. Glass,et al.  Software Conflict: Essays on the Art and Science of Software Engineering , 1990 .

[13]  Barry Boehm,et al.  Characteristics of software quality , 1978 .

[14]  Anita D. Carleton,et al.  Case studies of software-process-improvement measurement , 1994, Computer.

[15]  Michael Lyons.  The DP psyche , 1985 .

[16]  A. Mcguire,et al.  What is it to be a model? , 2000, HEPAC Health Economics in Prevention and Care.

[17]  K. Bradway,et al.  Jung's Psychological Types , 1964 .

[18]  Francis M. Sim,et al.  Role Theory: Expectations, Identities, and Behaviors. , 1982 .

[19]  Verzekeren Naar Sparen,et al.  Cambridge , 1969, Humphrey Burton: In My Own Time.

[20]  P ? ? ? ? ? ? ? % ? ? ? ? , 1991 .

[21]  Watts S. Humphrey,et al.  A discipline for software engineering , 2012, Series in software engineering.

[22]  IEEE Transactions on Software Engineering, Vol. 28 , 2002 .

[23]  Mark C. Paulk,et al.  Capability Maturity Model , 1991 .

[24]  L. Williams.  The Collaborative Software Process , 1999 .

[25]  P. Goodman.  Groups That Work (and Those That Don't)Groups That Work (and Those That Don't) by Hackman Richard. San Francisco: Jossey-Bass, 1991, 512 pp. , 1992 .

[26]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.

[27]  J. Susan Milton,et al.  Introduction to Probability and Statistics: Principles and Applications for Engineering and the Computing Sciences , 1990 .

[28]  Sallie M. Henry,et al.  Using Belbin's leadership role to improve team effectiveness: An empirical investigation , 1999, J. Syst. Softw..

[29]  Kouichi Kishida,et al.  Non-Technological Issues in Software Engineering Panel Chair: , 1991 .

[30]  Shirley Dex,et al.  JR 旅客販売総合システム（マルス）における運用及び管理について , 1991 .

[31]  吴德恒,et al.  经Co , 1964 .

[32]  Ken Auer,et al.  Extreme Programming Applied: Playing to Win , 2001 .

[33]  Ellen Isaacs,et al.  Interviewing customers: discovering what they can't tell you , 1996, CHI Extended Abstracts.

[34]  Robert R. Kessler,et al.  The collaborative software process(sm) , 2000 .

[35]  Glenford J. Myers,et al.  Art of Software Testing , 1979 .

[36]  John B. Black,et al.  Software psychology: The need for an interdisciplinary program , 1986, Proceedings of the IEEE.

[37]  Bill Curtis,et al.  Modern Coding Practices and Programmer Performance , 1979, Computer.

[38]  C. G. Jung.  Psychological Types , 2000 .

[39]  Sallie M. Henry,et al.  The effects of roles and personality characteristics on software development team effectiveness , 1998 .

[40]  Bill Curtis.  Empirical studies of the software design process , 1990 .

[41]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

[42]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[43]  Bill Curtis.  Software Process Improvement: Methods and Lessons Learned , 1997, Proceedings of the (19th) International Conference on Software Engineering.