The Proceedings of the Information Systems Education Conference 2004: §3263    Home    Papers/Indices    prev (§3262)    Next (§3264)
Sat, Nov 6, 10:30 - 10:55, Morgan Room     Paper (refereed)
Recommended Citation: Tu, Y and Y Tu.  Achieving an Effective and Successful IS Group Project.  In The Proceedings of the Information Systems Education Conference 2004, v 21 (Newport): §3263. ISSN: 1542-7382.

Achieving an Effective and Successful IS Group Project

Refereed5 pages
Yanbin Tu    [a1] [a2]
School of Business
University of Connecticut    [u1] [u2]
Storrs, Connecticut, USA    [c1] [c2]

Yanlin Tu    [a1] [a2]
Shanghai Yangjing Juyuan Experimental School    [u1] [u2]
Pudong, Shanghai, China    [c1] [c2]

A group project plays an important role to train information systems (IS) studentsí skills in teamwork. However, an effective and successful group project is not straightforward. In this paper, we summarize some teaching tips to achieve an effective and successful group project. In the preparation stage, the instructor should choose a suitable topic and form a reasonable team. In the execution stage, the instructor should try to align the studentís time-skewed behavior; in some circumstances, adjustment of topics and team members is needed. Studentsí separating the group project into several independent and isolated individual works should also be avoided. Additionally, some mechanisms are required to reduce the free-rider problem in a group project. In the assessment stage, the instructor should not only evaluate the overall project, but also accurately distinguish each memberís contribution. In the post-assessment stage, revision of a group project, which is commonly ignored, should draw more attention from the instructor. We also discuss the importance of incorporating groupware into an IS group project and demonstrate several roles of groupware in an IS group project.

Keywords: teamwork, group project, free-rider problem, assessment, groupware

Read this refereed paper in Adobe Portable Document (PDF) format. (5 pages, 359 K bytes)
Preview this refereed paper in Plain Text (TXT) format. (22 K bytes)

Comments and corrections to