Enterprise Experience into the Integration of Human-Centered Design and Kanban

he integration of Human-Centered Design (HCD) and Agile Software Development (ASD) promises the development of competitive products comprising a good User Experience (UX). This study has investigated the integration of HCD and Kanban with the aim to gain industrial experiences in a real world context. A case study showed that requirements flow into the development process in a structured manner by adding a design board. To this end, the transparency concerning recurring requirements increased. We contribute to the body of knowledge of software development by providing practical insights into Human-Centered Agile Development (HCAD). On one hand, it is shown that the integration of HCD and Kanban leads to a product with a good UX and makes the development process more human-centered. On the other hand, we conclude that a cross-functional collaboration speeds up product development.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2015-71938-RED

Agile Requirements Engineering: A systematic literature review

Nowadays, Agile Software Development (ASD) is used to cope with increasing complexity in system development. Hybrid development models, with the integration of User-Centered Design (UCD), are applied with the aim to deliver competitive products with a suitable User Experience (UX). Therefore, stakeholder and user involvement during Requirements Engineering (RE) are essential in order to establish a collaborative environment with constant feedback loops. The aim of this study is to capture the current state of the art of the literature related to Agile RE with focus on stakeholder and user involvement. In particular, we investigate what approaches exist to involve stakeholder in the process, which methodologies are commonly used to present the user perspective and how requirements management is been carried out. We conduct a Systematic Literature Review (SLR) with an extensive quality assessment of the included studies. We identified 27 relevant papers. After analyzing them in detail, we derive deep insights to the following aspects of Agile RE: stakeholder and user involvement, data gathering, user perspective, integrated methodologies, shared understanding, artifacts, documentation and Non-Functional Requirements (NFR). Agile RE is a complex research field with cross-functional influences. This study will contribute to the software development body of knowledge by assessing the involvement of stakeholder and user in Agile RE, providing methodologies that make ASD more human-centric and giving an overview of requirements management in ASD.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2015-71938-RED

Identifying Agile Requirements Engineering Patterns in Industry

Agile Software Development (ASD) is gaining in popularity in today´s business world. Industry is adopting agile methodologies both to accelerate value delivery and to enhance the ability to deal with changing requirements. However, ASD has a great impact on how Requirements Engineering (RE) is carried out in agile environments. The integration of Human-Centered Design (HCD) plays an important role due to the focus on user and stakeholder involvement. To this end, we aim to introduce agile RE patterns as main objective of this paper. On the one hand, we will describe our pattern mining process based on empirical research in literature and industry. On the other hand, we will discuss our results and provide two examples of agile RE patterns. In sum, the pattern mining process identifies 41 agile RE patterns. The accumulated knowledge will be shared by means of a web application.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2016-76956-C3-2-RMinisterio de Economía y Competitividad TIN2015-71938-RED

A Hybrid Approach Using RUP and Scrum as a Software Development Strategy

According to some researchers, a hybrid approach can help optimize the software development lifecycle by combining two or more methodologies. RUP and Scrum are two methodologies that successfully complement each other to improve the software development process. However, the literature has shown only few case studies on exactly how organizations are successfully applying this hybrid methodology and the benefits and issues found during the process. To help fill this literature gap, the main purpose of this thesis is to describe the development of the Lobbyist Registration and Tracking System for the City of Jacksonville case study where a hybrid approach, that integrates RUP and Scrum, was implemented to develop a major application to provide additional empirical evidence and enrich the knowledge in this under-investigated field. The objective of this research was fulfilled since the case study was described in detail with the specific processes implemented using RUP and Scrum within the context of the IBM Rational Collaborative Lifecycle Management Solution. The results may help researchers and practitioners who are looking for evidence about conducting a hybrid approach. However, more case studies that successfully combine RUP and Scrum need to be developed in order to have enough empirical evidence

A Software Development Process for Freshman Undergraduate Students

This conceptual paper presents work which is part of an ongoing research project into the design of a software development process aimed at freshman, undergraduate computing students. The process of how to plan and develop a solution is a topic that is addressed very lightly in many freshman, undergraduate courses which can leave novices open to developing habit-forming, maladaptive cognitive practices. The conceptual software development process described in this paper has a learning process at its core which centres on declarative knowledge (in the form of threshold concepts) and procedural knowledge (in the form of computational thinking skills) scaffolding freshman software development from initial planning through to final solution. The process - known as Computational Analysis and Design Engineered Thinking (CADET) - aims to support the structured development of both software and student self-efficacy

Carving out new business models in a small company through contextual ambidexterity: the case of a sustainable company

Business model innovation (BMI) and organizational ambidexterity have been pointed out as mechanisms for companies achieving sustainability. However, especially considering small and medium enterprises (SMEs), there is a lack of studies demonstrating how to combine these mechanisms. Tackling such a gap, this study seeks to understand how SMEs can ambidextrously manage BMI. Our aim is to provide a practical artifact, accessible to SMEs, to operationalize BMI through organizational ambidexterity. To this end, we conducted our study under the design science research to, first, build an artifact for operationalizing contextual ambidexterity for business model innovation. Then, we used an in-depth case study with a vegan fashion small e-commerce to evaluate the practical outcomes of the artifact. Our findings show that the company improves its business model while, at the same time, designs a new business model and monetizes it. Thus, our approach was able to take the first steps in the direction of operationalizing contextual ambidexterity for business model innovation in small and medium enterprises, democratizing the concept. We contribute to theory by connecting different literature strands and to practice by creating an artifact to assist managemen

User experience design and agile development : integration as an on-going achievement in practice

This research investigates how Agile development is combined with User Experience (UX) design. Agile development and UX design have roots in different disciplines and practitioners have to reconcile their perspectives on developing software if they are to work together. To date, there has been no sustained academic study on how Agile developers and UX designers work together in practical settings on a day-to-day basis. The ethnographically-informed research in this dissertation consists of three studies of teams in organisational settings, combined with an analysis of accounts of Agile development and UX design practice found in the literature. Together, they provide evidence for the complex, multifaceted nature of the work that integrates Agile development with UX design. The studies of day-to-day practice conducted for this research, found the work of the Agile developers and UX designers to be localised, contingent and purposeful. Agile devolopment and UX design integration, as it was achieved in the teams studied, was negotiated and achieved on a day-to-day basis between the developers and designers. The findings from the analysis of accounts of practice from the literature show that integration is achieved with the right tools, techniques and processes that coordinate between the tasks of the developers and designers and establish a focus on usability and on releasing working software. However, the accounts contain little and conflicting evidence for what constitutes the day-to-day work of Agile developers and UX designers in practical settings and as a result the utility of tools, techniques and processes for practice is not clear. Informed by the findings from the accounts in the literature and the studies of practice, five facets emerged as integral to an understanding of how the integration of Agile development and UX design is an on-going achievement in practice. These facets are (1) focus and coordination, (2) mutual awareness, (3) expectations about acceptable behaviour, (4) negotiating progress and (5) engaging with each other. The extent to which these facets enable integration, depend on contextual values concerning the combination of Agile development and UX design endorsed in the organisation. These findings serve to establish conditions which can constrain and enable Agile developers and UX designers in their integration work, while being sympathetic to the values embedded in the settings in which they work

How is the innovation process developed in traditional companies by combining the plan-oriented and flexible process models, and in which situations is it utilized?

This paper analyzes how the innovation process is developed in traditional companies by combining the plan-oriented and flexible process models, and in which situations it is utilized. To answer the research question, a multiple case study was selected. This research compared three traditional manufacturing companies within the same industry with in-depth interviews, follow-up interviews, observations, and secondary research. Traditional manufacturing companies today have begun to focus more on innovations, even so, how they organize for innovation differ amongst the companies. Five out of the eight boundary conditions presented by Paluch et al., (2019), proved highly important for the traditional companies researched, but the findings revealed investment and time influence, strategic fit and willingness to change and mindset to be of equal importance for selecting the general Hybrid innovation process. Nevertheless, three separate situations were revealed to affect the development of the combined process in traditional manufacturing companies. These situations were then based on four out of nine conditions initially found through both expected and observed pattern matching during the analysis; investment, consumer preferences, managerial control, and approach to risk. The different combination of the conditions resulted in three situation-based approaches to the Hybrid process model: short-term incremental-, short-term radical- and long-term radical innovations. From a theoretical perspective, this study emphasizes a need for a combined process. When considering large traditional manufacturing companies’ approach to innovation and how the degree of leaning towards the Agile or Stage-Gate method, whilst still being a Hybrid process, highly varies based on the innovational situation related to time and radicality. From a practical perspective, the three combined processes developed through research can serve as a guideline for innovation managers and help simplify the practice for mutual understanding of how to organize the innovation process based on three separate situations