The Agile methodologies have attracted the software development industry's attention due to their capability to overcome the limitations of the traditional software development approaches and to cope with increasing complexity in system development. Scrum is one of the Agile software development processes broadly adopted by industry. Scrum promotes frequent customer involvement and incremental short releases. Despite its popular use, Scrum’s requirements engineering stage is inadequately defined which can lead to increase development time and cost, along with low quality or failure for the end products. This research shows the importance of activity planning of requirements engineering in improving the product quality, cost, and scheduling as well as it points out some drawbacks of Agile practices and available solutions. To improve the Scrum requirements engineering by overcoming its challenges in cases, such as providing a comprehensive understanding of the customer’s needs and addressing the effects of the challenges in other cases, such as frequent changes of requirements, the Design Thinking model is integrated into the Scrum framework in the context of requirements engineering management. The use of the Design Thinking model, in the context of requirements engineering management, is validated through an in-depth scientific study of the IBM Design Thinking framework. In addition, this research presents an Items Prioritization dEcision Support System (IPESS) which is a tool to assist the Product Owners for requirements prioritization. IPESS is built on information collected in the Design Thinking model. The IPESS tool adopts Analytic Hierarchy Process (AHP) technique and PageRank algorithm to deal with the specified factors and to achieve the optimal order for requirements items based on the prioritization score. IPESS is a flexible and comprehensive tool that focuses on different important aspects including customer satisfaction and product quality. The IPESS tool is validated through an experiment that was conducted in a real-world project / Includes bibliography. / Dissertation (PhD)--Florida Atlantic University, 2021. / FAU Electronic Theses and Dissertations Collection

Department of Research and Development of company Seznam.cz plans and implements its projects using Scrum agile development methodology.  The company inquires an information system that captures the process of development. The information system must capture all company's dissimilarities from generic process and the system must be connected to other company's systems.

The diploma thesis deals with implementation of Agile Project Management Approach for smaller software projects of the department ATS of the office HTS CZ of the corporation Honeywell. The ATS department is a part of the Aerospace division, focused at aviation. For implementation of new approach there was used the agile methodology Scrum and the project management standard PMBoK.

Agile software development methodologies are very popular for their efficiency and flexibility. This thesis focuses on agile software development methodology called Scrum. Basic description and comparison of traditional and agile methodologies is mentioned at first. Attention is paid to methodology Scrum which is shown on an example of usage by a specific company. It is convenient to use some software tool for organization of Scrum methodology. Therefore, an overview of the most common tools and basic comparison of software tools for organizing this methodology is presented. Conclusion of this thesis is recommendation for improvements for the investigated team, based on issues which were identified.

Tesis para optar al grado de Magíster en Gestión y Dirección de Empresas / El objetivo de este caso de negocio, es apoyar la implementación de la Metodología Ágil, específicamente Scrum en una empresa del Retail Financiero en Chile (CMR-Falabella). Se espera, que, a través de este trabajo, se oriente a la empresa en la elección de su portafolio de mejoras y requerimientos de TI, como también, la aplicación de Scrum, en el trabajo diario de sus necesidades y mejoras de los procesos de apoyo al negocio. La información y datos entregados, será levantado de las áreas de operaciones y sistemas como del negocio de CMR-Falabella, para lo cual, se realizó entrevistas con expertos de Ti como así mismo personas claves de recursos humanos y del negocio. CMR-Falabella, siempre ha entregado soluciones fáciles y rápidas para sus clientes, por lo cual, se hace necesario un alineamiento y oportunidad en el área de TI, con respecto a mejoras y revisiones de cómo se están realizando las cosas actualmente. Se realizará un levantamiento de la metodología clásica v/s la metodología ágil propuesta (Scrum), lo que llevará a identificar y cuantificar, a través de métricas, el valor que Scrum entregará a la organización, con respecto a las entregas y puestas en producción de los desarrollos por parte del área de sistemas. Sin duda un factor importante, es la colaboración del área de Recursos Humanos, que, a través, de su oficina de Gestión de Cambio, impulsará, comunicará y motivará a cada uno de los integrantes de la organización, como a los equipos de la Célula a enfrentar esta nueva forma de hacer las cosas, todo esto alineados con los valores de CMR-Falabella. Es un gran desafío de cambiar los paradigmas, con entregas parcializadas a los clientes, que aportan un valor a la organización, con definiciones que se irán enriquecerán en cada sprint, que permitirá generar ahorros y un Time to Market anual (MM$623), que, ayudará con los resultados y a mantener los lineamientos con los objetivos planteados, entregando beneficios en tiempos más cortos. El trabajo en equipo comienza desde un inicio, como así mismo el trabajo colaborativo y la autogestión de los integrantes es fundamental en cada una de las etapas de la metodología Scrum, los resultados se ven cada 10 días, lo que permite innovar en cada definición y no esperar hasta la entrega final.

Este proyecto implementó una plataforma para la gestión de blogs para la Escuela de Ingeniería de Sistemas de Información y Computación (EISC), con la finalidad de mejorar la comunicación que mantiene con la comunidad académica y personas ajenas a la UPC con intereses hacia la Escuela. El presente documento está dividido en seis capítulos. El primer capítulo incluye la definición de conceptos asociados a marketing digital que permitan entender la importancia de tener una estrategia de marketing digital y de emplear las herramientas adecuadas para implementarlo en un entorno universitario. El segundo capítulo presenta un breve análisis de las soluciones alternativas, un análisis comparativo entre las mismas para finalmente brindar detalle sobre la solución propuesta. El tercer capítulo describe con mayor detalle los objetivos, el alcance, los riesgos y beneficios del proyecto. El cuarto capítulo explica la forma en la que se gestionó el proyecto durante el ciclo 2013-01, empleando la metodología Scrum y siguiendo los lineamientos de gestión establecidos por las empresas virtuales SSIA, Software Factory y QA. El quinto capítulo incluye el detalle del trabajo y todas las actividades realizadas a lo largo del proyecto. El sexto capítulo presenta la arquitectura del proyecto. Finalmente, se presentan los resultados obtenidos, conclusiones y evidencias del cumplimiento de los objetivos del proyecto. / This project implemented a web content management platform for the UPC’s School of Computer and Systems Engineering (EISC). This would allow them to manage their own blog and improve the communication with the academic community and any interested. This document is divided in six chapters. The first one describes the benefits and basic concepts related to digital marketing that allow to understand the importance of having a digital marketing strategy and the importance of using the adequate tools to implement it in an academic environment. The second chapter presents a brief analysis of the alternative solutions, then a comparison between them and finally a detailed description of the one proposed in this project. The third chapter describes in detail the objectives, scope, risks and benefits of the project. The fourth chapter explain how the project was managed during the 2013-01 academic cycle, using the Scrum methodology along with the management guidelines established by the virtual enterprise SSIA, Software Factory and QA. The fifth chapter presents all the task and activities executed and accomplished along the project. The sixth chapter presents the project architecture. Finally, this document presents the outcomes, conclusions and evidence of the fulfillment of the project. / Tesis

Syfte: Syftet med denna studie är att med hjälp av agentteorin skapa en förståelse kring hur ledare styr medlemmar mot gemensamma mål i en organisation som använder sig av Scrum. Metod: En kvalitativ studie med sju semistrukturerade intervjuer från en agil avdelning har genomförts. Studien hade även ett hermeneutiskt vetenskapstradition och synsätt som utgångspunkt. Resultat & slutsats: Studiens resultat och slutsats är att kommunikationen är a och o för den studerade avdelningen och det genomsyrar hela arbetet. Vidare har relationen mellan scrum mastern och dess medlemmar hög prioritet. De personliga målen som skapas för medlemmarna påverkas av relationen och kommunikationen. Fortsättningsvis sker övervakningen över medlemmarnas prestationer mot mål via den dagliga kommunikationen på avdelningen. Examensarbetets bidrag: Denna uppsats bidrar till teorin med en empirisk undersökning av en agil metod, scrum, och ger en ökad förståelse för hur avdelningen arbetar mot gemensamma mål.

Syften med denna uppsats är att kartlägga hur utvecklare upplever platsoberoende scrum-utveckling, vilken problematik som uppstår samt om effektiviteten påverkas. För att uppnå studiens syfte och besvara de frågeställningar som formulerats i rapporten har data samlats in. Denna data har dels varit kvantitativ, där data har samlats in från en verksamhet som bedriver systemutveckling med metodiken scrum. Data har även varit kvalitativ där data i form av intervjuer har samlats in. Den insamlade datan har sedan analyserats för att kunna svara på forskningsfrågorna.   Efter genomförd analys har slutsatser dragits för att kunna uppfylla uppsatsen ursprungliga syfte. Den insamlade empirin tyder på att det finns viss problematik relaterad till kommunikation som blir tydlig när arbetet bedrivs platsoberoende. Den insamlade datan tyder även på en försämrad upplevelse av den sociala miljön när arbetet bedrivs platsoberoende. Slutligen tyder även det analyserade resultatet på en minskad effektivitet när arbetet övergått till platsoberoende. Det teoretiska ramverket ligger som grund för att redogöra för befintliga teorier som är relevanta för undersökningen. Rapporten redogör för befintliga teorier som är relaterade till platsoberoende arbete, agil utveckling, scrum utveckling samt hur effektivitetet av scrum-utveckling kan mätas. / The purpose of this thesis is to map how individuals experience remote scrum development, what problems arise and whether efficiency is affected. In order to achieve the purpose of the study and answer the research-questions formulated in the report, data has been collected. This data has been partly quantitative, where data has been collected from a business that conducts system development with the methodology scrum. Data has also been qualitative where data in the form of interviews have been collected. The collected data has then been analyzed in order to answer the research questions. After completing the analysis, conclusions have been drawn in order to fulfill the thesis' original purpose. The collected empirical evidence indicates that certain problems related to communication become clear when the work is conducted remote. The data collected also indicates a deteriorating experience of the social environment when the work is conducted remote. Finally, the analyzed result also indicates a reduced efficiency when the work has shifted to remote. The theoretical framework is the basis for presenting existing theories that are relevant to the study. The report describes existing theories that are related to site-independent work, agile development, scrum development and how the effectiveness of scrum development can be measured.

Context. Distributed software development becomes increasingly common with the trend of globalization. Scrum, as one of the methods to realize agile, is gradually accepted by more and more people and applied to actual industrial production. Although there have been some successful cases of distributed Scrum team development, the description of these successful experiences may not be exhaustive enough and not applicable to all teams. There is still a great demand for actual industrial case studies, especially related research on specific teams and detailed challenges encountered. In order to enable more distributed scrum teams to better handle various challenges in the development process, further research on the challenges the teams encounter and how to solve, mitigate, and avoid the impact of these challenges is necessary. Objectives. The main objectives of this research are to investigate the challenges faced by distributed Scrum teams in the development process, the factors that cause them, and how to deal with these challenges. Methods. We conducted a systematic literature review and obtained the most common problems encountered by distributed Scrum teams and parts of the factors that caused this problem. On this basis, we conducted case studies on 2 large companies in Asia. We used archived data to know the basic information of the case team and a semi-structured interview was used to understand the problems they encountered and their opinions. Results. During this study we found that the most common challenge encountered by distributed Scrum teams was "Communication among stakeholders". Totally 16 factors were found that could cause this challenge. The two main factors were “Team members have insufficient knowledge or different skill levels” and “Are not familiar with each other or have differences”. And 42 solutions were provided after we integrated the information obtained. Conclusions. We conclude that communication is a matter of great concern, whether in the literature we used or in our case team. The factors and solutions given are only for reference by teams of similar types and development backgrounds. Further researches on other different types of teams and other challenges encountered are also necessary.

Scrum is a widely used methodology for software development that is born of the Agile movement. In recent years DevOps has been increasing in popularity within the software industry. The purpose of this thesis is to firstly, explore the technical and social challenges a Scrum team may face when adopting DevOps. Secondly, to explore what collaboration mechanisms that can facilitate a closer cooperation between development and operations. A multiple case study was conducted using semi-structured interviews as the data collection method. The interviews were transcribed and analyzed using thematic analysis. Three technical challenges and one social challenge emerged from the analysis. Additionally, four mechanisms were identified during the analysis as ways to achieve a closer collaboration between the development and operations teams. The result discussion showed that challenges of adopting DevOps when using Scrum are comparable to the findings of previous research where the scope of methodology is not limited to Scrum. Furthermore, the identified collaboration mechanisms can be used by organizations to enhance collaboration between development and operations but should not be seen as strict guidelines.