Team Familiarity, Role Experience, and Performance: Evidence from Indian Software Services
Much of the literature on team learning views experience as a unidimensional concept captured by the cumulative production volume of, or the number of projects completed by, a team. Implicit in this approach is the assumption that teams are stable in their membership and internal organization. In practice, however, such stability is rare, because the composition and structure of teams often change over time (e.g., between projects). In this paper, we use detailed data from an Indian software services firm to examine how such changes may affect the accumulation of experience within, and the performance of, teams. We find that the level of team familiarity (i.e., the average number of times that each member has worked with every other member of the team) has a significant positive effect on performance, but we observe that conventional measures of the experience of individual team members (e.g., years at the firm) are not consistently related to performance. We do find, however, that the role experience of individuals in a team (i.e., years in a given role within a team) is associated with better team performance. Our results offer an approach for capturing the experience held by fluid teams and highlight the need to study context-specific measures of experience, including role experience. In addition, our findings provide insight into how the interactions of team members may contribute to the development of broader firm capabilities.
Volume (Year): 55 (2009)
Issue (Month): 1 (January)
|Contact details of provider:|| Postal: |
Web page: http://www.informs.org/
More information through EDIRC
When requesting a correction, please mention this item's handle: RePEc:inm:ormnsc:v:55:y:2009:i:1:p:85-100. See general information about how to correct material in RePEc.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: (Mirko Janc)
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
If references are entirely missing, you can add them using this form.
If the full references list an item that is present in RePEc, but the system did not link to it, you can help with this form.
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your profile, as there may be some citations waiting for confirmation.
Please note that corrections may take a couple of weeks to filter through the various RePEc services.