2,621 research outputs found

    Complementing Measurements and Real Options Concepts to Support Inter-iteration Decision-Making in Agile Projects

    Get PDF
    Agile software projects are characterized by iterative and incremental development, accommodation of changes and active customer participation. The process is driven by creating business value for the client, assuming that the client (i) is aware of it, and (ii) is capable to estimate the business value, associated with the separate features of the system to be implemented. This paper is focused on the complementary use of measurement techniques and concepts of real-option-analysis to assist clients in assessing and comparing alternative sets of requirements. Our overall objective is to provide systematic support to clients for the decision-making process on what to implement in each iteration. The design of our approach is justified by using empirical data, published earlier by other authors

    Roles and responsibilities in agile ICT for development

    Get PDF
    This paper examines the different roles in designing interactive software in a ICT for development context. Using experiences from a participatory action research project, in which we used agile methods to design and deploy an system to support ‘agricultural information flow’ for a co-operative of small farmers in rural India, we identify points of difference between the roles in standard descriptions of agile software methods and the roles as they emerged in our project. A key finding is the critical role played by a ‘Development Project Manager’ in facilitating dialogue, orchestrating the activities of other actors and in building the capabilities and confidence of all the participants in joint action

    An agile business process and practice meta-model

    Get PDF
    Business Process Management (BPM) encompasses the discovery, modelling, monitoring, analysis and improvement of business processes. Limitations of traditional BPM approaches in addressing changes in business requirements have resulted in a number of agile BPM approaches that seek to accelerate the redesign of business process models. Meta-models are a key BPM feature that reduce the ambiguity of business process models. This paper describes a meta-model supporting the agile version of the Business Process and Practice Alignment Methodology (BPPAM) for business process improvement, which captures process information from actual work practices. The ability of the meta-model to achieve business process agility is discussed and compared with other agile meta-models, based on definitions of business process flexibility and agility found in the literature. (C) 2017 The Authors. Published by Elsevier B.V

    Agile Requirements Engineering: A systematic literature review

    Get PDF
    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

    Boundary Objects and their Use in Agile Systems Engineering

    Full text link
    Agile methods are increasingly introduced in automotive companies in the attempt to become more efficient and flexible in the system development. The adoption of agile practices influences communication between stakeholders, but also makes companies rethink the management of artifacts and documentation like requirements, safety compliance documents, and architecture models. Practitioners aim to reduce irrelevant documentation, but face a lack of guidance to determine what artifacts are needed and how they should be managed. This paper presents artifacts, challenges, guidelines, and practices for the continuous management of systems engineering artifacts in automotive based on a theoretical and empirical understanding of the topic. In collaboration with 53 practitioners from six automotive companies, we conducted a design-science study involving interviews, a questionnaire, focus groups, and practical data analysis of a systems engineering tool. The guidelines suggest the distinction between artifacts that are shared among different actors in a company (boundary objects) and those that are used within a team (locally relevant artifacts). We propose an analysis approach to identify boundary objects and three practices to manage systems engineering artifacts in industry

    DECISION MAKING SUPPORT THROUGH A KNOWLEDGE MANAGEMENT FRAMEWORK FOR COMPLEX IT SYSTEMS DEVELOPMENT PROJECTS IN THE KINGDOM OF SAUDI ARABIA

    Get PDF
    Recent research reveals a narrow, rational model of problem- solving and decision-making in complex IT systems development projects. This creates problems that are identified in the thesis. The aim of this study is to develop a novel decision-making framework to support the decision-making process of managers of complex IT systems development projects by focusing on knowledge management frameworks. The objectives for the research were determined through a critical review of the existing research on decision-making in IT projects, primarily to discover how project managers’ decision-making can be supported through project-specific knowledge management. A qualitative research approach was then designed to investigate the phenomenon in its context by conducting in-depth semi-structured interviews. This study used qualitative data, through expert participants’ observations and opinions on IT systems development, particularly by understanding project management issues. The expert participants expressed their experiences through in-depth interviews. The collected data was then analysed using the thematic analysis technique and the findings were used to develop the IT Systems Development Decision-Making Support Framework. The Framework was then validated through focus group interviews. The main contribution of this research is based on the application of knowledge creation and knowledge management theories to decision-making frameworks for IT systems projects through the IT Systems Development Decision-Making Support Framework. The Framework is expected to enable decision evaluation and project-specific knowledge generation and sharing in IT systems development projects. This is vital for the type of contextual knowledge required for project-specific knowledge creation and management. Since IT systems development projects tend to be unique and their development process is complex, it is contended that an effective novel approach for modelling the expert decision-making process and assessing the defined model through project-specific knowledge activities is essential. This approach should help to deal with high level of complexity that is normally found in IT systems development projects
    • 

    corecore