Agile Software Development Principles Research Articles

Perancangan Aplikasi Naviku untuk Memberikan Informasi Navigasi Kepada Tunanetra Menggunakan Metode Test Driven Development

Visually impaired is a term for someone who has lost or reduced the function of vision. People with visual disabilities often experience difficulties in daily activities, for example when walking or navigating. They need the help of others to help them go to a room or move from one place to another. Currently, existing navigation aids do not fully meet the needs of the blind. They still need the help of others to get detailed information about visual objects such as the layout of rooms in buildings, traffic signs, and vehicles. Based on these problems, an Android-based navigation application needed that utilizes Text-to-Speech (TTS) technology to help blind people navigate independently by utilizing navigation information provided by voice. In order to help the development process, applications are developed by adopting Agile Software Development principles using the Test Driven Development (TDD) method. The features developed begin with a test fail phase where the developer creates unit test code before the production code is implemented, then refactor the code, and tests afterward (test passes). The success status of the features being tested gets success status with a rate of 100% for all features. Then in the TTS test, testing was carried out with 2 TTS engines, namely Google TTS and Samsung TTS, the results showed that the Word Error Rate (WRE) of Google TTS was 2,86, lower than Samsung TTS which got 4,06.

Game-based Sprint retrospectives: multiple action research

In today’s fast-paced world of rapid technological change, software development teams need to constantly revise their work practices. Not surprisingly, regular reflection on how to become more effective is perceived as one of the most important principles of Agile Software Development. Nevertheless, running an effective and enjoyable retrospective meeting is still a challenge in real environments. As reported by several studies, the Sprint Retrospective is an agile practice most likely to be implemented improperly or sacrificed when teams perform under pressure to deliver. To facilitate the implementation of the practice, some agile coaches have proposed to set up retrospective meetings in the form of retrospective games. However, there has been little research-based evidence to support the positive effects of retrospective games. Our aim is to investigate whether the adoption of retrospective games can improve retrospective meetings in general and lead to positive societal outcomes. In this paper, we report on an Action Research project in which we implemented six retrospective games in six Scrum teams that had experienced common retrospective problems. The received feedback indicates that the approach helped the teams to mitigate many of the “accidental difficulties” pertaining to the Sprint Retrospective, such as lack of structure, dullness, too many complaints, or unequal participation and made the meetings more productive to some degree. Moreover, depending on their individual preferences, different participants perceived different games as having a positive impact on their communication, motivation-and-involvement, and/or creativity, even though there were others, less numerous, who had an opposite view. The advantages and disadvantages of each game as well as eight lessons learned are presented in the paper.

A framework for agile project management for the water industry in developing economies

Water project management in developing economies such as South Africa is subject to a number of challenges owing to not only water scarcity but also top-down bureaucracies; challenged information and communication technologies (ICTs); lack of agility; lack of top management support; lack of smart water management as embedded in the 4th Industrial Revolution; lack of customer education; and lack of general sustainability and competitive advantage. The researchers conducted a comprehensive literature review on water industry challenges aimed at eliciting how principles of agile software development may be adopted in the water industry of developing economies. A number of propositions were formulated from scholarly literature and a conceptual framework was developed on the strength of the propositions. The framework is analysed and validated theoretically. The paper concludes with directions for future research in this area.

OGITO, an Open Geospatial Interactive Tool to support collaborative spatial planning with a maptable

Maptables are increasingly used to support collaborative spatial planning processes. Despite the proven benefits and claimed potential of using a maptable in such processes, software applications specifically designed for this device are still scarce. Moreover, often-used applications do not fully exploit the touch functionality of a maptable, or have low usability. To address this gap, we developed and evaluated the Open Geospatial Interactive TOol (OGITO), an open-source software application designed to support collaborative spatial planning processes with a maptable. To develop such tool, we combined human-centred design and Agile software development principles in a co-design effort with intended users and stakeholders. Through iterative development cycles and feedback from users, OGITO was evolved until it satisfied user expectations. In a case study on community mapping in Sumatra, Indonesia, a sample of users evaluated OGITO's usability. Case study participants reported high satisfaction with this tool for the tasks and context given. Our research shows the added value of iterative development and user feedback for improving and further development of the tool's usability and functionality.

Implementation Science Meets Software Development to Create eHealth Components for an Integrated Care Model for Allogeneic Stem Cell Transplantation Facilitated by eHealth: The SMILe Study as an Example.

To describe a process of creating eHealth components for an integrated care model using an agile software development approach, user-centered design and, via the Behavior Change Wheel, behavior theory-guided content development. Following the principles of implementation science and using the SMILe project (integrated care model for allogeneic stem cell transplantation facilitated by eHealth) as an example, this study demonstrates how to narrow the research-to-practice gap often encountered in eHealth projects. We followed a four-step process: (a) formation of an interdisciplinary team; (b) a contextual analysis to drive the development process via behavioral theory; (c) transfer of content to software following agile software development principles; and (d) frequent stakeholder and end user involvement following user-centered design principles. Our newly developed comprehensive development approach allowed us to create a running eHealth component and embed it in an integrated care model. An interdisciplinary team's collaboration at specified interaction points supported clear, timely communication and interactions between the specialists. Because behavioral theory drove the content development process, we formulated user stories to define the software features, which were prioritized and iteratively developed using agile software development principles. A prototype intervention module has now been developed and received high ratings on the System Usability Scale after two rounds of usability testing. Following an agile software development process, structured collaboration between nursing scientists and software specialists allowed our interdisciplinary team to develop meaningful, theory-based eHealth components adapted to context-specific needs. The creation of high-quality, accurately fitting eHealth components specifically to be embedded in integrated care models should increase the chances of uptake, adoption, and sustainable implementation in clinical practice.

An Efficient DAGbM-KSJS Algorithm for Agile Software Testing

Agile software testing is a software testing practice that follows the principles of agile software development. In this paper, an optimal Agile software testing is performed using Directed Acyclic Graph-based Model (DAGbM). Initially, the suggested model pre-processes the test case dataset, then by deploying the Dependency Assessment for Use Case (DAUC) algorithm, the dependency between the uses of cases are determined. The K-Shingling based Jaccard Similarity (KSJS) algorithm estimates the similarity among every test cases and prioritizes the clustered test cases using Span Clustering based Prioritization (SCP) algorithm. After prioritizing the clustered test cases, the use cases are prioritized based on dependency. Finally, the minimum distance value is exploited for prioritizing the individual test cases. The performance of the suggested method is validated using parameters such as code average, failure rate, prioritization time, and percentage of defects detected. The validation results prove that when compared to the existing methods, the suggested method provides optimal results for all the parameters.

Achieving agility through BRIDGE process model: an approach to integrate the agile and disciplined software development

Despite of many criticisms, agile software development (Beck et al., Manifesto for Agile Software Development, http://agilemanifesto.org, [1]) philosophy has been proved to be quite successful to increase the project success rate up to a significant extent. The primary reasons behind the criticism of agile are the strong violation of the traditional disciplined software engineering theories, principles and practices. The goal of this research paper is to establish the fact that agility may also be achieved by following traditional process models especially with BRIDGE (Mandal, 2009 IEEE International Advance Computing Conference (IACC 2009) Patiala, India, [2]) process model. Hence, the aim of this paper is to integrate the agile and traditional disciplined software development process models and establish the compatibility between both the approaches. At the beginning, we have explored the objectives and principles of agile software development. Next, we briefly discussed the BRIDGE process model and further justified that--following BRIDGE process model, the philosophy of agile may also be achieved and conclude that BRIDGE model has both the capability of traditional software development process model as well as of the agile process.

Agile Principles and Achievement of Success in Software Development: A Quantitative Study in Brazilian Organizations

The principles of agile development emerge as potential solutions to numerous design problems of software development. In this context, this paper aims to identify and analyze the profile of Brazilian software producers regarding the use of agile principles and their potential to achieve success in producing software. This is a quantitative study made with professionals from the software industry. Data were collected through structured questionnaires and analyzed using technical descriptive analysis, factor analysis and cluster analysis. Based on the categorization of factors, three software organizations profiles have been obtained regarding the use of agile principles and the scope of success in producing software. The implications of this study are that organizations with the highest success rates in software are the same as those that have higher rates for capacity in terms of team, culture, communication with the client, environmental configuration and relationships with external partners. Organizations that used agile software development principles achieved success in software development, but it cannot be said that the use of agile principles alone can guarantee the achievement of such success in software development. Additionally, relationships with external partners, although not contemplated in the related studies investigated, was shown to be a critical factor for success in software development and, therefore, relevant to the agile software development field. In conclusion, this study is relevant because it helps to improve our understanding of the use of agile principles in the development of software and whether these principles are associated with obtaining success in software production; therefore, it explores a new factor that has not been observed previously.

Agile methods for software practice transformation

In a large-scale distributed complex software engineering environment, the ability to rapidly evaluate and improve software engineering practices can be a key market differentiator. Practices that shorten the development cycle, cost-effectively improve quality, and align software with customer needs can have a direct impact on the business value delivered by the enterprise. The IBM Quality Software Engineering (QSE) organization motivates and enables teams across IBM business units and geographies to adopt recommended software engineering practices. QSE has historically established communities and used well-known organizational change management principles to help teams adopt and use recommended practices. In 2008 and 2009, QSE discovered that blending well-known organizational change management principles with agile software development principles enables communities to more consistently deliver significant value to their members. QSE Communities use Scrum, which is an agile project management framework, to prioritize their work on the basis of the communities' needs, plan their work every two weeks and then deliver value at the end of every two-week Sprint (iteration), demonstrate results, and obtain feedback and continuously improve by reflecting and identifying improvement actions at the end of each Sprint. Combining Scrum with proven steps to organizational change management has allowed QSE to rapidly motivate and enable software engineering improvements across IBM.

Being Extreme in the Classroom: experiences Teaching XP

Agile Methods propose a new way of looking at software development that questions many of the beliefs of conventional Software Engineering. Agile methods such as Extreme Programming (XP) have been very effective in producing highquality software in realworld projects with strict time constraints. Nevertheless, most university courses and industrial training programs are still based on oldstyle heavy-weight methods. This article, based on our experiences teaching XP in academic and industrial environments, presents effective ways of teaching students and professionals on how to develop high-quality software following the principles of agile software development. We also discuss related work in the area, describe realworld cases, and discuss open problems not yet resolved.

Being Extreme in the classroom: Experiences teaching XP

AbstractAgile Methods propose a new way of looking at software development that questions many of the beliefs of conventional Software Engineering. Agile methods such as Extreme Programming (XP) have been very effective in producing high-quality software in real-world projects with strict time constraints.Nevertheless, most university courses and industrial training programs are still based on old-style heavyweight methods. This article, based on our experiences teaching XP in academic and industrial environments, presents effective ways of teaching students and professionals on how to develop high-quality software following the principles of agile software development. We also discuss related work in the area, describe real-world cases, and discuss open problems not yet resolved.