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 ...