The influence of organizational culture on the adoption of extreme programming

The adoption of extreme programming (XP) method requires a very peculiar cultural context in software development companies. However, stakeholders do not always consider this matter and tend to stand to technical requirements of the method. Hence this paper aims at identifying aspects of organizational culture that may influence favorably or unfavorably the use of XP. In order to identify those aspects, this study analyzes dimensions of organizational culture under the perspective of practices and values of XP. This paper is based on the review of the literature of the area and empirical observations carried out with six software companies. This study does not intend to develop a tool for measurement of XP’s compatibility with the organizational culture of each company. It intends to provide parameters (favorable and unfavorable aspects) for previous consideration of the convenience of XP implementation.     

Individual empowerment of agile and non-agile software developers in small teams

ContextEmpowerment of employees at work has been known to have a positive impact on job motivation and satisfaction. Software development is a field of knowledge work wherein one should also expect to see these effects, and the idea of empowerment has become particularly visible in agile methodologies, in which proponents emphasise team empowerment and individual control of the work activities as a central concern.ObjectiveThis research aims to get a better understanding of how empowerment is enabled in software development teams, both agile and non-agile, to identify differences in empowering practices and levels of individual empowerment.MethodTwenty-five interviews with agile and non-agile developers from Norway and Canada on decision making and empowerment are analysed. The analysis is conducted using a conceptual model with categories for involvement, structural empowerment and psychological empowerment.ResultsBoth kinds of development organisations are highly empowered and they are similar in most aspects relating to empowerment. However, there is a distinction in the sense that agile developers have more possibilities to select work tasks and influence the priorities in a development project due to team empowerment. Agile developers seem to put a higher emphasis on the value of information in decision making, and have more prescribed activities to enable low-cost information flow. More power is obtained through the achievement of managing roles for the non-agile developers who show interest and are rich in initiatives.ConclusionAgile developers have a higher sense of being able to impact the organisation than non-agile developers and have information channels that is significantly differently from non-agile developers. For non-agile teams, higher empowerment can be obtained by systematically applying low-cost participative decision making practices in the manager–developer relation and among peer developers. For agile teams, it is essential to more rigorously follow the empowering practices already established.     

Acceptance of agile methodologies: A critical review and conceptual framework

It is widely believed that systems development methodologies (SDMs) can help improve the software development process. Nevertheless, their deployment often encounters resistance from systems developers. Agile methodologies, the latest batch of SDMs that are most suitable in dealing with volatile business requirements, are likely to face the same challenge as they require developers to drastically change their work habits and acquire new skills. This paper addresses what can be done to overcome the challenge to agile methodologies acceptance. We provide a critical review of the extant literature on the acceptance of traditional SDMs and agile methodologies, and develop a conceptual framework for agile methodologies acceptance based on a knowledge management perspective. This framework can provide guidance for future research into acceptance of agile methodologies, and has implications for practitioners concerned with the effective deployment of agile methodologies.     

Harnessing agile concepts for the development of Intelligent Systems

Traditional and current approaches to intelligent systems design, have led to the creation of sophisticated and computationally-intensive packages and environments, for a wide range of applications. This paper proposes methods with which to extend the functionality of such systems, borrowing knowledge management concepts from the field of Agile Manufacturing. As such, this paper proposes that the future of intelligent systems design should be based not only upon the continuing development of artificial intelligence techniques, but also effective methods for harnessing human skills and core competencies to achieve these aims. Amir M. Sharif: He obtained his BEng (Hons) in Aeronautical Engineering from City University (London) in 1994 and is a research student in the Department of Information Systems and Computing, Brunel University (UK) currently completing his Ph.D in artificial intelligence. Amir maitains close links with both industry and academia and research interests include Evolutionary and Knowledge Based Systems, IT/IS investment evaluation, Information Management and E-commerce/Supply Chain Management. He has published in internationally refereed journals and spoken at conferences world-wide and is a member of numerours computer science-related journal and conference program committee boards. He is an Associate Member of the Institute of Electrical Engineers (AMIEE) and also has student membership of the Association for Computing Machinery (ACM) and Institute of Electrical and Electronic Engineers.     

Agile methods rapidly replacing traditional methods at Nokia: A survey of opinions on agile transformation

Context

Many organizations have started to deploy agile methods, but so far there exist only a few studies on organization-wide transformations. Are agile methods here to stay? Some claim that agile software development methods are in the mainstream adoption phase in the software industry, while others hope that those are a passing fad. The assumption here is that if agile would not provide real improvement, adopters would be eager at first but turn pessimistic after putting it into practice.

Objective

Despite the growing amount of anecdotal evidence on the success of agile methods across a wide range of different real-life development settings, scientific studies remain scarce. Even less is known about the perception of the impacts of agile transformation when it is deployed in a very large software development environment, and whether agile methods are here to stay. This study aims to fill that gap by providing evidence from a large-scale agile transformation within Nokia. While we have yet to confirm these findings with solid quantitative data, we believe that the perception of the impacts already pinpoints the direction of the impacts of large-scale agile transformation.

Method

The data were collected using a questionnaire. The population of the study contains more than 1000 respondents in seven different countries in Europe, North America, and Asia.

Results

The results reveal that most respondents agree on all accounts with the generally claimed benefits of agile methods. These benefits include higher satisfaction, a feeling of effectiveness, increased quality and transparency, increased autonomy and happiness, and earlier detection of defects. Finally, 60% of respondents would not like to return to the old way of working.

Conclusion

While the perception of the impact of agile methods is predominantly positive, several challenge areas were discovered. However, based on this study, agile methods are here to stay.     

A survey on the methods and tools of concurrent new product development and agile manufacturing

Companies in either manufacturing or servicing have to be restructured or re-organized in order to overcome with challenges of the 21st century in which customers are not only satisfied but also delighted. In this competitive environment, organizations should use a flexible, adaptive and responsive paradigm that can be entitled by a unique term: agile manufacturing (AM). An AM system is able to develop a variety of product at low cost and in a short time period. For this, it has some of useful enabling technologies and physical tools. Among these, concurrent engineering (CE) is a systematic approach to the integrated, concurrent design of product and their related processes, including manufacture and support. It is then a useful and beneficial approach to reduce the development time and manufacturing cost, while simultaneously improving the quality of a product in order to better respond to the customer expectations. The aim of this study is to underline the synergistic impact of new product development (NPD) and CE, (which can be called CNPD), and to survey their methods and tools in association with the AM.     

The impact of agile practices on communication in software development

Agile software development practices such as eXtreme Programming (XP) and SCRUM have increasingly been adopted to respond to the challenges of volatile business environments, where the markets and technologies evolve rapidly and present the unexpected. In spite of the encouraging results so far, little is known about how agile practices affect communication. This article presents the results from a study which examined the impact of XP and SCRUM practices on communication within software development teams and within the focal organization. The research was carried out as a case study in F-Secure where two agile software development projects were compared from the communication perspective. The goal of the study is to increase the understanding of communication in the context of agile software development: internally among the developers and project leaders and in the interface between the development team and stakeholders (i.e. customers, testers, other development teams). The study shows that agile practices improve both informal and formal communication. However, it further indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication. The study highlights the fact that hurdles and improvements in the communication process can both affect the feature requirements and task subtask dependencies as described in coordination theory. While the use of SCRUM and some XP practices facilitate team and organizational communication of the dependencies between product features and working tasks, the use of agile practices requires that the team and organization use also additional plan-driven practices to ensure the efficiency of external communication between all the actors of software development.

Drivers of agile software development use: Dialectic interplay between benefits and hindrances

Context

Agile software development with its emphasis on producing working code through frequent releases, extensive client interactions and iterative development has emerged as an alternative to traditional plan-based software development methods. While a number of case studies have provided insights into the use and consequences of agile, few empirical studies have examined the factors that drive the adoption and use of agile.

Objective

We draw on intention-based theories and a dialectic perspective to identify factors driving the use of agile practices among adopters of this software development methodology.

Method

Data for the study was gathered through an anonymous online survey of software development professionals. We requested participation from members of a selected list of online discussion groups, and received 98 responses.

Results

Our analyses reveal that subjective norm and training play a significant role in influencing software developers’ use of agile processes and methods, while perceived benefits and perceived limitations are not primary drivers of agile use among adopters. Interestingly, perceived benefit emerges as a significant predictor of agile use only if adopters face hindrances to their agile practices.

Conclusion

We conclude that research in the adoption of software development innovations should examine the effects of both enabling and detracting factors and the interactions between them. Since training, subjective norm, and the interplay between perceived benefits and perceived hindrances appear to be key factors influencing the adoption of agile methods, researchers can focus on how to (a) perform training on agile methods more effectively, (b) facilitate the dialog between developers and managers about perceived benefits and hindrances, and (c) capitalize on subjective norm to publicize the benefits of agile methods within an organization. Further, when managing the transition to new software development methods, we recommend that practitioners adapt their strategies and tactics contingent on the extent of perceived hindrances to the change.     

A framework to support the evaluation, adoption and improvement of agile methods in practice

Agile methods are often seen as providing ways to avoid overheads typically perceived as being imposed by traditional software development environments. However, few organizations are psychologically or technically able to take on an agile approach rapidly and effectively. Here, we describe a number of approaches to assist in such a transition. The Agile Software Solution Framework (ASSF) provides an overall context for the exploration of agile methods, knowledge and governance and contains an Agile Toolkit for quantifying part of the agile process. These link to the business aspects of software development so that the business value and agile process are well aligned. Finally, we describe how these theories are applied in practice with two industry case studies using the Agile Adoption and Improvement Model (AAIM).     

The mediating effect of organizational culture and knowledge sharing on transformational leadership and Enterprise Resource Planning systems success: An empirical study in China

Senior leadership has been identified as a critical factor in fostering Enterprise Resource Planning (ERP) systems success, however, the specific impact mechanism of transformational leadership on ERP success is still largely unknown. Based on organizational culture theory and knowledge based view, this study developed a theoretical model to explore the mediating effect of organizational culture and knowledge sharing on transformational leadership and ERP success. Data was collected from 115 IS executives and 413 ERP end users in 115 organizations in China. Partial Least Squares (PLS) analysis results suggest that transformational leadership is directly related with all the four types of organizational culture – development culture, group culture, hierarchical culture and rational culture, and is indirectly related with knowledge sharing and ERP success. Specifically, development culture has direct impact on ERP success, while hierarchical culture, group and rational culture are indirectly related with ERP success, mediated by explicit and tacit knowledge sharing. The research findings can provide guidelines for the top executives to facilitate appropriate organizational culture, so as to foster ERP knowledge sharing and achieve business benefits with the assimilation of ERP systems.     

Development and validation of an instrument to measure organizational cultures’ support of Business Process Management

The purpose of Business Process Management (BPM) is to increase the efficiency and effectiveness of organizational processes through improvement and innovation. Despite a common understanding that culture is an important element in BPM efforts, there is a dearth of theoretical and empirical research on culture as a facilitator of successful BPM. We develop the BPM culture construct and propose a validated instrument with which to measure organizational cultures’ support of BPM. The operationalization of the BPM culture concept provides a theoretical foundation for future research and a tool to assist organizations in developing a cultural environment that supports successful BPM.     

Team-based work and work system balance in the context of agile manufacturing

Manufacturing agility is the ability to prosper in an environment characterized by constant and unpredictable change. The purpose of this paper is to analyze team attributes necessary to facilitate agile manufacturing, and using Balance Theory as a framework, it evaluates the potential positive and negative impacts related to these team attributes that could alter the balance of work system elements and resulting "stress load" experienced by persons working on agile teams. Teams operating within the context of agile manufacturing are characterized as multifunctional, dynamic, cooperative, and virtual. A review of the literature relevant to each of these attributes is provided, as well as suggestions for future research.     

Perceptions and use of electronic media: Testing the relationship between organizational interpretation differences and media richness

How do managers perceive and use media? Media richness theory (MRT) appears to provide persuasive answers to this, but does it work when electronic media is used? Surveys of Japanese managers showed that the perceptions of media, including electronic media, did not contradict MRT. But, even so, the use of rich media was found to be influenced more strongly by whether the media was traditional or electronic, with respect to organizational interpretation of its environment. The perception and use of electronic media may not correspond, though they have generally been assumed to do so.     

A comparison of issues and advantages in agile and incremental development between state of the art and an industrial case

Recent empirical studies have been conducted identifying a number of issues and advantages of incremental and agile methods. However, the majority of studies focused on one model (Extreme Programming) and small projects. To draw more general conclusions we conduct a case study in large-scale development identifying issues and advantages, and compare the results with previous empirical studies on the topic. The principle results are that (1) the case study and literature agree on the benefits while new issues arise when using agile in large-scale and (2) an empirical research framework is needed to make agile studies comparable.     

The relationships between organizational and individual variables to on-the-job driver accidents and accident-free kilometres

Highway fatalities are the leading cause of fatal work injuries in the US, accounting for approximately 1 in 4 of the 5900 job-related deaths during 2001. The present study focused on the contribution of organizational factors and driver behaviours to on-the-job driving accidents in a large Western Canadian corporation. A structural equation modelling (SEM) approach was used which allows researchers to test a complex set of relationships within a global theoretical framework. A number of scales were used to assess organizational support, driver errors, and driver behaviours. The sample of professional drivers that participated allowed the recording of on-the-job accidents and accident-free kilometres from their personnel files. The pattern of relationships in the fitted model, after controlling for exposure and social desirability, provides insight into the role of organizational support, planning, environment adaptations, fatigue, speed, errors and moving citations to on-the-job accidents and accident-free kilometres. For example, organizational support affected the capacity to plan. Time to plan work-related driving was found to predict accidents, fatigue and adaptations to the environment. Other interesting model paths, SEM limitations, future research and recommendations are elaborated.     

The interaction between the use of information technology and organizational culture

Abstract

The interaction between the use of information technology, (IT) in organizations and that organization's culture is examined. The interaction is considered from the early stages of specification through to the regular use of the systems. The changes in the technological artefacts which result from the use of IT are discussed. Some suggestions about control of the interaction are made.     

The interaction between the use of information technology and organizational culture

The interaction between the use of information technology, (IT) in organizations and that organization's culture is examined. The interaction is considered from the early stages of specification through to the regular use of the systems. The changes in the technological artefacts which result from the use of IT are discussed. Some suggestions about control of the interaction are made.     

Supporting continuous learning in a large organization: the role of group and organizational perspectives

Many organizations recognize the need to continuously adapt and learn in order to survive and remain competitive. Learning and therefore change in organizations is driven in two ways. First, there is strategically driven learning, motivated by high-level factors such as market changes, company mergers and newly emerging approaches to organizational management and workplace learning. These changes reveal themselves in the introduction of new training programmes, recruitment strategies and knowledge management methodologies. Second, there is local, continuous learning occurring from the ground up. This is revealed as workers become more adept at their job through experience and collaboration with colleagues. Continuous learning is more gradual and requires local autonomy. This paper describes an experiment in supporting local, continuous learning, and its dissemination, but driven by a strategic initiative of the organization. This work raised many issues concerning the difficulty of integrating local and global organizational influences on learning. We outline lessons learned and suggestions as to the extent to which it is possible to align continuous learning with a company-wide perspective.     

Combining series elastic actuation and magneto-rheological damping for the control of agile locomotion

All-terrain robot locomotion is an active topic of research. Search and rescue maneuvers and exploratory missions could benefit from robots with the abilities of real animals. However, technological barriers exist to ultimately achieving the actuation system, which is able to meet the exigent requirements of these robots. This paper describes the locomotion control of a leg prototype, designed and developed to make a quadruped walk dynamically while exhibiting compliant interaction with the environment. The actuation system of the leg is based on the hybrid use of series elasticity and magneto-rheological dampers, which provide variable compliance for natural-looking motion and improved interaction with the ground. The locomotion control architecture has been proposed to exploit natural leg dynamics in order to improve energy efficiency. Results show that the controller achieves a significant reduction in energy consumption during the leg swing phase thanks to the exploitation of inherent leg dynamics. Added to this, experiments with the real leg prototype show that the combined use of series elasticity and magneto-rheological damping at the knee provide a 20 % reduction in the energy wasted in braking the knee during its extension in the leg stance phase.