A framework to assist in the assessment and tailoring of agile software development methods

University of Technology, Sydney. Faculty of Engineering and Information Technology.The innovative well-known agile methods offer many powerful agile software development practices and have received considerable attention from both practitioners as well as the research community. While many organizations are interested in adopting agile methods suitable to their local circumstances, there is little guidance available on how to do so. Organizations, especially on the large-scale, currently lack systematic support for adopting agile methods in their complex software development settings. To address this important issue, this research proposes an agile software solution framework (ASSF) to both assistance in the assessment of the capability of the organization or team and tailoring of agile method in order to support the systematic adoption and improvement of agility in both agile and, incidentally, non-agile software development environments - especially formal and large environments. The ASSF has been incrementally developed by the iterative application of build, review and adjust research activities, which is called here a “qualitative empirical” research method. The ASSF is intended for use by agile coaches and consultants as a comprehensive information guide. The ASSF has two main components: framework characteristics and lifecycle management. The framework characteristics component incorporates 10 main elements or attributes to describe the agile-hybrid software development methodologies: (1) people (2) process, (3) product, (4) tools, (5) agility, (6) abstraction, (7) business value, (8) policy (9) rules and (10) legal. The framework lifecycle management component specifies the stages, practices and resources in order to support the systematic adoption and improvement of agility. The framework stages refer to an agility adoption and improvement lifecycle, its practices refer to an agility adoption and improvement process, and its resources refer to models, templates and toolkit that can be used during the agility adoption and improvement process such as the contextual analysis model, a key agility indicators index, an agility adoption and improvement model, an agility adoption and improvement scorecard, and an agile toolkit. The components of this framework have been empirically analysed and reviewed by experts from industry as well as the research community, and updated based on the feedback received. The results of this research indicated that the proposed ASSF framework may be considered reasonable for a gradual successful transition or adoption of agile practices in formal and large software development environments

Naming the Pain in Requirements Engineering: A Design for a Global Family of Surveys and First Results from Germany

For many years, we have observed industry struggling in defining a high quality requirements engineering (RE) and researchers trying to understand industrial expectations and problems. Although we are investigating the discipline with a plethora of empirical studies, they still do not allow for empirical generalisations. To lay an empirical and externally valid foundation about the state of the practice in RE, we aim at a series of open and reproducible surveys that allow us to steer future research in a problem-driven manner. We designed a globally distributed family of surveys in joint collaborations with different researchers and completed the first run in Germany. The instrument is based on a theory in the form of a set of hypotheses inferred from our experiences and available studies. We test each hypothesis in our theory and identify further candidates to extend the theory by correlation and Grounded Theory analysis. In this article, we report on the design of the family of surveys, its underlying theory, and the full results obtained from Germany with participants from 58 companies. The results reveal, for example, a tendency to improve RE via internally defined qualitative methods rather than relying on normative approaches like CMMI. We also discovered various RE problems that are statistically significant in practice. For instance, we could corroborate communication flaws or moving targets as problems in practice. Our results are not yet fully representative but already give first insights into current practices and problems in RE, and they allow us to draw lessons learnt for future replications. Our results obtained from this first run in Germany make us confident that the survey design and instrument are well-suited to be replicated and, thereby, to create a generalisable empirical basis of RE in practice

Agile Manifesto and Practices Selection for Tailoring Software Development: A Systematic Literature Review

peer reviewedAgile methods have been largely used for many years to provide developers with a flexible software development process leading to software quality improvement. To get the best results and eliminate unnecessary efforts, the development team should select the most appropriate methods and techniques. The fundamental core of an agile method has to be well-understood before deciding which parts of the method need to be adopted. We believe that the quickest way to do so is to understand the prescripts of the Agile Manifesto. Many researches have proposed different tailoring approaches based on the relation and straight-forward interpretation between each agile practice and agile values or principles. We however have observed that agile practitioners do not dedicate the necessary attention to the Agile Manifesto before adopting agile methods or practices and directly use them. It is because the importance of Agile Manifesto in tailoring context is not obvious enough to the community. This study aims at doing a systematic literature review on the existing case studies, to verify the relation between the Agile Manifesto and agile practice selection

Digital support interventions for the self-management of low back pain: a systematic review

Background: Low back pain (LBP) is a common cause of disability and is ranked as the most burdensome health condition globally. Self-management, including components on increased knowledge, monitoring of symptoms, and physical activity, are consistently recommended in clinical guidelines as cost-effective strategies for LBP management and there is increasing interest in the potential role of digital health. Objective: The study aimed to synthesize and critically appraise published evidence concerning the use of interactive digital interventions to support self-management of LBP. The following specific questions were examined: (1) What are the key components of digital self-management interventions for LBP, including theoretical underpinnings? (2) What outcome measures have been used in randomized trials of digital self-management interventions in LBP and what effect, if any, did the intervention have on these? and (3) What specific characteristics or components, if any, of interventions appear to be associated with beneficial outcomes? Methods: Bibliographic databases searched from 2000 to March 2016 included Medline, Embase, CINAHL, PsycINFO, Cochrane Library, DoPHER and TRoPHI, Social Science Citation Index, and Science Citation Index. Reference and citation searching was also undertaken. Search strategy combined the following concepts: (1) back pain, (2) digital intervention, and (3) self-management. Only randomized controlled trial (RCT) protocols or completed RCTs involving adults with LBP published in peer-reviewed journals were included. Two reviewers independently screened titles and abstracts, full-text articles, extracted data, and assessed risk of bias using Cochrane risk of bias tool. An independent third reviewer adjudicated on disagreements. Data were synthesized narratively. Results: Of the total 7014 references identified, 11 were included, describing 9 studies: 6 completed RCTs and 3 protocols for future RCTs. The completed RCTs included a total of 2706 participants (range of 114-1343 participants per study) and varied considerably in the nature and delivery of the interventions, the duration/definition of LBP, the outcomes measured, and the effectiveness of the interventions. Participants were generally white, middle aged, and in 5 of 6 RCT reports, the majority were female and most reported educational level as time at college or higher. Only one study reported between-group differences in favor of the digital intervention. There was considerable variation in the extent of reporting the characteristics, components, and theories underpinning each intervention. None of the studies showed evidence of harm. Conclusions: The literature is extremely heterogeneous, making it difficult to understand what might work best, for whom, and in what circumstances. Participants were predominantly female, white, well educated, and middle aged, and thus the wider applicability of digital self-management interventions remains uncertain. No information on cost-effectiveness was reported. The evidence base for interactive digital interventions to support patient self-management of LBP remains weak

Examining perceptions of agility in software development practice

This is the post-print version of the final published article that is available from the link below. Copyright @ 2010 ACM.Organizations undertaking software development are often reminded that successful practice depends on a number of non-technical issues that are managerial, cultural and organizational in nature. These issues cover aspects from appropriate corporate structure, through software process development and standardization to effective collaborative practice. Since the articulation of the 'software crisis' in the late-1960s, significant effort has been put into addressing problems related to the cost, time and quality of software development via the application of systematic processes and management practices for software engineering. Early efforts resulted in prescriptive structured methods, which have evolved and expanded over time to embrace consortia/ company-led initiatives such as the Unified Modeling Language and the Unified Process alongside formal process improvement frameworks such as the International Standards Organization's 9000 series, the Capability Maturity Model and SPICE. More recently, the philosophy behind traditional plan-based initiatives has been questioned by the agile movement, which seeks to emphasize the human and craft aspects of software development over and above the engineering aspects. Agile practice is strongly collaborative in its outlook, favoring individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan (see Sidebar 1). Early experience reports on the use of agile practice suggest some success in dealing with the problems of the software crisis, and suggest that plan-based and agile practice are not mutually exclusive. Indeed, flexibility may arise from this unlikely marriage in an aim to strike a balance between the rigor of traditional plan-based approaches and the need for adaptation of those to suit particular development situations. With this in mind, this article surveys the current practice in software engineering alongside perceptions of senior development managers in relation to agile practice in order to understand the principles of agility that may be practiced implicitly and their effects on plan-based approach

Influential factors of aligning Spotify squads in mission-critical and offshore projects – a longitudinal embedded case study

Changing the development process of an organization is one of the toughest and riskiest decisions. This is particularly true if the known experiences and practices of the new considered ways of working are relative and subject to contextual assumptions. Spotify engineering culture is deemed as a new agile software development method which increasingly attracts large-scale organizations. The method relies on several small cross-functional self-organized teams (i.e., squads). The squad autonomy is a key driver in Spotify method, where a squad decides what to do and how to do it. To enable effective squad autonomy, each squad shall be aligned with a mission, strategy, short-term goals and other squads. Since a little known about Spotify method, there is a need to answer the question of: How can organizations work out and maintain the alignment to enable loosely coupled and tightly aligned squads? In this paper, we identify factors to support the alignment that is actually performed in practice but have never been discussed before in terms of Spotify method. We also present Spotify Tailoring by highlighting the modified and newly introduced processes to the method. Our work is based on a longitudinal embedded case study which was conducted in a real-world large-scale offshore software intensive organization that maintains mission-critical systems. According to the confidentiality agreement by the organization in question, we are not allowed to reveal a detailed description of the features of the explored project

Towards a Holistic Approach to Designing Theory-based Mobile Health Interventions

Increasing evidence has shown that theory-based health behavior change interventions are more effective than non-theory-based ones. However, only a few segments of relevant studies were theory-based, especially the studies conducted by non-psychology researchers. On the other hand, many mobile health interventions, even those based on the behavioral theories, may still fail in the absence of a user-centered design process. The gap between behavioral theories and user-centered design increases the difficulty of designing and implementing mobile health interventions. To bridge this gap, we propose a holistic approach to designing theory-based mobile health interventions built on the existing theories and frameworks of three categories: (1) behavioral theories (e.g., the Social Cognitive Theory, the Theory of Planned Behavior, and the Health Action Process Approach), (2) the technological models and frameworks (e.g., the Behavior Change Techniques, the Persuasive System Design and Behavior Change Support System, and the Just-in-Time Adaptive Interventions), and (3) the user-centered systematic approaches (e.g., the CeHRes Roadmap, the Wendel's Approach, and the IDEAS Model). This holistic approach provides researchers a lens to see the whole picture for developing mobile health interventions