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

Crystallization of agility: Back to basics

There are a number of agile and traditional methodologies for software development. Agilists provide agile principles and agile values to characterize the agile methods but there is no clear and inclusive definition of agile methods; subsequently it is not feasible to draw a clear distinction between traditional and agile software development methods in practice. The purpose of this paper is to explain the concept of agility in detail; and then to suggest a definition of agile methods that would help in the ranking or differentiation of agile methods from other available methods

Improving agile software development by the application of method engineering practices

Despite the vast attention and wide acceptance of the newly engineered agile methods for software development, those methods are seldom linked to the goals of software process improvement (SPI), an approach that aims to provide support for significant improvement of both the quality of those methods as well as the resultant software products. In this paper, we propose an extension to agile methods by adding extra characteristics in order for agile methods to better support SPI. We explain how agile methods can gain those extra attributes through the application of a method engineering approach along with our new tool (4-DAT) that assists method engineers and managers in selecting the most appropriate method fragments for their needed agile methods. Finally, we summarize a number of industrial case studies carried out over several years in order to test and improve the efficiency of our theory of adding SPI to an agile methodological approach

Systematic Analysis of Safety and Security Risks in Smart Homes

The revolution in Internet of Things (IoT)-based devices and applications has provided smart applications for humans. These applications range from healthcare to traffic-flow management, to communication devices, to smart security devices, and many others. In particular, government and private organizations are showing significant interest in IoT-enabled applications for smart homes. Despite the perceived benefits and interest, human safety is also a key concern. This research is aimed at systematically analyzing the available literature on smart homes and identifying areas of concern or risk with a view to supporting the design of safe and secure smart homes. For this systematic review process, relevant work in the most highly regarded journals published in the period 2016-2020 (a section of 2020 is included)was analyzed. A final set of 99 relevant articles (journal articles, book sections, conference papers, and survey papers) was analyzed in this study. This analysis is focused on three research questions and relevant keywords. The systematic analysis results and key insights will help researchers and practitioners to make more informed decisions when dealing with the safety and security risks of smart homes, especially in emergency situations.This publication was supported by Qatar University Internal Grant No. IRCC-2020-009

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

Defining an integrated agile governance for large agile software development environments

This paper highlights the important aspect of IT governance, with the objective of defining an unaddressed aspect of agile governance, by the application of an iterative, inductive, instantaneous analysis and emergent interpretation of appropriate data-grounded conceptual categories of IT governance. An effective agile governance approach will facilitate the achievement of desired discipline, rationale, business value, improved performance, monitoring, as well as control of large agile software development environments by aligning business goals and agile software development goals. © Springer-Verlag Berlin Heidelberg 2007