What makes organizations so similar? We contend that the engine of rationalization and bureaucratization has moved from the competitive marketplace to the state and the professions. Once a set of organizations emerges as a field, a paradox arises: rational actors make their organizations increasingly similar as they try to change them. We describe three isomorphic processes-coercive, mimetic, and normative—leading to this outcome. We then specify hypotheses about the impact of resource centralization and dependency, goal ambiguity and technical uncertainty, and professionalization and structuration on isomorphic change. Finally, we suggest implications for theories of organizations and social change.

The iron cage revisited: Institutional isomorphism and collective rationality in organizational fields (Chinese Translation)

Cultivating Communities of Practice: A Guide to Managing Knowledge

textPrior studies have emphasized that structural attributes are crucial to simultaneously pursuing exploration and exploitation, yet our understanding of antecedents of ambidexterity is still limited. Structural differentiation can help ambidextrous organizations to maintain multiple inconsistent and conflicting demands; however, differentiated exploratory and exploitative activities need to mobilized, coordinated, integrated, and applied. Based on this idea, we delineate formal and informal senior team integration mechanisms (i.e. contingency rewards and social integration) and formal and informal organizational integration mechanisms (i.e. cross-functional interfaces and connectedness) and examine how they mediate the relationship between structural differentiation and ambidexterity. Overall, our findings suggest that the previously asserted direct effect of structural differentiation on ambidexterity operates through informal senior team (i.e. senior team social integration) and formal organizational (i.e. cross-functional interfaces) integration mechanisms. Through this richer explanation and empirical assessment, we contribute to a greater clarity and better understanding of how organizations may effectively pursue exploration and exploitation simultaneously to achieve ambidexterity.

/pdf/structural-differentiation-and-ambidexterity-the-mediating-4tfwksgx8f.pdf

Structural Differentiation and Ambidexterity: The Mediating Role of Integration Mechanisms

The rise of motivational information systems: A review of gamification research

The Nature Of Emotion Fundamental Questions

ContextIn the last decade, software development has been characterized by two major approaches: agile software development, which aims to achieve increased velocity and flexibility during the development process, and user-centered design, which places the goals and needs of the system's end-users at the center of software development in order to deliver software with appropriate usability. Hybrid development models, referred to as user-centered agile software development (UCASD) in this article, propose to combine the merits of both approaches in order to design software that is both useful and usable. ObjectiveThis paper aims to capture the current state of the art in UCASD approaches and to derive generic principles from these approaches. More specifically, we investigate the following research question: Which principles constitute a user-centered agile software development approach? MethodWe conduct a systematic review of the literature on UCASD. Identified works are analyzed using a coding scheme that differentiates four levels of UCASD: the process, practices, people/social and technology dimensions. Through subsequent synthesis, we derive generic principles of UCASD. ResultsWe identified and analyzed 83 relevant publications. The analysis resulted in a comprehensive coding system and five principles for UCASD: (1) separate product discovery and product creation, (2) iterative and incremental design and development, (3) parallel interwoven creation tracks, (4) continuous stakeholder involvement, and (5) artifact-mediated communication. ConclusionOur paper contributes to the software development body of knowledge by (1) providing a broad overview of existing works in the area of UCASD, (2) deriving an analysis framework (in form a coding system) for works in this area, going beyond former classifications, and (3) identifying generic principles of UCASD and associating them with specific practices and processes.

Exploring principles of user-centered agile software development

Context Since its inception around 2010, gamification has become one of the top technology and software trends. However, gamification has also been regarded as one of the most challenging areas of software engineering. Beyond traditional software design requirements, designing gamification requires the command of disciplines such as (motivational/behavioral) psychology, game design, and narratology, making the development of gamified software a challenge for traditional software developers. Gamification software inhabits a finely tuned niche of software engineering that seeks for both high functionality and engagement; beyond technical flawlessness, gamification has to motivate and affect users. Consequently, it has also been projected that most gamified software is doomed to fail. Objective This paper seeks to advance the understanding of designing gamification and to provide a comprehensive method for developing gamified software. Method We approach the research problem via a design science research approach; firstly, by synthesizing the current body of literature on gamification design methods and by interviewing 25 gamification experts, producing a comprehensive list of design principles for developing gamified software. Secondly, and more importantly, we develop a detailed method for engineering of gamified software based on the gathered knowledge and design principles. Finally, we conduct an evaluation of the artifacts via interviews of ten gamification experts and implementation of the engineering method in a gamification project. Results As results of the study, we present the method and key design principles for engineering gamified software. Based on the empirical and expert evaluation, the developed method was deemed as comprehensive, implementable, complete, and useful. We deliver a comprehensive overview of gamification guidelines and shed novel insights into the nature of gamification development and design discourse. Conclusion This paper takes first steps towards a comprehensive method for gamified software engineering.

/pdf/how-to-design-gamification-a-method-for-engineering-gamified-4eycagd6ob.pdf

How to design gamification? A method for engineering gamified software

During recent years, gamification has become a popular method of enriching information technologies. Popular business analysts have made promising predictions about penetration of gamification, however, it has also been estimated that most gamifica-tion efforts will fail due to poor understanding of how gamification should be designed and implemented. Therefore, in this paper we seek to advance the understanding of best practices related to the gamifica-tion design process. We approach this research problem via a design science research approach; firstly, by synthesizing the current body of literature on gamification design methods and interviewing 25 gamification experts. Secondly, we develop a method for gamification design, based on the gathered knowledge. Finally, we conduct an evaluation of the method via interviews of 10 gamification experts. The results indicate that the developed method is comprehensive , complete and provides practical utility. We deliver a comprehensive overview of gamification guidelines and shed novel insights into the overall nature of the gamification development and design discourse.

/pdf/how-to-gamify-a-method-for-designing-gamification-2v6428edy4.pdf

How to Gamify? A Method For Designing Gamification

Agile software development helps software producing organizations to respond to manifold challenges. While prior research focused on agility as a project or process phenomenon, the authors suggest that agility is an emergent phenomenon on the team level. The paper aims to discuss this issue.,Using the theory of complex adaptive systems (CASs), the study captures the multiple influencing levels of software development teams (SDTs) and their interplay with self-organization and emergence. The authors investigate three agile SDTs in different contextual environments that participate with four or more different roles each.,The results suggest self-organization as a central process when understanding team agility. While contextual factors often provide restriction on self-organization, they can help the team to enhance its autonomy.,The theoretical contributions result from the development and test of theory grounded propositions and the investigation of mature agile development teams.,The findings help practitioners to improve the cost-effectiveness ratio of their team’s operations.,The study provides empirical evidence for the emergence of team agility in agile SDTs. Using the lens of CAS, the study suggests the importance of the team’s autonomy.

/pdf/explaining-the-emergence-of-team-agility-a-complex-adaptive-2nnnj5ap32.pdf

Explaining the emergence of team agility: a complex adaptive systems perspective

Software engineering researchers are increasingly interested in the role of emotion during software development. While general tools are available to extract emotions from textual data, these perform poorly in the domain of software engineering. Hence, this paper develops MEME - a Method for EMotion Extraction. Using GHtorrent and GitHub as data sources, the paper presents an implementation of the method. The evaluation results suggest a better performance of MEME in contrast to Syuzhet R package emotion analysis.

Karl Werder

Papers

Exploring principles of user-centered agile software development

How to design gamification? A method for engineering gamified software

How to Gamify? A Method For Designing Gamification

Explaining the emergence of team agility: a complex adaptive systems perspective

MEME: toward a method for emotions extraction from github