Search

It is well acknowledged in the information systems (IS) literature that information technology (IT) plays an important role in firm innovation. A small but growing body of empirical evidence points to the importance of IT employees as an important complementary resource, particularly for IT-related innovation. However, there is an open question as to whether investment in such resources is complementary across a range of innovation types. This research note aims to provide theoretical and empirical clarity by emphasizing the complementary nature of firm investment in IT and in IT human resources (HR) in affecting firm innovation performance across four types of innovation: incremental, radical, non-IT related and IT related. Drawing on the theory of complementarities and theorizing about the operand and operant nature of resources, we argue that firm investment in IT HR enables firms to gain additional innovation value from their IT investments and vice versa. Using a sample involving 36,812 firm-year observations, we find that firms with robust investments in IT and in IT human resources produce more patents with greater value. Furthermore, we find that such firms produce more patents that emphasize new knowledge and those that build on existing knowledge. Finally, we find that this complementarity promotes IT-related and non–IT-related innovation. A series of analyses demonstrate the robustness of these results. We discuss implications for theory and practice.

Purpose: Advances in information technology coupled with the need to build resilience against disruptions by pandemics like COVID-19 continue to emphasize offshoring services in the software industry. Service-level agreements (SLAs) have served as a key mechanism for safeguarding against risk in offshore service arrangements. Yet, variations in service cost and quality persist. This study aims to open up the blackbox linking SLAs to offshore project outcomes by examining (1) how the provisions in these contracts affect the ability of project teams – the work unit primarily in charge of producing the offshored service – to achieve their objectives and fulfill client requirements and (2) how differences in contextual factors shape the effects of these provisions. Design/methodology/approach: The authors incorporate the role of organizational work practice differences to understand the challenges that 270 offshore project teams faced in coordinating and integrating technical and business domain knowledge across organizational boundaries in offshore arrangements. The examined offshore IT projects were managed by a leading software vendor in India and several of its US-based clients over a three-year period. Findings: The authors demonstrate that organizational work practice differences represent a barrier to offshore project success, and that project team transition processes are an important mechanism for overcoming these barriers. Moreover, the authors find that transition processes represent key mediating mechanisms through which SLA provisions affect offshore project outcomes. Originality/value: The study findings shed light on how SLAs shape software project teams' balance between activities aimed at meeting client needs and those aimed at containing costs.

As new information technology (IT) platforms continue to emerge, the technical project risk associated with developing IT projects for these platforms is particularly challenging for organizations. We develop a nomological network of people, process, and technology to gain insight into how the effect of technical project risk can be mitigated at the IT project team level. Drawing on cultural contingency theory, the IT project risk framework, and the IT project management literature, we elaborate on the IT project team composition and team processes necessary to mitigate technical project risk. We tested the nomological network by conducting a field study of 325 IT project teams over a 3-year period at a large corporation in China. We found that project risk mitigation processes mediated the effect of IT project teams’ cultural composition on IT project performance, and the effect of these processes on IT project performance was stronger under high levels of technical project risk compared to low levels of such risk. By incorporating the cultural contingency theory into developing a nomological network of technical risk mitigation processes, this work not only contributes to the IT project management literature, but also provides suggestions for practitioners on how to better leverage people, process, and technology in mitigating IT project risks.

As new information technology (IT) platforms continue to emerge, the technical project risk associated with developing IT projects for these platforms is particularly challenging for organizations. We develop a nomological network of people, process, and technology to gain insight into how the effect of technical project risk can be mitigated at the IT project team level. Drawing on cultural contingency theory, the IT project risk framework, and the IT project management literature, we elaborate on the IT project team composition and team processes necessary to mitigate technical project risk. We tested the nomological network by conducting a field study of 325 IT project teams over a 3-year period at a large corporation in China. We found that project risk mitigation processes mediated the effect of IT project teams’ cultural composition on IT project performance, and the effect of these processes on IT project performance was stronger under high levels of technical project risk compared to low levels of such risk. By incorporating the cultural contingency theory into developing a nomological network of technical risk mitigation processes, this work not only contributes to the IT project management literature, but also provides suggestions for practitioners on how to better leverage people, process, and technology in mitigating IT project risks.

As new information technology (IT) platforms continue to emerge, the technical project risk associated with developing IT projects for these platforms is particularly challenging for organizations. We develop a nomological network of people, process, and technology to gain insight into how the effect of technical project risk can be mitigated at the IT project team level. Drawing on cultural contingency theory, the IT project risk framework, and the IT project management literature, we elaborate on the IT project team composition and team processes necessary to mitigate technical project risk. We tested the nomological network by conducting a field study of 325 IT project teams over a 3-year period at a large corporation in China. We found that project risk mitigation processes mediated the effect of IT project teams’ cultural composition on IT project performance, and the effect of these processes on IT project performance was stronger under high levels of technical project risk compared to low levels of such risk. By incorporating the cultural contingency theory into developing a nomological network of technical risk mitigation processes, this work not only contributes to the IT project management literature, but also provides suggestions for practitioners on how to better leverage people, process, and technology in mitigating IT project risks.

As new information technology (IT) platforms continue to emerge, the technical project risk associated with developing IT projects for these platforms is particularly challenging for organizations. We develop a nomological network of people, process, and technology to gain insight into how the effect of technical project risk can be mitigated at the IT project team level. Drawing on cultural contingency theory, the IT project risk framework, and the IT project management literature, we elaborate on the IT project team composition and team processes necessary to mitigate technical project risk. We tested the nomological network by conducting a field study of 325 IT project teams over a 3-year period at a large corporation in China. We found that project risk mitigation processes mediated the effect of IT project teams’ cultural composition on IT project performance, and the effect of these processes on IT project performance was stronger under high levels of technical project risk compared to low levels of such risk. By incorporating the cultural contingency theory into developing a nomological network of technical risk mitigation processes, this work not only contributes to the IT project management literature, but also provides suggestions for practitioners on how to better leverage people, process, and technology in mitigating IT project risks.

We integrate control theory and the information systems (IS) project management literature using a multilevel lens to theorize the cross-level effects of technical IS project risk on individual developer outcomes-performance and psychological stress- and the mechanisms by which IS project managers' project-related knowledge attenuates this relationship. We argue that IS project managers with project-related knowledge mitigate technical IS project risk by facilitating the enactment of internal and external process controls in their IS projects. Our empirical study involves data collected from 1,230 individual developers embedded in 130 IS project teams that are managed by 20 IS project managers. Our results provide strong support for the three-level model and its set of (a) cross-level main effects of technical IS project risk on individual developer outcomes; (b) cross-level main effects of IS project manager project-related knowledge on enacted internal and external process controls; and (c) cross-level moderation of the relationship between technical IS project risk and individual developer outcomes by IS project manager project-related knowledge through internal and external process controls. Our study provides insights on how IS project management, IS project process controls, and technical IS project risk must be managed as a system of multilevel dependencies to achieve the desired developer outcomes.

The success of information systems development (ISD) projects depends on the developers who deliver them. However, developers face many challenges in bringing an ISD project to successful completion. These projects are often large and highly complex, with volatile targets, creating a stressful environment for developers. Although prior literature has considered how technical ISD risk factors, such as project size, complexity, and target volatility, affect team- and project-level outcomes, their effects on developers have received limited attention. This gap in the literature is problematic for two reasons: (1) the interplay between developers and project characteristics are unaccounted for, resulting in an incomplete picture of ISD; and (2) developer stress has been shown to reduce team performance. In this research, we examine the role of empowering leadership in reducing developer stress in ISD. We develop a multilevel model of the effect of empowering leadership on the relationship between technical ISD risk factors and developers' role perceptions, and explore the consequences for developers' stress. The model was tested in a field study of 350 developers in 73 ISD teams from a large U.S.-based firm. Results showed that empowering leadership ameliorated the negative effects of project size and target volatility on role ambiguity as well as the negative effects of project size, complexity, and target volatility on role conflict and stress. We also found that empowering leadership reduced role ambiguity, role conflict, and stress directly, and that role ambiguity and role conflict increased stress. Project size, complexity, and target volatility were found to increase empowering leadership behaviors. We conclude that empowering leadership can be an effective means of helping developers cope with technical ISD risk factors and discuss the implications of our findings for research and practice.

Research on information technology (IT) adoption and use, one of the most mature streams of research in the information science and information systems literature, is primarily based on the intentionality framework. Behavioral intention (BI) to use an IT is considered the sole proximal determinant of IT adoption and use. Recently, researchers have discussed the limitations of BI and argued that behavioral expectation (BE) would be a better predictor of IT use. However, without a theoretical and empirical understanding of the determinants of BE, we remain limited in our comprehension of what factors promote greater IT use in organizations. Using the unified theory of acceptance and use of technology as the theoretical framework, we develop a model that posits 2 determinants (i.e., social influence and facilitating conditions) of BE and 4 moderators (i.e., gender, age, experience, and voluntariness of use) of the relationship between BE and its determinants. We argue that the cognitions underlying the formation of BI and BE differ. We found strong support for the proposed model in a longitudinal field study of 321 users of a new IT. We offer theoretical and practical IT implications of our findings.

"Team temporal leadership" orients teams toward managing the time-related aspects of their work. We examine how perceived time pressure affects team processes and subsequent performance under weak versus strong team temporal leadership. The results of our field study of 111 project teams show that the mediated relationship between perceived time pressure and team performance is non-linear. Moreover, this non-linear mediated relationship is moderated by team temporal leadership such that, under strong team temporal leadership, the indirect effect of perceived time pressure on team performance is mostly positive, while, under conditions of weak team temporal leadership, the indirect effect is positive at low levels of perceived time pressure and negative at intermediate to high levels. Implications for current and future time pressure research are also discussed.

Software development is a complex undertaking that continues to present software project teams with numerous challenges. Software project teams are adopting extreme programming (XP) practices in order to overcome the challenges of software development in an increasingly dynamic environment. The ability to coordinate software developers' efforts is critical in such conditions. Expertise coordination has been identified as an important emergent process through which software project teams manage non-routine challenges in software development. However, the extent to which XP enables software project teams to coordinate expertise is unknown. Drawing on the agile development and expertise coordination literatures, we examine the role of collective ownership and coding standards as processes and practices that govern coordination in software project teams. We examine the relationship between collective ownership, coding standards, expertise coordination, and software project technical quality in a field study of 56 software project teams comprising 509 software developers. We found that collective ownership and coding standards play a role in improving software project technical quality. We also found that collective ownership and coding standards moderated the relationship between expertise coordination and software project technical quality, with collective ownership attenuating the relationship and coding standards strengthening the relationship. Theoretical and practical implications of the findings are discussed. © 2009 Operational Research Society Ltd.

Software development is a complex undertaking that continues to present software project teams with numerous challenges. Software project teams are adopting extreme programming (XP) practices in order to overcome the challenges of software development in an increasingly dynamic environment. The ability to coordinate software developers' efforts is critical in such conditions. Expertise coordination has been identified as an important emergent process through which software project teams manage non-routine challenges in software development. However, the extent to which XP enables software project teams to coordinate expertise is unknown. Drawing on the agile development and expertise coordination literatures, we examine the role of collective ownership and coding standards as processes and practices that govern coordination in software project teams. We examine the relationship between collective ownership, coding standards, expertise coordination, and software project technical quality in a field study of 56 software project teams comprising 509 software developers. We found that collective ownership and coding standards play a role in improving software project technical quality. We also found that collective ownership and coding standards moderated the relationship between expertise coordination and software project technical quality, with collective ownership attenuating the relationship and coding standards strengthening the relationship. Theoretical and practical implications of the findings are discussed. © 2009 Operational Research Society Ltd.

Software development is a complex undertaking that continues to present software project teams with numerous challenges. Software project teams are adopting extreme programming (XP) practices in order to overcome the challenges of software development in an increasingly dynamic environment. The ability to coordinate software developers' efforts is critical in such conditions. Expertise coordination has been identified as an important emergent process through which software project teams manage non-routine challenges in software development. However, the extent to which XP enables software project teams to coordinate expertise is unknown. Drawing on the agile development and expertise coordination literatures, we examine the role of collective ownership and coding standards as processes and practices that govern coordination in software project teams. We examine the relationship between collective ownership, coding standards, expertise coordination, and software project technical quality in a field study of 56 software project teams comprising 509 software developers. We found that collective ownership and coding standards play a role in improving software project technical quality. We also found that collective ownership and coding standards moderated the relationship between expertise coordination and software project technical quality, with collective ownership attenuating the relationship and coding standards strengthening the relationship. Theoretical and practical implications of the findings are discussed. © 2009 Operational Research Society Ltd.

This paper extends prior research in household technology adoption by incorporating the role of espoused cultural values. Specifically, we theorize that espoused cultural values-individualism/collectivism, masculinity/ femininity, power distance, uncertainty avoidance, and long-term orientation-play an important role in affecting consumers' behaviors by altering consumers' belief structures-attitudinal beliefs, normative beliefs, and control beliefs. Our theoretical model predicts that the impact of consumers' belief structures on household technology adoption intention varies across consumers with different cultural values. Propositions are provided to explain how different cultural mechanisms moderate the relationships between consumers' beliefs and household technology adoption intention. The paper concludes with theoretical implications, future research directions, and practical implications. © 2008 Springer Science+Business Media, LLC.

This paper extends prior research in household technology adoption by incorporating the role of espoused cultural values. Specifically, we theorize that espoused cultural values-individualism/collectivism, masculinity/ femininity, power distance, uncertainty avoidance, and long-term orientation-play an important role in affecting consumers' behaviors by altering consumers' belief structures-attitudinal beliefs, normative beliefs, and control beliefs. Our theoretical model predicts that the impact of consumers' belief structures on household technology adoption intention varies across consumers with different cultural values. Propositions are provided to explain how different cultural mechanisms moderate the relationships between consumers' beliefs and household technology adoption intention. The paper concludes with theoretical implications, future research directions, and practical implications. © 2008 Springer Science+Business Media, LLC.

Prior reviews of the CEO turnover and succession literature suggest that empirical findings on organizational implications continue to be equivocal. In this paper, we develop a conceptual framework for examining the impact of CEO turnover and succession on organizational capabilities. Using the social network perspective as a theoretical lens, we identify conditions in which CEO turnover is expected to influence organizational exploration and exploitation capabilities. We also identify contingencies under which CEO succession will moderate the impact of CEO turnover on organizational capabilities. Our framework provides a useful lens through which to view the consequences of CEO turnover and succession and sheds some light on the equivocal findings to date.

Prior reviews of the CEO turnover and succession literature suggest that empirical findings on organizational implications continue to be equivocal. In this paper, we develop a conceptual framework for examining the impact of CEO turnover and succession on organizational capabilities. Using the social network perspective as a theoretical lens, we identify conditions in which CEO turnover is expected to influence organizational exploration and exploitation capabilities. We also identify contingencies under which CEO succession will moderate the impact of CEO turnover on organizational capabilities. Our framework provides a useful lens through which to view the consequences of CEO turnover and succession and sheds some light on the equivocal findings to date.

Prior reviews of the CEO turnover and succession literature suggest that empirical findings on organizational implications continue to be equivocal. In this paper, we develop a conceptual framework for examining the impact of CEO turnover and succession on organizational capabilities. Using the social network perspective as a theoretical lens, we identify conditions in which CEO turnover is expected to influence organizational exploration and exploitation capabilities. We also identify contingencies under which CEO succession will moderate the impact of CEO turnover on organizational capabilities. Our framework provides a useful lens through which to view the consequences of CEO turnover and succession and sheds some light on the equivocal findings to date.

Software project teams are often faced with the potential for changing requirements during software development. Such changes present a significant challenge to software project teams often resulting in cost overruns, missed deadlines, and faulty code. While the phenomenon of requirements changes by itself is not new, the frequency with which such changes occur has increased in recent years. Software project teams continue to be challenged by the uncertainty caused by the potential for such changes. Flexibility has been identified as a desirable characteristic of teams in this type of environment. This dissertation is made up of two essays that examine the processes and governance mechanisms that can potentially enable software project teams to achieve greater flexibility. The first essay provides a team process-oriented view of the problem. Specifically, agile programming practices and boundary spanning activities are argued to enhance software project team effectiveness by receiving customer feedback and incorporating requirements changes on an on-going basis. A longitudinal field study of 56 software development teams provides support for these arguments. The second essay adopts a team governance lens. Specifically, formal and informal control modes are posited to influence software project team effectiveness. Control mechanisms that promote team autonomy and flexibility are argued to positively influence software project team effectiveness. Further, team leader behaviors are also expected to play a critical role in facilitating software project team effectiveness. These arguments are tested and largely supported. Together, the two essays shed light on how software project teams can be designed to have greater flexibility--an important stepping stone for managing software development in the face of requirements uncertainty.