Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <s> Centralization and formalization have previously been employed in research designs investigating organizational innovation. The results, however, have been mixed. Three arguments are raised toward explaining this inconsistency. First, innovation is a multi-phased process in which the influence of centralization and formalization could be expected to differ. Second, as innovations may vary with regard to their compatibility to individuals in organizations, the expected influence of centralization and formalization may also vary. Third, organizational innovations may be directed toward particular vested interests, such as the technical or administrative core. Accordingly, the influence of centralization and formalization may also vary. ::: ::: This paper reports on a study which examines the influence of centralization and formalization on organizational innovation given the arguments given above. The effectiveness of employing structural overlays to overcome the conflicting forces often arising between organizational processes and particular organizational behaviors-such as innovative behavior-is investigated as well. ::: ::: Managers of 49 software development groups responded to a questionnaire assessing the influences of centralization and formalization on the initiation, adoption, and implementation of six modern software practices MSP within their software groups. Three of the MSP were technical in nature and three were administrative. The technical MSP were viewed as being incompatible to the technical core. Two structural overlays were investigated regarding their ability to improve the diffusion process: the existence of a formal body responsible for identifying MSP and introducing them into the software group; and, the assignment of computer specialists to projects as "set" teams. <s> BIB001 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <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> BIB002 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <s> Abstract:A general opinion is that systems personnel are unlikely adopters of new systems development methods. Thirty-five systems persons from eleven organizations who attended a seminar/workshop on a requirements defining method were surveyed three months after the seminar to determine whether they used the method and factors influencing usage. Factors about the potential adoptee, the current tasks assigned, and the organization and its existing methods were considered as predictors of usage. The study found adopters to be younger, to have spent less time in their organization and in systems work, not to have a current method that they would have to give up, to perceive themselves to be risk takers, and to be more optimistic about their ability to use the method and have it fit in their organization. <s> BIB003 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <s> Abstract This paper presents the findings of an empirical study of factors affecting the acceptance of CASE by systems developers. Based on two research models (technology acceptance and personal computer utilization) recently published in IS literature, an integrated model which consists of six variables and incorporates key elements of both models was developed to examine determinants of CASE acceptance. The findings indicate that ease of use has the largest influence on CASE acceptance, followed by long-term consequences. Both transitional support and near-term usefulness do not have a significant direct effect on the acceptance but exhibit their indirect influence through ease of use and/or long-term consequences. The implementation gap was found to have a relatively small and negative effect on CASE acceptance through its influence on ease of use, near-term usefulness, and long-term consequences. Implications of the findings, from both a research and a managerial perspective are discussed in this paper. <s> BIB004 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <s> This paper discusses the findings of a field study of experienced systems developers which investigated the use of systems development methodologies (SDMs) in practice. Among the main findings to emerge are the following. There is a wide difference between the formalized sequence of steps and stages prescribed by a methodology and the methodology-in-action uniquely enacted for each development project. Also, there is much evidence which suggests that developers omit certain aspects of methodologies not from a position of ignorance, but from the more pragmatic basis that certain aspects are not relevant to the development environment they face. Thus, methodologies are tailored to the needs of the prevailing development environment and, being documented in a single manual often, are framed at a higher level of granularity that specifies broad activities and objectives, rather than specifying in a very detailed fashion the exact manner in which development should take place. Additionally, the findings clarify the apparently contradictory position in the literature as to whether developer experience is positively or negatively correlated with methodology use. The study would suggest that experienced developers are likely to use methodologies, albeit ones which have been heavily customized to the exigencies of the particular situation. <s> BIB005 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <s> Object-oriented (OO) analysis, design, and programming techniques have emerged as potential solutions to the software crisis. However, learning OO techniques can be a difficult process. This study investigates students' perceptions of the difficulties in learning and using OO techniques. Two groups of students who had recently completed a sixteen-week course on OO systems development participated in the study. Cognitive mapping techniques implemented with group support system (GSS) technology were used to gather information on the students' perceptions. The groups used the GSS to identify what was difficult about learning and using OO techniques, classify these concepts into categories, rank the relative importance of each category, and determine the relationships among the categories. Importance rankings of the categories show that learning basic object concepts was most important to and most difficult for the students, followed by design issues, and programming techniques. Composite cognitive maps of the shared perceptions of group members suggest that educators and industry trainers can reduce the difficulties of learning OO concepts by teaching simplified methodologies and controlling difficulties of the programming environment. <s> BIB006 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <s> Abstract Technology transfer in software engineering involves more than a new idea or evidence that it works. This paper illustrates how technology transfer requires a good idea, the generation of evidence, analysis of that evidence, good packaging and support, and careful consideration of the audience for the technology. By learning from other disciplines, we present a model of technology transfer that can be tailored to a particular organisation's needs. <s> BIB007 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <s> This paper proposes a four-tiered framework for classifying and understanding the myriad of information systems development methodologies that have been proposed in the literature. The framework is divided into four levels: paradigms, approaches, methodologies, and techniques. This paper primarily focuses on the two intermediate levels: approaches and methodologies. The principal contribution of the framework is in providing a new kind of "deep structure" for better understanding the intellectual core of methodologies and approaches and their interrelationships. It achieves this goal by articulating a parsimonious set of foundational features that are shared by subsets of methodologies and approaches. To illustrate how the framework's deep structure provides a better understanding of methodologies' intellectual core, it is applied to eleven examples. The paper also introduces and illustrates a procedure for "accommodating" and "assimilating" new information systems development methodologies in addition to the eleven already discussed. This procedure provides the framework with the necessary flexibility for handling the continuing proliferation of new methodologies. <s> BIB008 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <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> BIB009 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <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> BIB010 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <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> BIB011 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <s> Very little research has been conducted to examine the effects of information technology (IT) maturity on the use of the evaluation methodologies and the management of electronic commerce (EC) benefits. One survey and two in-depth case studies were carried out to examine these practices and processes in large Australian organizations. A key contribution of this research is to extend the Limits-to-Value model to examine the relationship between the levels of IT maturity and the adoption of IT investment evaluation and benefits realization methodologies as well as its effect on the management of business-to-business (B2B) EC benefits. The finding indicates that IT maturity has a positive impact on the adoption of these methodologies. A number of managerial issues and problems have also emerged from the analysis of the data collected. These findings will assist organizations in making better business decisions. Managerial implications and future research directions are also provided. 1 Introduction Investment in information technology (IT) is one of the major factors determining the success or failure of organizations in implementing electronic commerce (EC) projects [18,19,36]. However, senior IT managers have found it increasingly difficult to justify rising IT expenditures [8] and are often under immense pressure to find a way to measure the contribution of their organizations' IT investments in relation to the performance in EC, as well as to find reliable ways to ensure that the business benefits from IT investments are actually realized [I]. Therefore, it is not surprising to see that the term "productivity paradox" has gained increasing notoriety as many studies have suggested relatively static productivity and rising IT expenditure [4,24]. The productivity paradox is die notion that despite large investments in IS/IT over many years, it has been difficult to determine where the IT and B2BEC benefits have actually occurred, if indeed there have been any [26, 31]. There are many researchers who argue that such productivity paradox may be attributed to, among other things, the inappropriate use of IT evaluation methodologies (e.g., [29]) and, moreover, it is unclear whether the ability to evaluate IT investments in EC has something to do with the organizations' levels of IT maturity [H]. There are two types of methodologies that organizations need to undertake in order to ensure that IT investments in EC are properly planned, evaluated, and monitored, and that expected benefits are eventually realized. An IT investment evaluation methodology is concerned with making investment decisions about IT projects [2]. In other words, the domain of concern is more about selecting the project or projects that at the outset seem to offer the greatest returns or benefits for the outlay. On the other hand, an IT benefits realization methodology can be seen to extend investment evaluation further into the project life cycle by ensuring expected benefits are realized once a decision to invest has been taken [6]. This involves planning how and when benefits will be realized and deciding who will be responsible for achieving benefits as well as actually overseeing the realization of benefits [34]. Given the above analysis, it can be concluded that, in general, organizations that employ IT benefits realization methodologies would be likely to also employ IT investments evaluation methodologies but the converse would not necessarily be the case. Behind this assertion however, is a more fundamental observation concerned with the underlying IT maturity' of an organization in terms of its willingness and cultural capability to use formal or semi-formal processes explicitly as part of its decision-making. In other words, it will be asserted in this paper that organizations that are more mature in IT are more likely to display more willingness to use evaluation processes. Closely connected with this is this notion that it is possible to define and record an organization's IT maturity against some predefined benchmark or benchmarks and in so doing provide a basis for organizations to plan to towards greater IT maturity. … <s> BIB012 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <s> In this study, we examine two trainee reactions: ease of learning and ease of use and their relationships with task performance in the context of object-oriented systems development. We conducted an experiment involving over 300 subjects. From that pool 72 trainees that met all of the criteria were selected for analysis in a carefully controlled study. We found that ease of learning was strongly correlated to task performance whereas ease of use was not. The finding was unexpected; ease of learning and ease of use are two overlapping concepts while their effects on task performance are very different. We offer a theoretical explanation to the paradoxical finding and its implications to the improvement of training evaluation. <s> BIB013 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <s> In this paper, we draw on control theory to understand the conditions under which the use of agile practices is most effective in improving software project quality. Although agile development methodologies offer the potential of improving software development outcomes, limited research has examined how project managers can structure the software development environment to maximize the benefits of agile methodology use during a project. As a result, project managers have little guidance on how to manage teams who are using agile methodologies. Arguing that the most effective control modes are those that provide teams with autonomy in determining the methods for achieving project objectives, we propose hypotheses related to the interaction between control modes, agile methodology use, and requirements change. We test the model in a field study of 862 software developers in 110 teams. The model explains substantial variance in four objective measures of project quality---bug severity, component complexity, coordinative complexity, and dynamic complexity. Results largely support our hypotheses, highlighting the interplay between project control, agile methodology use, and requirements change. The findings contribute to extant literature by integrating control theory into the growing literature on agile methodology use and by identifying specific contingencies affecting the efficacy of different control modes. We discuss the theoretical and practical implications of our results. <s> BIB014 </s> Understanding acceptance of information system development and management methodologies by actual users: A review and assessment of existing literature <s> RESULTS AND FUTURE RESEARCH OPPORTUNITIES 4.1 Critical Review <s> The paper presents an approach for evaluation of software development methodologies (SDM) that considers the aspects of a SDM's social adoption and technical efficiency. It builds on existing evaluation models used in the field of SDM. Case study approach was used to validate the model in four software development organisations. In all four cases the management confirmed that the model provided valuable new insights into adoption and efficiency of the companies' SDM. <s> BIB015
In general, while development of methodologies has been widely researched, there has been little research on the determinants of individual intentions to use methodologies in the more general context of ISDM methodologies. A number of studies suggest that the use of methodologies is limited in practice, and thateven when they are used -are not literally applied. This signals a fundamental flaw in methodology engineering. Other authors go so far as to suggest that methodologies are useful to beginners, rather than to experienced individuals BIB008 . A number of studies have attempted to understand the adoption of methodologies by organisations, using organisations as their unit of analysis (for e.g. BIB012 BIB005  BIB001 ). While these studies shed light on the important organisational-level decision to adopt software development innovations, they do not focus on the individuallevel determinants of intentions. Others study the effects of using a methodology on project success or task performance (for e.g.  BIB013 BIB014 ). On the whole, while there is abundant software engineering research on development of particular methodologies (for e.g. BIB015 ), studies that examine the determinants of methodology use and success at an individual level, considering not only ISD but also ISM methodologies, are scarce BIB007 . A plethora of research projects address the use of certain tools and techniques/methods  BIB004 BIB003 BIB002 BIB006 that may form part of a methodology. Some studies regard adoption merely as intention to use and do not study the actual use of the methodology (for e.g. BIB009 , BIB011 , BIB010 ). In the following subsections we provide an overview of the specific studies related to the research topic at hand.