Using Beibin's leadership role to improve team effectiveness: An empirical investigation

Journal of Systems and Software

Volumn 44, Issue 3, 1999, Pages 241-250

  Henry, Sallie M ^a   Stevens, K Todd ^a  

^a State University   (United States)

Author keywords

Empirical studies; Roles; Software engineering; Team formation

Indexed keywords

BENCHMARKING; PRODUCTIVITY; PROFESSIONAL ASPECTS;

TEAM FORMATIONS;

SOFTWARE ENGINEERING;

EID: 0032761158     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0164-1212(98)10060-2     Document Type: Article

References (27)

1. Belbin, R.M., 1981. Management Teams. Wiley, New York.
2. Belbin, M., 1993. Team Roles at Work. Butterworth-Heinemann, Oxford.
3. Biddle, B.J., 1979. Role Theory: Expectations, Identities, and Behaviors. Academic Press, New York.
4. Boehm, B.W., 1981. Software Engineering Economics. Prentice-Hall, Englewood Cliffs, NJ.
5. Bostrom, R.P., Kaiser, K.M., 1981. Personality differences within systems project teams: Implications for designing solving centers. In: Proceedings of the Eighteenth Annual Computer Personnel Research Conference, 3-5 June. ACM (Assoc. Comput. Machinery), New York, pp. 248-285.
6. Cherlin, M., 1981. The Toll of Turnover. Datamation (April), 208-212.
7. Curtis, B., Soloway, E.M., Brooks, R.E., Black, J.B., Ehrlich, K., Rudy Ramsey, H., 1986. Software psychology: The need for an interdisciplinary program. Proc. IEEE (August), 1092-1106.
8. DeMarco, T., Lister, T., 1987. Peopleware: Productive Projects and Teams. Dorset, New York.
9. Henry, S.M., 1983. A project oriented course on software engineering. In: Proceedings of the 1983 ACM SIGCSE Symposium on Computer Science Education, February, pp. 57-61.
10. Holt, R.W., Boehm-Davis, D.A., Schultz, A.C., 1987. Mental representations of programs for student and professional programmers. In: Olson, G.M., Sheppard, S., Soloway, E. (0Eds.), Empirical Studies of Programmers: Second Workshop, Washington, D.C., 7-8 December, Ablex, Norwood, NJ, pp. 33-46.
11. Jeffery, D.R., 1987. The relationship between team size, experience, and attitudes and software development productivity. In: Proceedings of COMPSAC87, Tokyo, Japan, 7-9 October. IEEE Computer Soc. Press, Silver Spring, MD, pp. 2-8.
12. Jeffrey, H.J., Putman, A.O., 1994. Relationship definition and management: Tools for requirements analysis. Journal of Systems and Software (March), 277-294.
13. Knowles, E.S., 1982. From individuals to group members: A dialectic for the social sciences. In: Ickes, W., Knowles, E.S. (Eds.), Personality, Roles and Social Behavior. Springer, New York.
14. Littell, R.C., Freund, R.J., Spector, P.C., 1991. SAS System for Linear Models, 3rd edition. SAS Institute, Cary, North Carolina.
15. Mills, H.D., 1983. Software Productivity. Little, Brown and Company, Boston.
16. Myers, I.B., 1987. Introduction to Type. Consulting Psychologists Press, Palo Alto, CA.
17. Nichols, J.A., 1982. Forward. In: Proceedings of Human Factors in Computer Systems, Gaithersburg, Maryland, 15-17 March. ACM (Assoc. Comput. Machinery Press), New York, p. iii.
18. Sarbin, T.R., 1954. Role Theory. In: Gardner Lindzey (Ed.), Handbook of Social Psychology. Addison-Wesley, Reading, MA.
19. Scott, T.J., Cross II, J.H., 1995. Team selection methods for student programming teams. In: Software Engineering Education: Proceedings of Eighth SEI CSEE Conference, New Orleans, Louisiana, 29 March-1 April. Springer, Berlin, pp. 295-303.
20. Shneiderman, B., 1980. Software Psychology. Winthrop Publishers, Cambridge, MA.
21. Sunstrom, E., De Meuse, K.P., Futrell, D., 1990. Work Teams. American Psychologist (February), 120-133.
22. Thomsett, R., 1990. Effective Project Teams. American Programmer (July/August), 25-35.
23. Trower, J.K., Straub Jr., D.W., 1991. Improving the performance of technologists and users on interdisciplinary teams: An analysis of information systems project teams. Computer Personnel (November), 62-72.
24. von Mayrhauser, A., 1984. Task analysis and the selection of software development team structures. In: Proceedings of COMPSAC84, Chicago, IL, 7-9 November. IEEE Computer Soc. Press, Silver Spring, MD, pp. 120-126.
25. Walz, D.B., Elam, J.J., Krasner, H., Curtis, B., 1987. A methodology for studying software design teams: An investigation of conflict behaviors in the requirements definition phase. In: Olson, G.M., Sheppard, S., Soloway, E. (Eds.), Empirical Studies of Programmers: Second Workshop, Washington, D.C., 7-8 December. Ablex, Norwood, NJ, pp. 83-99.
26. Weinberg, G.M., 1971. The Psychology of Computer Programming. Van Nostrand Reinhold, New York.
27. Zahniser, R.A., 1990. Building software in groups. American Programmer (July/August), 50-56.