Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> Content overview <s> Managers in charge of introducing new production technologies need to approach implementation as an internal marketing campaign. Potential users of the innovation are subject to various influences. By building on positive influences and countering negative ones, implementation managers can speed the diffusion of the innovation within the organization. For instance, in the case presented here, programmers and analysts were more likely to use new structured software development methods if their supervisors, influential peers, and especially their clients supported use. Users were more likely than nonusers to have received training close to the time they were asked to use the new methods and to see very specific, rather than just general, potential benefits. <s> BIB001 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> Content overview <s> Research into information systems development (ISD) methodologies is generally restricted to the creation or elaboration of methodologies or the provision of CASE support. This paper proposes that a fruitful area of research, which will provide insights into the effectiveness of ISD methodologies, must centre on the observation of the practice of systems developers, users and managers, and the study of methodologies in use. Such a programme requires certain techniques, ideally longitudinal ethnographic case studies. Preliminary results from a couple of case studies indicate that ISD methodologies are not used as prescribed but this does not necessarily prevent the successful completion of development projects. <s> BIB002 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> Content overview <s> There is a myriad of system development methodologies, techniques, and tools that have been developed ever since businesses started using computers for information processing. However, there is no real consensus on the aptness or applicability of these methods. There are proponents and critics of each method, and different organizations use different methods. This article identifies many of the system development methods in use today. It, then, empirically assesses these methods on a comprehensive set of attributes. It also makes a contingency analysis of the applicability of the methods based on system life cycle stage, system type, and problem structure. These results should serve as a valuable set of inputs in method selection for system development. <s> BIB003 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> Content overview <s> The adoption of systems development methodologies has been a subject for research and a topic for discussion for a number of years. One factor, which is often emphasized, is education and training. However, very little research has been focused on the role of formal university education and the dissemination of systems development methodologies. This is the background for this study. It investigates the extent to which a methodology, as well as its encompassing component methods and techniques, taught at the Copenhagen Business School, has been adopted by students and the organizations they are working for. The main result is that very few examples of direct adoption of the methodology taught have been found, but that the training has in general positive influence on the students' utilization of methodologies. The reasons for adoption and non-adoption are discussed based on a grounded theory analysis. <s> BIB004 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> Content overview <s> Object-oriented systems development (OOSD) is a recent innovation in software development that is often cited as a viable solution to many of the ills plaguing this critical industry. However, some express doubt about the potentially over-hyped claims of OOSD. While there are many accounts of the successful application of OOSD, widespread acceptance has not been achieved, implying that OOSD may not be viewed as positively by industry as the literature would suggest.To address this dilemma, the present study examines a wide variety of specific beliefs about OOSD as provided by a survey of 150 systems developers. Using Ajzen's (1988) theory of planned behavior as a foundation, an exploratory factor analysis is performed to determine which specific beliefs about OOSD are indeed salient indicators of three fundamental concepts that should influence acceptance: the usefulness of OOSD, social pressure to use OOSD, and the ease of using OOSD. The results of the study reveal that while many specific beliefs about OOSD are indeed salient indicators of these more fundamental, potentially influential factors, many other beliefs are not. This study should prove helpful to practitioners who are considering the adoption or continued use of OOSD, and to researchers who are interested in the diffusion of innovations in general <s> BIB005 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> Content overview <s> In this research, the authors examine factors affecting the use of product development methods. Based on established behavioral theories, they develop and test a model that can explain, and hence predict, the extent of use of development methods. Although their model can be adapted to any development process, they apply it to software development. To test their model, they examine the combined effects of a number of important usage factors that contribute to the depth and breadth of use of two software development approaches: the waterfall model and prototyping. Two main constructs, process quality and facilitating conditions, are found to be the drivers of method usage. The dominating "facilitating conditions" and "process quality" indicators vary from one method to another product quality was not found to be a statistically significant factor in explaining usage. The authors' results are consistent with the view taken by the software process improvement movement, i.e., that a quality process will result in a quality product. <s> BIB006 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> Content overview <s> Many organizations attempt to deploy methodologies intended to improve software development processes. However, resistance by individual software developers against using such methodologies often obstructs their successful deployment. To better explain why individual developers accept or resist methodologies, five theoretical models of individual intentions to accept information technology tools were examined. In a field study of 128 developers in a large organization that implemented a methodology, each model explained significant variance in developers' intentions to use the methodology. Similar to findings from the tool adoption context, we found that, if a methodology is not regarded as useful by developers, its prospects for successful deployment may be severely undermined. In contrast to the typical pattern of findings in a tool context, however, we found that methodology adoption intentions are driven by: 1) the presence of an organizational mandate to use the methodology, 2) the compatibility of the methodology with how developers perform their work, and 3) the opinions of developers' coworkers and supervisors toward using the methodology. Collectively, these results provide surprising new insights into why software developers accept or resist methodologies and suggest what software engineering managers might do to overcome developer resistance. <s> BIB007 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> Content overview <s> Seeking to improve software development, many organizations attempt to deploy formalized methodologies. This typically entails substantial behavioral change by software developers away from previous informal practices toward conformance with the methodology. Developers' resistance to such change often results in failure to fully deploy and realize the benefits of the methodology. The present research draws upon theories of intention formation and innovation diffusion to advance knowledge about why developers accept or resist following methodologies. Results from a field study within a large organization indicate that developers' intentions are directly influenced by their perceptions of usefulness, social pressure, compatibility, and organizational mandate. This pattern of intention determinants is quite different from that typically observed in studies of information technology tool adoption, revealing several key differences between the domains of tool versus methodology adoption. Specifically, although organizational mandate had a significant effect on intentions, the strength of its direct influence was the lowest among the four significant constructs, and usefulness, compatibility, and social pressure all influenced intentions directly, above and beyond the effects of organizational mandate. The findings suggest, contrary to popular belief, that an organizational mandate is not sufficient to guarantee use of the methodology in a sustained manner. <s> BIB008 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> Content overview <s> In an ongoing effort to improve systems development, a variety of innovative products, such as CASE, and processes, such as object-oriented development, have been introduced over the years. While models such as the technology acceptance model (TAM) have been used to explain the acceptance of development products, very little research exists on the acceptance of the more complex development processes. Using the theory of planned behavior, goal-setting theory, and the TAM, this study develops a model to explain the acceptance of innovative information systems development processes by individual software developers. A total of 150 experienced developers completed a survey designed to explore factors that relate to the acceptance of object-oriented systems development (OOSD), the focus of this particular study. An analysis of the collected data reveals a succinct model that explains more than 60% of a developer's acceptance of OOSD. These results have important implications for both managers and process designers in their efforts to promote the acceptance of systems development innovations among developers. Researchers should also benefit from an augmented understanding of the acceptance of complex innovative processes. <s> BIB009 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> Content overview <s> We studied the differences in perception between IS managers and developers about the deployment of systems development methodologies. The results indicated that IS managers were generally more positive about systems development methodologies than were developers. IS managers perceived methodology support for organizational alignment, and methodology impact on the productivity and quality of the development process to be significantly more important than did system developers, who, in turn, perceived methodology support for verification and validation significantly higher than did IS managers. These differences can be explained by the relevance and importance of the support to the task that the stakeholders perform. <s> BIB010 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> Content overview <s> This exploratory study analyzes the relationship between organizational culture and the deployment of systems development methodologies. Organizational culture is interpreted in terms of the competing values model and deployment as perceptions of the support, use, and impact of systems development methodologies. The results show that the deployment of methodologies by IS developers is primarily associated with a hierarchical culture that is oriented toward security, order, and routinization. IT managers' critical attitudes of the deployment of methodologies in organizations with a strong rational culture (focusing on productivity, efficiency, and goal achievement) is also worth noting. Based on its empirical findings, the paper proposes a theoretical model to explain the impact of organizational culture on the deployment of systems development methodologies. <s> BIB011 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> Content overview <s> The theories of social exchange, task-technology fit, and technology acceptance are utilized in a field study of software development methodologies. This investigation includes the effects of user experiences on perceptions of acceptance and usage of a methodology. More specifically, perceptions of the outputs and deliverables from a methodology and perceptions of challenges and obstacles to using and applying a methodology were found to significantly and positively influence perceived usefulness and negatively influence ease of use of a methodology, respectively, within a developer's organization. Perceived usefulness was a positive and strong antecedent to perceptions of fit between the methodology and client problems, and the strengthening of efficacy beliefs about the methodology. <s> BIB012
As illustrated in the previous section, earlier studies on ISDM methodologies are largely descriptive and do not explain acceptance at an individual level BIB011 . It is only very recently that more explanatory studies that actually study the research problems at hand BIB011 , have appeared. Westrup BIB002 conducted longitudinal case studies of the development and implementation of IS to explore how ISD methodologies are acquired by developers, and describe some of the ways in which methodologies are used in practice. An important conclusion of the study is that users reinterpreted the methodologies in each situation. Therefore, they did not follow the methodology rigorously. They also observe that developers used methodologies to complete deliverables and as insurance, to deny responsibility in case of project failure. Based upon the use of methodology manuals, Hidding  comes to a similar conclusion. He finds that even though practitioners seldom read methodology material, they are still able to produce the deliverables. Based on his research, Hidding  suggests that people assume different Some studies focus on very specific determinants of methodology adoption and suggest (directly or indirectly) determinants that could impact the behavioral decision. Kautz and Heje BIB004 conducted explorative studies to understand the role of formal university education on the adoption of systems development methodologies by means of grounded theory. They found a positive effect. However, the authors mentioned themselves that only a simple statistical analysis was carried out in their research. Huisman and Iivari BIB010 studied the perceptions of IS managers and developers, and found that managers had more positive views on the use of ISD methodologies than the developers. They concluded that ISD methodologies reflect management"s agenda, implying different expectations, assumptions and norms. This provides further evidence for the widespread understanding that while developing and implementing IS methodologies, organisations often do not consider the values, beliefs and needs of the actual users. This might be the cause of the methodologies eventually being rejected. In a related study, Iivari and Huisman BIB011 found that organisational culture orientations, especially hierarchical and rational organisational cultures, affect the use of ISD methodologies. Most of the factors that have been reported have been studied separately and, for this reason, the relationships among them have not been explored sufficiently BIB006 . Although these studies identify some factors to have a significant effect on usage, when grouped together with other factors, they might become insignificant. Therefore, we suggest, along with Khalifa and Verner BIB006 , that in order to determine what factors really drive the extent of use of ISDM methodologies, the combined effects (instead of isolated study of the effects) of these factors need to be examined. In a plethora of research, the use of ISDM methodologies per se has not been studied, but rather the adoption of certain methods/techniques (such as object-oriented programming) and tools (such as CASE tools) BIB007 . Some of these studies have contributed in a major way to understanding the antecedents of an individual"s decision to use ISDM methodologies. For example, Leonard-Barton BIB001 studied innovation acceptance, based on the adoption or rejection of structured systems analysis (SSA), and suggested that social pressure and training positively influence the use of methodologies. Although the author herself mentions that SSA is a method used only in the first phase of systems development and not a comprehensive methodology, we still consider her findings worthy of acknowledgement since they were published at a time when research on the adoption of IS methodologies was in its infancy. Khalifa and Verner BIB006 studied several determinants of software developers' use of two specific approaches, namely prototyping and waterfall. Although, similar to Palvia and Nosek BIB003 , they regard prototyping to be a methodology, we consider it to be a method/technique since it is very often used within the waterfall methodology, as the authors point out themselves. Johnson et al. BIB005 applied TPB to examine the beliefs that underlie attitudes, social norms and behavioural control constructs, to examine IS developers" beliefs underlying intentions to use object oriented (OO) methods; however, they did not empirically test the relationships between the constructs. Research discussed in this paragraph represents an important step towards examining the underlying topic, but since the use of ISDM methodologies involves radical change compared to using simple methods and tools, we consider human behaviour, in the context of using complete methodologies, to be more complex. This requires a deeper examination that should take into consideration not only cognitive but also automatic user behaviour, such as emotions and habits. Riemenschneider et al. BIB007 attempted to remedy some of the shortcomings of the research of Johnson et al. BIB005 by using five theoretical models to study the intentions of software developers to use methodologies. He found that the usefulness of methodologies plays the most crucial role in the adoption process. Being the first study to empirically test these five models in a methodology context, Riemenschneider et al. BIB007 provided thoughtful insights on the determinants of intention to adopt methodologies. In a related study (based on the quantitative data of Riemenschneider et. al. BIB007 ), Hardgrave et al. BIB008 investigated the determinants of the individual developer's intentions to follow methodologies, based on TAM and DOI. In their study, perceived usefulness, social pressure, perceived compatibility and organisational mandate were found to have a direct influence on individual developers' intentions to follow methodologies, whereas social pressure, complexity and perceived compatibility were found to be significant determinants of perceived usefulness. In a similar study, Hardgrave and Johnson BIB009 found that organisational usefulness (OU), subjective norm and perceived behavioural control-internal significantly influenced intentions of software developers to use OO-SD processes. Although they propose that personal usefulness (PU) might also affect the intention to use, they could not psychometrically separate it from organisational usefulness. They suggest that the cause of this might lie in that "…developers do not view their personal benefits separately from organisational benefits" BIB009 . We suggest differentiating OU and PU based on other dimensions, influenced by purely personal interests (independent of organisational usefulness) such as materialism and enjoyment. Kacmar et al. BIB012 conducted a field study of ISD methodologies, applying theories of social exchange, task-technology fit, and technology acceptance. They found that perceptions of the outputs and deliverables from a methodology, and perceptions of challenges and obstacles to using and applying a methodology, to significantly and positively influence perceived usefulness. They found that these factors also negatively influence ease of use of a methodology, respectively, within a developer"s organisation. Although Riemenschneider et al. BIB007 , Hardgrave et al. BIB008 and Hardgrave and Johnson BIB009 contribute significantly in understanding the topic at hand, they consider adoption to be merely the intention to use and do not study the actual use of the methodology. In our view, the mere intention to use a methodology, even though it plays a major role in determining actual use, does not imply that the individual will actually use the methodology. As such, future research could focus on studying the actual use of a methodology, rather than the mere intention to do so.