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.

No abstract

Abstract

Purpose: Agile software development helps software producing organizations to respond to manifold challenges. While prior research focused on agility as a project or process phenomenon, we suggest that agility is an emergent phenomenon on the team level. Research approach: Using the theory of complex adaptive systems (CASs), we capture the multiple influencing levels of software development teams (SDTs) and their interplay with self-organization and emergence. We investigate three agile SDTs in different contextual environments that participate with four or more different roles each. Findings: 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. Research implications: Our theoretical contributions result from the development and test of theory-grounded propositions and the investigation of mature agile development teams. Practical implications: Our findings help practitioners to improve the cost-effectiveness ratio of their team's operations. Originality: 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.

To stay ahead of the competition, firms must continuously learn from their customers and swiftly adopt those lessons to improve their products. A unit at Ubisoft, a leading game publisher headquartered in Paris, has established a three-pronged approach to drive product innovation based on three practices: data-driven exploration, data-augmented ideation, and data-informed validation. By establishing processes and capabilities for these practices and blending them in a portfolio approach to product design, they maximize the value generation potential of the data at their disposal. Product development in a variety of industries can benefit from the lessons of these data-oriented innovation practices.