Adoption of Design Thinking, Agile Software Development and Co-creation: A Qualitative Study towards Digital Banking Innovation Success

Digitalization in the financial sector challenges banking institutions to develop new methods of innovation processes by incorporating current concepts such as design thinking (DT), agile software development (ASD), and cocreation. This qualitative study is based on empirical research conducted at three Indonesian banks. Semi-structured interviews with three IT executives and a questioner of 31 middle managers participating in digital banking efforts were used to gather data. A Systematic Literature Review based on Kitchenheim processes generates keywords in the VOS Viewer software. NVIVO 12 qualitative software is employed to aid data analysis for illustrating the process integration. The research's contribution is identified, including process integration, obstacles, potential solutions, and enhanced framework on adopting DT, ASD, and Co-creation. Keywords— design thinking, agile software development, co-creation, Innovation

FAILURES PREDICTION APPROACH IN AGILE SOFTWARE DEVELOPMENT

Software failure prediction is an important activity during agile software development as it can help managers to identify the failure modules. Thus, it can reduce the test time, cost and assign testing resources efficiently. RapidMiner Studio9.4 has been used to perform all the required steps from preparing the primary data to visualizing the results and evaluating the outputs, as well as verifying and improving them in a unified environment. Two datasets are used in this work, the results for the first one indicate that the percentage of failure to predict the time used in the test is for all 181 rows, for all test times recorded, is 3% for Mean time between failures (MTBF). Whereas, SVM achieved a 97% success in predicting compared to previous work whose results indicated that the use of Administrative Delay Time (ADT) achieved a statistically significant overall success rate of 93.5%. At the same time, the second dataset result indicates that the percentage of failure to predict the time used is 1.5% for MTBF, SVM achieved 98.5% prediction.

Security Assurance in Agile Software Development Methods

Agile software development was introduced in the beginning of the 2000s to increase the visibility and efficiency software projects. Since then it has become as an industry standard. However, fitting sequential security engineering development models into iterative and incremental development practices in agile methods has caused difficulties in defining, implementing, and verifying the security properties of software. In addition, agile methods have also been criticized for decreased quality of documentation, resulting in decreased security assurance necessary for regulative purposes and security measurement. As a consequence, lack of security assurance can complicate security incident management, thus increasing the software's potential lifetime cost. This chapter clarifies the requirements for software security assurance by using an evaluation framework to analyze the compatibility of established agile security development methods: XP, Scrum, and Kanban. The results show that the agile methods are not inherently incompatible with security engineering requirements.

The Role of Neural Networks and Metaheuristics in Agile Software Development Effort Estimation

In any software development, accurate estimation of resources is one of the crucial tasks that leads to a successful project development. A lot of work has been done in estimation of effort in traditional software development. But, work on estimation of effort for agile software development is very scant. This paper provides an effort estimation technique for agile software development using artificial neural networks (ANN) and a metaheuristic technique. The artificial neural networks used are radial basis function neural network (RBFN) and functional link artificial neural network (FLANN). The metaheuristic technique used is whale optimization algorithm (WOA), which is a nature-inspired metaheuristic technique. The proposed techniques FLANN-WOA and RBFN-WOA are evaluated on three agile datasets, and it is found that these neural network models performed extremely well with the metaheuristic technique used. This is further empirically validated using non-parametric statistical tests.

Cloud Enhances Agile Software Development

The software industries follow some patterns (i.e., process model to develop any software product). Agile methodology is the most famous and used process model. It is a trend to develop efficient software products with high client satisfaction. In this chapter, the authors discuss agile methodology and its components, benefits, and drawbacks while using the cloud computing in agile software development, existing frameworks for agile-cloud combination, and some security measures.

Threat Modeling in Agile Software Development

Threat modeling is a way to get an overview of possible attacks against your systems. The advantages of threat modeling include tackling security problems early, improved risk assessments, and more effective security testing. There will always be limited resources available for security, and threat modeling will allow you to focus on the most important areas first. There is no one single “correct” way of doing threat modeling, and “agile” is no excuse for not doing it. This chapter describes the authors' experiences with doing threat modeling with agile development organizations, outlining challenges to be faced and pitfalls to be avoided.

Traditional or Agile Contracting for Software Development

As the use of software is present in so many activities today, it is important for business in particular to be aware of challenges that may seem different today than before the prevalence of software in our lives. Agile project management is one example: this more recent and nimble approach to software development presents its own challenges. Fortunately, the guiding legal principles related to traditional contract formation and execution are based in principles of fairness and equity, making the customization of legal principles to Agile contracting a reasonable endeavor. This chapter presents basic contract law and such law as it more specifically relates to contracts dealing with Agile software development.