169 research outputs found

    Systematic mapping of software engineering management with an agile approach

    Get PDF
    El enfoque ágil ha generado una amplia variedad de estrategias para administrar con éxito diversos proyectos de software en todo el mundo. Además, podemos asegurar que los proyectos de software se han beneficiado de los métodos ágiles ya conocidos. En este sentido, este artículo busca demostrar cómo se aplica el enfoque ágil en las áreas de la gestión en la ingeniería del Software. Para ello, este estudio realiza un mapeo sistemático para identificar las principales tendencias en la gestión de la ingeniería de software con un enfoque ágil. Se han identificado un total de 1137 artículos, de los cuales 165 son relevantes para los fines de este estudio, estos indican que la entrega temprana de valor, un principio clave de la agilidad, sigue siendo la principal tendencia para el uso de métodos ágiles. Sin embargo, también existen fuertes tendencias enfocadas en puntos clave de la gestión en ingeniería de software, como optimizar la gestión de calidad, optimizar la especificación de requisitos, optimizar la gestión de riesgos y mejorar la comunicación y coordinación del equipo, estos resultados permitirán generar nuevas líneas de investigación para cada punto clave de la gestión en la ingeniería del software impactado por el enfoque ágil.The agile approach has generated a wide variety of strategies to successfully manage various software projects worldwide. In addition, we can ensure that software projects have benefited from the already known agile methods. In this sense, this article seeks to demonstrate how the agile approach is applied in Software engineering management areas. To do this, this study performs a systematic mapping to identify the main trends in software engineering management with an agile approach. A total of 1137 articles have identified, of which 165 are relevant for the purposes of this study, these indicate that early value delivery, a key principle of agility, continues to be the main trend for the use of agile methods. However, there are also strong trends focused on key points of management in software engineering, such as optimize quality management, optimize requirements specification, optimize risk management, and improve team communication and coordination, these results will allow generating new lines of research for each key point of management in software engineering impacted by the agile approach

    Estudio investigación acción - Definición de marco de trabajo empleando metodologías ágiles para la configuración de herramientas tecnológicas y su aplicación en proyectos de desarrollo de software para una empresa aseguradora

    Get PDF
    El presente trabajo describe la revisión sistemática realizada sobre el uso correcto de las metodologías ágiles y herramientas para proyectos de desarrollo de software dependiendo de las complejidades que se presente. Se inicia con una breve descripción del problema que se busca resolver para la cual se realiza la revisión sistemática. Este problema principalmente es la ausencia de un marco de trabajo que facilite a la organización y guíe con este el uso correcto de las metodologías ágiles y herramientas tecnológicas aplicadas a proyectos de desarrollo de software. Con esto se pretende ayudar a usuarios antes de la construcción del software; es decir que le facilite identificar la complejidad del proyecto que desea implementar y con eso pueda escoger una metodología, herramientas o técnicas para usarlas en la ejecución de su proyecto. Luego de especifica el método de revisión de literatura a emplear la cual será principalmente una revisión sistemática en múltiples bases de datos de artículos como Scopus o IEEE usando el método PICOC como se describe en dicha sección. Luego estos artículos encontrados se filtran utilizando criterios de inclusión y exclusión como el año de publicación o el contenido del artículo. Finalmente, una vez seleccionados los artículos relevantes se procede a responder a las preguntas de investigación planteadas durante la aplicación del método PICOC. En este caso se consideraron 4 preguntas que fueron respondidas utilizando todos los artículos relevantes.Trabajo de investigació

    La Metodología SCRUM en el Sistema de Gestión de Calidad en una empresa de manufactura de grifería

    Get PDF
    La calidad como proceso de continuo mejoramiento en productos y servicios acompaña la humanidad en prácticamente todas las etapas, logrando optimizar recursos, tiempo y otros aspectos determinantes referentes a la calidad. Las organizaciones que emplean Scrum y demandan de un sistema de gestión de calidad como lo es ISO 9001:2015, afrontan considerables desafíos en el empeño por explicar que las actividades del proceso cumplen con el estándar, y por desarrollar procedimientos, técnicas y herramientas para ello. La estrategia propuesta beneficia a profesionales y empresas que pretenden emplear y favorecerse de estas soluciones. Se analiza la factibilidad de la metodología Scrum en el sistema de gestión de calidad en la producción de grifería en una empresa ecuatoriana, para garantizar que el producto cumple con las políticas de la entidad. Se realiza una investigación cualitativa de nivel descriptivo, la cual detalla concepciones esenciales de la aplicación de Scrum en los sistemas de gestión de calidad y los procesos industriales para la producción de grifería. Adoptar esta metodología en una empresa manufacturera de grifería tiene efectos positivos en el desempeño de la organización, satisfacción del cliente, la reducción de costos y la mejora continua a la calidad; aplicando los procesos al entorno cambiante y evolucionando según las necesidades del cliente.

    Adopting Agile Methods in Large-scale Organizations using Scaling Frameworks

    Get PDF
    Agile methods were originally developed for small and co-located teams. The popularity and success of agile methods in small teams led to growing interest on agile adoption across large organizations as well. However, there are several challenges while adopting agile to large, e.g., coordination between large number of teams and integration of other nondevelopment units e.g., HR, and marketing. Scaling frameworks, e.g. Scaled Agile Framework (SAFe) and Large ScaleScrum (LeSS) to support scaling agile to large have become popular in the recent past. Despite of popularity, there is very little scientific research on usage of the scaling frameworks. The primary goal of the thesis is to investigate the adoption and usage of scaling frameworks in practice. The goal is divided into two parts: a) scaling frameworks usage and adoption and b) SAFe usage and adoption. In the first part, we conducted two surveys. The first survey aimed to explore why the frameworks were developed, and how they were evolved, their benefits and challenges directly from the practitioners who developed them. Later, in second survey, we collected data from 204 software practitioners using scaling frameworks to understand the reasons, expected benefits and satisfaction of using them. In the second part, we conducted a multivocal literature review (MLR) due to the lack of scientific evidence on SAFe, to understand the benefits and challenges of SAFe adoption. Next, we conducted an indepth case study to explore the reasons, transformation process, benefits and challenges of SAFe. To get a wider overview of the benefits and challenges of SAFe we conducted a survey, to explore the benefits and challenges of SAFe. Our results for the first part show that majority of the frameworks were designed to improve agility, collaboration, coordination,and synchronization between agile teams. The most common reasons for their adoption were to scale more people and deal with existing challenges and pain points. The benefits of adopting these frameworks were categorized intoto business, product, organizational, and culture and the challenges were categorized to implementation, organizational,and scope. Our results for the second part show that reasons for SAFe adoption are related to organizational, business,and framework-specific. SAFe transformation activities typically map with the SAFe roadmap activities. The most common benefits of SAFe adoption are improved transparency, collaboration and faster time to market. The most significant challenges of SAFe adoption are identifying value streams and forming ARTs, change resistance, and inculcating an agile mindset. More in-depth research on scaling frameworks is needed to establish the effectiveness oftheir usage in practice. We encourage researchers to conduct in-depth case studies on their usage and adoption

    The Digital Transformation of Automotive Businesses: THREE ARTEFACTS TO SUPPORT DIGITAL SERVICE PROVISION AND INNOVATION

    Get PDF
    Digitalisation and increasing competitive pressure drive original equipment manufacturers (OEMs) to switch their focus towards the provision of digital services and open-up towards increased collaboration and customer integration. This shift implies a significant transformational change from product to product-service providers, where OEMs realign themselves within strategic, business and procedural dimensions. Thus, OEMs must manage digital transformation (DT) processes in order to stay competitive and remain adaptable to changing customer demands. However, OEMs aspiring to become participants or leaders in their domain, struggle to initiate activities as there is a lack of applicable instruments that can guide and support them during this process. Compared to the practical importance of DT, empirical studies are not comprehensive. This study proposes three artefacts, validated within case companies that intend to support automotive OEMs in digital service provisioning. Artefact one, a layered conceptual model for a digital automotive ecosystem, was developed by means of 26 expert interviews. It can serve as a useful instrument for decision makers to strategically plan and outline digital ecosystems. Artefact two is a conceptual reference framework for automotive service systems. The artefact was developed based on an extensive literature review, and the mapping of the business model canvas to the service system domain. The artefact intends to assist OEMs in the efficient conception of digital services under consideration of relevant stakeholders and the necessary infrastructures. Finally, artefact three proposes a methodology by which to transform software readiness assessment processes to fit into the agile software development approach with consideration of the existing operational infrastructure. Overall, the findings contribute to the empirical body of knowledge about the digital transformation of manufacturing industries. The results suggest value creation for digital automotive services occurs in networks among interdependent stakeholders in which customers play an integral role during the services’ life-cycle. The findings further indicate the artefacts as being useful instruments, however, success is dependent on the integration and collaboration of all contributing departments.:Table of Contents Bibliographic Description II Acknowledgment III Table of Contents IV List of Figures VI List of Tables VII List of Abbreviations VIII 1 Introduction 1 1.1 Motivation and Problem Statement 1 1.2 Objective and Research Questions 6 1.3 Research Methodology 7 1.4 Contributions 10 1.5 Outline 12 2 Background 13 2.1 From Interdependent Value Creation to Digital Ecosystems 13 2.1.1 Digitalisation Drives Collaboration 13 2.1.2 Pursuing an Ecosystem Strategy 13 2.1.3 Research Gaps and Strategy Formulation Obstacles 20 2.2 From Products to Product-Service Solutions 22 2.2.1 Digital Service Fulfilment Requires Co-Creational Networks 22 2.2.2 Enhancing Business Models with Digital Services 28 2.2.3 Research Gaps and Service Conception Obstacles 30 2.3 From Linear Development to Continuous Innovation 32 2.3.1 Digital Innovation Demands Digital Transformation 32 2.3.2 Assessing Digital Products 36 2.3.3 Research Gaps and Implementation Obstacles 38 3 Artefact 1: Digital Automotive Ecosystems 41 3.1 Meta Data 41 3.2 Summary 42 3.3 Designing a Layered Conceptual Model of a Digital Ecosystem 45 4 Artefact 2: Conceptual Reference Framework 79 4.1 Meta Data 79 4.2 Summary 80 4.3 On the Move Towards Customer-Centric Automotive Business Models 83 5 Artefact 3: Agile Software Readiness Assessment Procedures 121 5.1 Meta Data 121 5.2 Meta Data 122 5.3 Summary 123 5.4 Adding Agility to Software Readiness Assessment Procedures 126 5.5 Continuous Software Readiness Assessments for Agile Development 147 6 Conclusion and Future Work 158 6.1 Contributions 158 6.1.1 Strategic Dimension: Artefact 1 158 6.1.2 Business Dimension: Artefact 2 159 6.1.3 Process Dimension: Artefact 3 161 6.1.4 Synthesis of Contributions 163 6.2 Implications 167 6.2.1 Scientific Implications 167 6.2.2 Managerial Implications 168 6.2.3 Intelligent Parking Service Example (ParkSpotHelp) 171 6.3 Concluding Remarks 174 6.3.1 Threats to Validity 174 6.3.2 Outlook and Future Research Recommendations 174 Appendix VII Bibliography XX Wissenschaftlicher Werdegang XXXVII Selbständigkeitserklärung XXXVII

    Product Development within Artificial Intelligence, Ethics and Legal Risk

    Get PDF
    This open-access-book synthesizes a supportive developer checklist considering sustainable Team and agile Project Management in the challenge of Artificial Intelligence and limits of image recognition. The study bases on technical, ethical, and legal requirements with examples concerning autonomous vehicles. As the first of its kind, it analyzes all reported car accidents state wide (1.28 million) over a 10-year period. Integrating of highly sensitive international court rulings and growing consumer expectations make this book a helpful guide for product and team development from initial concept until market launch

    Product Development within Artificial Intelligence, Ethics and Legal Risk

    Get PDF
    This open-access-book synthesizes a supportive developer checklist considering sustainable Team and agile Project Management in the challenge of Artificial Intelligence and limits of image recognition. The study bases on technical, ethical, and legal requirements with examples concerning autonomous vehicles. As the first of its kind, it analyzes all reported car accidents state wide (1.28 million) over a 10-year period. Integrating of highly sensitive international court rulings and growing consumer expectations make this book a helpful guide for product and team development from initial concept until market launch

    CORPORATE SOCIAL RESPONSIBILITY IN ROMANIA

    Get PDF
    The purpose of this paper is to identify the main opportunities and limitations of corporate social responsibility (CSR). The survey was defined with the aim to involve the highest possible number of relevant CSR topics and give the issue a more wholesome perspective. It provides a basis for further comprehension and deeper analyses of specific CSR areas. The conditions determining the success of CSR in Romania have been defined in the paper on the basis of the previously cumulative knowledge as well as the results of various researches. This paper provides knowledge which may be useful in the programs promoting CSR.Corporate social responsibility, Supportive policies, Romania
    corecore