Search

En aquest treball es presenta el primer cicle de vida del desenvolupament d’una aplicació d’escriptori destinada a l’anàlisi de dades i a la generació de models de pneumàtic. L'aplicació es desenvolupa a Python i està dirigida a equips de Formula Student, encara que també pot ser utilitzada fora d'aquest context; de manera que és possible importar i treballar amb dades de pneumàtic procedents del FSAE Tire Test Consortium (FSAE TTC). A partir d'un fitxer de dades, l'aplicació és capaç de descriure les característiques de força lateral, força de frenada i self-aligning torque d'un pneumàtic; fent ús del model Magic Formula '89. Per generar un model, es fa ús de la rutina de minimització Differential Evolution, que és capaç d'ajustar el model a les dades de manera automàtica, sense necessitat d'establir rangs o estimacions inicials per als coeficients del model. D'aquesta manera, l'usuari no necessita tenir experiència prèvia en modelització de pneumàtics ni coneixements sobre el significat físic dels coeficients. Un cop obtingut, el model pot ser exportat a MATLAB i integrat a un model de vehicle. L'execució del projecte es realitza d’acord a la metodologia agile, de manera que el desenvolupament de l'aplicació queda dividit en diversos cicles de vida. Cada cicle està compost per les fases d’anàlisi, disseny i implementació. A més, al final de cada cicle es fa un lliurament de l'aplicació a l'usuari per facilitar la detecció d'errors i afavorir l'aparició de possibles millores; així com dur a terme un disseny orientat a satisfer les demandes de l’usuari. El codi de l'aplicació s'estructura seguint l’esquema del patró Model View Presenter, de manera que resulta possible fer canvis en la GUI o les funcions de càlcul de forma independent. Per acabar, aquest treball pretén establir les bases per continuar desenvolupant i perfeccionant l'aplicació en futurs cicles de vida, mantenint en tot moment la filosofia i els mètodes emprats des del començament del projecte., En este trabajo se presenta el primer ciclo de vida del desarrollo de una aplicación de escritorio destinada al análisis de datos y a la generación de modelos de neumático. La aplicación se desarrolla en Python y está dirigida a equipos de Formula Student, aunque también puede ser utilizada fuera de este contexto; de modo que resulta posible importar y trabajar con datos de neumático procedentes del FSAE Tire Test Consortium (FSAE TTC). A partir de un archivo de datos, la aplicación es capaz de describir las características de fuerza lateral, fuerza de frenado y momento autoalineante de un neumático; haciendo uso del modelo Magic Formula ’89. Para generar un modelo, se hace uso del algoritmo de minimización Differential Evolution, que es capaz de ajustar el modelo a los datos de forma automática, sin necesidad de establecer rangos o estimaciones iniciales para los coeficientes del modelo. De este modo, el usuario no necesita poseer experiencia previa en modelización de neumáticos ni conocimientos acerca del significado físico de los coeficientes. Una vez obtenido, el modelo puede ser exportado a MATLAB e integrado en un modelo de vehículo. La ejecución del proyecto se ciñe a la metodología agile, de modo que el desarrollo de la aplicación queda dividido en varios ciclos de vida. Cada ciclo está compuesto por las fases de análisis, diseño e implementación. Además, al final de cada ciclo se realiza una entrega de la aplicación al usuario para facilitar la detección de errores y favorecer la aparición de posibles mejoras; así como llevar a cabo un diseño orientado a satisfacer las demandas del usuario. El código de la aplicación se estructura en base al patrón Model View Presenter, por lo que resulta posible llevar a cabo cambios en la GUI o las funciones de cálculo de forma independiente. Este trabajo pretende sentar las bases para continuar desarrollando la aplicación en futuros ciclos de vida, manteniendo en todo momento la filosofía empleada desde el comienzo., This project introduces the first development lifecycle of a desktop application for tyre data analysis and tyre modelling. The application is developed with Python and is aimed at Formula Student teams, but can also be used outside this context, so that it is possible to import and work with tyre data from the FSAE Tire Test Consortium (FSAE TTC). Taking a data file as an input, the application is able to describe the lateral force, braking force and self-aligning torque characteristics of a tyre, making use of the Magic Formula '89 model. To generate a model, the Differential Evolution minimisation algorithm is used, which is able to fit the model to the data automatically, without the need to set initial ranges or estimations for the model coefficients. This way, the user does not need any previous experience in tyre modelling or knowledge of the physical meaning of the coefficients. Once obtained, the model can be exported to MATLAB and be integrated into a vehicle model. The execution of the project follows the agile methodology, so that the development of the application is divided into several life cycles. Each cycle is broken down into the analysis, design and implementation phases. In addition, at the end of each cycle, the application is delivered to the user to facilitate the detection of errors and encourage the appearance of possible improvements, as well as to carry out a design aimed at satisfying the user's demands. The application code is structured on the basis of the Model View Presenter pattern, making it possible to make changes to the GUI or calculation functions independently. Finally, this work aims to lay the foundations for further development and refinement of the application in future life cycles, while maintaining the philosophy and methods used from the beginning of the project.

Aquest treball final de màster és sobre Printing Template Engine (PTE), un motor de renderització de PDF destinat a millorar els procediments de generació i gestió de documents. L'estudi examina les dificultats amb els processos de documents convencionals i el requisit d'un sistema complet que combini sincronització de dades, funcionalitat offline i renderització dinàmica. El treball se centra en l'arquitectura i el disseny de PTE, fent ús de la tecnologia JavaScript i processos Agile per garantir-ne usabilitat, escalabilitat i adaptabilitat. PTE demostra la seva eficàcia en la producció de documents PDF personalitzats mitjançant procediments rigorosos de prova i control de qualitat. El projecte també aborda la seguretat, el rendiment i els avenços futurs alhora que integra PTE amb els sistemes actuals. Els resultats emfatitzen la importància de la PTE per a l'optimització del procés documental, la millora de la productivitat i la satisfacció de les demandes de les regions sense alfabetització digital. En definitiva, aquesta iniciativa avança en el camp de la gestió de documents i proporciona informació valuosa a les empreses que busquen solucions fiables i eficaces per a les activitats relacionades amb els documents.

Este proyecto, desarrollado en un convenio de prácticas de empresa, trata sobre la creación de un sistema interno para mejorar la productividad de los equipos de desarrollo. El objetivo es proporcionar arquetipos, estructuras base de archivos, que agilizan y simplifican la creación de nuevos componentes para sus proyectos centrados en microservicios. Como lenguaje de programación se ha usado Java, junto con frameworks como Spring y plataformas de servicio como AWS, además de la adaptación de metodologías ágiles para el seguimiento del proyecto., This project, developed in an internship agreement, is about creating an internal system to improve the productivity of development teams. The goal is to provide archetypes, base file structures, that accelerate and simplify the creation of new components for their projects focused on microservices. As a programming language we have used Java, along with frameworks such as Spring and service platforms such as AWS, in addition to the adaptation of agile methodologies for project management.

IT-avdelningar är många gånger pressade att leverera ett värde med kvalitet och inom en tidsbegränsad period, vilket kan resultera i ofullständiga leveranser. För att möta dessa krav behöver IT-avdelningar arbeta med att effektivisera sina verksamhetsprocesser och kontinuerligt lärande. Genom tvärfunktionella team kan effektiviteten öka genom en förbättrad samordning och minskat beroende av nyckelpersoner.Den här intervjustudien riktar sig mot en IT-avdelning inom ett försäkringsbolag, med syfte att studera fallföretagets nuvarande verksamhetsprocesser inom utveckling och förvaltning för att identifiera utmaningar som orsakar ofullständiga leveranser. Därtill avser studien att föreslå förändringsåtgärder som kan eliminera dessa orsaker. Inledningsvis genomfördes en litteraturgenomgång för att anskaffa kunskap inom området. Utifrån insamlad kunskap från tidigare studier och litteratur har en analysmodell tagits fram för att sammanfattningsvis visualisera faktorer som kan öka graden av avslutade uppgifter inom en leverans. Studien har genomförts med en kvalitativ ansats i form av semistrukturerade intervjuer. Sex respondenter från fallföretaget har deltagit i studien, där samtliga respondenter har ett direkt beroende till fallförtagets utvecklings- och förvaltningsprocesser. Utifrån en analys av resultatet med stöd av analysmodellen har studiens undersökningsfrågor besvarats.Slutsatserna som kan dras av denna studie är att fallföretagets utvecklings- och förvaltningsprocesser är strukturerade i tre huvudsakliga områden: Fokussprint, Förvaltning och Projekt. Uppdelningen av nyutveckling och förvaltning i olika team har förbättrat effektivitet och fokus för teamet. Däremot har flera faktorer identifierats som orsakarofullständiga leveranser, inklusive komplexitet som upptäcks sent i genomförandet, brist på formella uppföljningar och kompetensglapp inom teamet. Studien resulterade i föreslagna förbättringsåtgärder för fallföretaget som inkluderar behovetav förbättrad tid

Organisationer blir mer och mer datadrivna, vilket leder till ett behov av bättre datahantering. Uppkomsten av data mesh, ett socio-tekniskt decentraliserat tillvägagångssätt, innebär en ny möjlighet för organisationer att hantera data på ett nytt sätt. Data mesh inkluderar- användningen av dataprodukter, som möjliggör paketering and tillhandahållande av datatill data konsumenter. Denna avhandling undersöker implementeringen av data mesh inom en finansiell organisation, med fokus på produktutveckling av dataprodukter. Genom att kombinera teori om data mesh och produktutveckling tillsammans med en fallstudie utförd i en finansiell organisation, kompletterad med branschintervjuer, identifieras krav, utmaningar- samt nuvarande och potentiella framtida tillvägagångssätt. Den här studien undersöker forsksningsgapet som industrin uttrycker när det gäller praktisk tillämpning av data mesh-teori, som även uttrycks av luckor i litteraturen relaterat till implementering av teorin, särskilt relaterat till produktutveckling. En rekommendation gällande produktutveckling av dataprodukter inom en organisation i liknande kontext som fallstudieföretaget presenteras, med fokus på nya nödvändiga steg som behövs utföras före och under produktutvecklingsprocessen., As organizations become more and more data driven, a need for better data management has surfaced. The emergence of data mesh, socio-technical and decentralized approach, provided an option to handle data management inside organizations. The data mesh approach includes the use of data products, a product that allows for packaging and provisioning o fdata. This thesis investigates the implementation of data mesh inside a financial organization, exploring the product development of data products. By combining data mesh theory and product development theory together with a case study performed in a financial organization, supplemented with industry interviews, requirements, challenges, as well as present and potential future practices are extracted. The study highlights the gap expressed by the industry of practical application of data mesh theory, as there exists gaps in the literature addressing implementations of the theory, especially related to product development. A recommendation for how to approach an implementation of data mesh within an organization existing in similar context as the case company is provided, highlighting necessary new steps to be performed before and during the product development process.

This study investigates the integration of Agile approaches with hightech advancements such as digitalisation, automation, interconnected systems, and IoT within the automotive industry. The primary aim is to provide a comprehensive framework for Agile approaches tailored to the advanced automotive industry. It addresses the growing need for adaptability in development processes to meet market demands and rapid technological overevolving as vehicles transform into computers on wheels. The study begins with a thorough literature review of both Agile approaches and emerging industrial technologies. This theoretical foundation identifies gaps in existing research and underscores the necessity for a framework to integrate agile approaches with high techniques. Empirical data were collected by a qualitative case study, through interviews with professionals from large, global automotive companies, including Volvo Cars and Volvo Construction Equipment (VCE). These interviews provided realworld insights into Agile approaches' opportunities, challenges, and tailoring to meet industryspecific needs. A framework for agile implementation in the automotive industry is constructed and comprised of an extensive literature review and profound insights from the results of the content analysis of the interviews. This framework emphasises cultivating an Agile mindset, leveraging modern technologies, fostering customer collaboration, streamlining documentation processes, embracing changes promptly, improving planning methodologies, increasing flexibility, and acquiring relevant skills. Key findings reveal that process development methods must evolve alongside advancing technologies. Industries must adapt by tailoring Agile approaches and incorporating hybrid approaches, as reverting to previous methods is not a choice. This research contributes to both theory and practice by providing a comprehensive framework for Agile approaches in the automotive industry. It bridges the gap between

Syftet med denna rapport är att analysera samt presentera förslag på vilka ledarskapsstilar och metoder som kan användas under en ramp-up. Vidare undersöker rapporten vilka ledarskapsstilar som bör användas när en stabil respektive instabil efterfrågan råder. Både kvantitativa samt kvalitativa forskningsmetoder ligger som grund för rapporten för att besvara forskningsfrågorna. De kvantitativa metoderna som används är huvudsakligen insamling av vetenskapliga artiklar och kurslitteratur vilka bygger det teoretiska ramverket. Även data från fallföretaget ingår i dem kvantitativa metoderna. Vidare är semistrukturerande intervjuer samt observationer inom fallföretagets produktion tillvägagångssättet för dem kvalitativa metoderna. Det agila ledarskapet lämpar sig bra för företag som befinner sig i en situation där det krävs en högre grad av flexibilitet. Det skulle kunna vara under oroliga perioder som gör att snabba omställningar inom verksamhetenen blir nödvändigt. Företag som smidigt kan genomgå förändringar för att anpassa sig har en högre chans för fler marknadsandelar och blir därför lönsammare under perioder som kräver detta. Ett leant ledarskap har stort fokus på kontinuerlig förbättring, minimering av slöserier och människans utveckling inom företaget. Detta ledarskap bör därför implementeras i företag som är verksamma i marknader som är stabila under längre perioder. När det gäller personalens utveckling kan det dock vara gynnsamt att implementera denna form av ledarskap under en ramp-up. Detta på grund av att personalens kompetens ökar, det skapas en förbättringskultur och en gemensam strävan efter perfektion sprids på arbetsplatsen. Inget företag är det andra likt, vilket betyder att varje företag befinner sig i en unik situation och bör implementera ledarskap, verktyg och metoder därefter. Denna rapport hoppas kunna vidga vyerna hos företag för hur dessa hjälpmedel kan underlätta arbeten med diverse processer, samt visa att dessa hjälpmedel finns tillgängl, The purpose of this thesis is to analyze as well as present suggestions on which leadership styles and methods that can be used during a Ramp-up. Additionally, the thesis will explore the most suitable leadership style for both stable and unstable demands. Both quantitative and qualitative research methods lie as a base for this thesis to answer the research questions. The qualitative methods that are being used are the collection of peer reviewed articles and course literature which is the base for the theoretical framework. Data collected from the case company is included in the qualitative methods. Furthermore, semi structured interviews and observations within the case company’s production constitute the approach for these qualitative methods. The Agile leadership suits well for companies facing situations requiring a higher degree of flexibility. These could be turbulent periods requiring swift operational adjustments. Companies that smoothly can apply adaptive changes have a higher chance of acquiring more market shares and can therefore be more profitable during periods that demand it. A Lean leadership style have a big focus on continuous improvements, minimizing waste and the individual’s growth within the company. This leadership style should therefore be implemented in companies that are active markets where the demand is stable during longer periods. Regarding the staff’s development, it can be favorable to implement this form of leadership during a ramp-up. The reason behind this is that the staff’s competence increases, creating a culture of improvement and facilitates a shared pursuit of perfection that spreads in the workplace. No company is the other alike, meaning that every company exist in a unique situation and should implement leadership, tools and methods thereafter. This Thesis hopes to broaden the views in companies to help them better understand how these aids can facilitate work with various processes and also show that these aids are a

Agile methodologies have emerged as transformative paradigms in the ever-evolving software development landscape, emphasizing iterative development, customer collaboration, and adaptability. As the scope and complexity of projects and organizations expand, applying agile principles within the context of Large-Scale Agile Development (LSAD) encounters distinctive challenges. The majority of challenges encountered in LSAD, technical and non-technical, are attributed to the accrual of social debt. However, a conspicuous gap remains in understanding and addressing social debt in LSAD. This study aims to fill this void by investigating social debt in LSAD through an in-depth industrial case study with a leading Nordic company specializing in telecommunications software and services and focusing on producing secure 5G network solutions. The study investigates the causes of LSAD's social debt and examines its impacts on secure 5G telecom software development. By addressing these objectives, this research sheds light on a critical aspect of LSAD's social debt, caused by 3C challenges(communication, coordination and collaboration), social confines challenges, community smells challenges, and organisational social challenges in the telecom sector that have been underrepresented in the existing literature.

The development of software and systems is a complex task that involves social, technical and organisational factors. Technical debt is a well-known concept that refers to the negative consequences of taking shortcuts in software development. However, organisational debt (OD) is a less well-known phenomenon that arises due to shortcuts in the organisational structure and processes of a software organisation. The lack of a clearly defined OD makes it difficult to identify and manage this type of debt. This study presents a multi-vocabulary literature review that consolidates an understanding of the nature of OD and its impact on software organisations. OD encompasses a set of attributes, precedents and outcomes. In addition, this study highlights the five causes and mitigation strategies of OD. The results of this study indicate that software companies are facing a major issue with OD. Future research should include empirical studies to validate techniques that can assist software professionals in managing OD to address this issue.

The aims of this study were to use the operant supervisory taxonomy index (OSTI) with self-recorded videos: 1) to assess three crucial supervisory behaviours at recurrent workplace meetings; 2) to assess an intervention to increase supervisors' use of performance consequences; 3) to demonstrate how using OSTI with video for studying supervisor-employee interactions contributes to the field of human factors and ergonomics. Eight supervisors at a technical company video-recorded themselves at standardised daily staff meetings for ten weeks (360 videos, in total). All supervisors increased their delivery of performance consequences per meeting after participating in weekly sessions focusing on their use of this behaviour. The use of the crucial supervisory behaviours varied within and between supervisors. A combination of self-recorded videos over time and OSTI is a useful method for objectively analysing supervisor performance in detail and can contribute to improving supervisory behaviours and their impact on performance and health., QC 20240705

Background: Trust is crucial for teams to function well, especially in collaborative settings. The COVID-19 pandemic challenged traditional trust-building methods due to remote work. Hybrid work models emerged, blending remote and in-office collaboration. Balancing remote and in-office work remains essential post-pandemic, recognizing benefits for both managers and employees. Purpose: This thesis explores the impact of hybrid work on trust within agile software development (ASD) teams. Research questions delve into the impact of hybrid work on trust across agile methodologies and explore communication methods fostering trust in agile teams in hybrid settings. Findings aim to guide agile teams and managers in optimizing remote work solutions for collaborative environments. Methodology: This study employs a qualitative approach conducting semi-structured interviews with 16 participants chosen through purposive sampling. Thematic analysis was employed to identify themes regarding hybrid work policies, trust dynamics, and communication methods in hybrid setups. Ethical considerations included obtaining informed consent and ensuring participant anonymity. Results and analysis: Findings show a preference for at least two days per week in the office. Trust aspects of ability and integrity were regarded as more important than benevolence for trustworthiness by most of the participants. The impact of hybrid work was revealed to be mostly on the aspect of benevolence. Scrum and Kanban agile methodologies exhibited varied responses to hybrid work's influence on trust based on their underlying principles. Participants recognized the challenges of remote work, preferring on-site communication for convenience while utilizing Microsoft Teams messaging for remote interactions. Adaptive strategies like breakout rooms were used to foster collaboration and transparency. Conclusions: Hybrid work poses challenges like communication barriers and difficulties in interpreting non-verbal cu

This research identifies shared strengths of Scrum and Kanban, such as iterative and incremental work and effective workload management, which are particularly beneficial in startup contexts characterized by high uncertainty. By systematically comparing the fundamental elements of both methodologies, the study delineates key dimensions and components that inform the development of a hybrid approach. This study aimed to explore which components of Kanban and Scrum are best suited for navigating uncertainty and ambiguity in a fast-paced environment. To achieve this objective, our first research question delves into the productive attributes of both Scrum and Kanban methods, laying the groundwork for our investigation. Additionally, we sought to identify the key factors driving adaptations in the application of these methods within software startups, as well as pinpoint the highlighted concepts and elements that can be effectively utilized. This formed the basis of our second research question, with the ultimate aim of developing a hybrid model that integrates the most beneficial aspects of both methodologies, thus addressing the challenges posed by uncertainty and rapid change in the initial phase of the study. We employed a mixed-methods approach, utilizing a literature review, survey, and case study analysis. The theoretical foundation was established through a comprehensive review of existing literature on Scrum and Kanban, supported by the construction of a comparative mind map. Survey data was collected from industry professionals to gather insights into the practical application of these methodologies. Additionally, a case study was conducted to provide a deeper understanding of the challenges and successes in implementing agile practices within a startup environment. Through our research, we identified key dimensions and components of Scrum and Kanban relevant to software startups, including values, principles/practices, team structure, events/cadences, and art

In today's rapidly evolving digital landscape, organizations face increasing pressure to deliver secure software systems while maintaining agility and speed. The integration of security practices into agile development processes, known as DevSecOps, has emerged as a critical approach to addressing this challenge. However, the successful adoption and adaptation of DevSecOps practices are often hindered by various organizational, cultural, and socio-technical factors. The purpose of this thesis is to investigate the complex interplay between push factors (institutional pressures), pull factors, (internal organizational dynamics), and organizational priorities that influence the success of DevSecOps adaptation across organizations. It explores how these factors shape the alignment of security practices with rapid development processes, with a particular focus on the role of norms and attitudes surrounding security. Employing a qualitative approach and drawing upon multiple theoretical perspectives, including Institutional Theory, Socio-Technical Systems Theory, and Organizational Culture Theory, this research provides a comprehensive understanding of the enablers and barriers to DevSecOps adaptation. The findings shed light on the key institutional pressures, such as regulatory compliance, industry standards, and customer demands, that drive DevSecOps adoption. Additionally, the study uncovers the internal organizational factors, including leadership support, cross-functional collaboration, and cultural barriers, that enable or hinder the integration of security practices into development processes. Furthermore, the research examines the role of organizational priorities, such as balancing speed and security, resource allocation, and risk management practices, in fostering an environment conducive to DevSecOps implementation. Significantly, the study highlights the crucial influence of norms and attitudes, such as security awareness, continuous learning, and overcoming

Background: Over the last few years, the principle of cross-docking has prominently spreadthrough the companies in which they try hard to make their supply chain channels efficientand achieve higher demands of the society. Studies claimed that inventory management remains to be challenge for professionals of supply chain as long-term processing times may result in considerable financial losses for firms. Aim: This research aims to evaluate the effectiveness of Hub-and-Spoke cross-dockingstrategy in inventory management by understanding the impact, outcomes or efficacy of its implementation. Methodology: This research has adopted qualitative research method to generate extensive data and deep insights to underlying factors behind organizations' decisions and behavior on the implementation of cross-docking concept. The interviews have been chosen as the main data collection method of this research because it has been used successfully in order to produce rich and detailed information about the participants in the supply chain management.The total sample size of the participants is 10. For instance, the research conducted interviews via In-person, Zoom and WhatsApp video calls. The researcher recruited supply chain managers including companies’ representatives, supply chain practitioners, logistic managers,inventory managers and related stakeholders responsible for executing and overviewing inventory management approaches within their firms operating in Sweden. Thus, individuals can offer useful information related to supply planning, implementing and optimising cross-docking operations within their organisations. Findings and Conclusion: The research has, however, led to the impact of the organizational culture on the sustainable Hub-and-Spoke cross-docking strategy with the participants, all agreeing on the role that culture plays in shaping the structure of the strategy in the long-term. Finally, organizational culture was considered to be the cornerstone s

In the world of software development, the most common framework is the agileframework. This framework first arose as a counter-reaction to waterfall development,mostly to incorporate user-centered design. But today the user-centered design and theuser are often overlooked. Still, some believe that the integration of user-centereddesign and agile development could help improve software development. Thisintegration is called user-centered agile design or UCAD for short. The main reason forconsidering UCAD over agile development is that software stands and falls with gooduser experience. Something that the user-centered perspective can help with.This thesis therefore sought to research the usage of UCAD in daily work with anautoethnographic approach. This meant that the author could use their experiencesfrom developing a piece of software as the basis of the research. This software was awebshop application for Quintus Technologies AB that acts as a way for their customersto buy spare and wear parts. The results were therefore in the form of a story told infirst-person perspective about the whole development period of about 20 weeks.This project found amongst other things that UCAD does hold some merit and theauthor also enjoyed this way of working. There were of course some problems, with thebiggest challenge being the act of trying to balance UX and functional tasks. To combatthis problem the notion of gear-switching was conceptualized. One specific factor thatwas brought up by earlier research was also found to be important. This factor was thetask factor and most importantly this factor brought up the consideration of tasks overroles. Whilst this project indicates that UCAD might be a good evolution of the agileframework there is still a lot more research that needs to be done mostly in differentsettings. Such as bigger teams and with more mature software. Whilst more research isneeded, this project still shows great potential for the UCAD framework.

Today, project managers play a key role in launching new products and managing for success. As leaders in the IT industry, project managers create strategies and orchestrate carefully designed action plans to complete projects successfully (Murch, 2001, p. 3). Agile methods in information technology (IT) project management have become increasingly common due to their ability to increase flexibility, improve teamwork, and accelerate business delivery but effectively implementing agile practices is often faced with significant obstacles to its full potential. This thesis will examine these barriers and discuss strategies from first-hand professionals to then suggest effective ways to address implementation of agile methods in IT project management when deemed possible. The thesis adopts a mixed methods approach, using an in-depth literature review, qualitative interviews with IT managers and team members, specifically examining the barriers for agile implementations to work in an IT project setting and understanding strategies that project managers would employ that prior research has not highlighted in-depth on. These various viewpoints will come from professionals formerly or currently in the field based in the United States, speaking on their personal project experience with agile methodologies. The thesis will help to serve to introduce new strategic plans that previous research has not specified on and answer the research questions later mentioned in the chapters. To address these challenges, the research will highlight several strategies that could be implemented for IT project teams looking to work with agile methods. Furthermore, this research emphasizes the importance of understanding these barriers from IT professionals as well as the strategies implemented by team members to adopt an agile project management approach. The findings of this study provide valuable insights for IT managers and organizations aiming to implement agile processes in their organizat

The agile working methods have been developed to meet the needs of flexibility, innovation and increased competitiveness of companies. These methods are characterized by a dynamic and self-directing approach to team management. After covid-19, hybrid work has become an established way of working, this means a combination of remote work and work in the office. Despite this, there is a lack of understanding of the challenges these methods can bring to communication within agile teams. The scrum master can be seen as a project manager within agile teams that work with the scrum methodology. One of the scrum master's most important tasks is to be responsible for communication within agile teams. The purpose of this study is thus to deepen the understanding of the communication challenges that scrum masters can face in a hybrid work environment where team members work from home as well as the office. Through semi-structured interviews with scrum masters, this study delves into experiences of communication challenges and how they deal with these challenges. Based on collected empirical evidence, conclusions can be drawn that scrum masters experience communication challenges linked to, spontaneous communication, digital tools, trust, community and problem solving. The overall conclusion in relation to the study's results is that the scrum masters are well aware of the challenges hybrid work entails and what measures they need to take to deal with them. Although the increasing trend of agile teams working within a hybrid context is relatively new, our results indicate that the scrum masters have undergone a learning process to deal with the communication challenges that have arisen. They have identified challenges with the hybrid way of working and implemented a range of measures to address these challenges., The agile working methods have been developed to meet the needs of flexibility, innovation and increased competitiveness of companies. These methods are characterized by a dynamic and self-directing approach to team management. After covid-19, hybrid work has become an established way of working, this means a combination of remote work and work in the office. Despite this, there is a lack of understanding of the challenges these methods can bring to communication within agile teams. The scrum master can be seen as a project manager within agile teams that work with the scrum methodology. One of the scrum master's most important tasks is to be responsible for communication within agile teams. The purpose of this study is thus to deepen the understanding of the communication challenges that scrum masters can face in a hybrid work environment where team members work from home as well as the office. Through semi-structured interviews with scrum masters, this study delves into experiences of communication challenges and how they deal with these challenges. Based on collected empirical evidence, conclusions can be drawn that scrum masters experience communication challenges linked to, spontaneous communication, digital tools, trust, community and problem solving. The overall conclusion in relation to the study's results is that the scrum masters are well aware of the challenges hybrid work entails and what measures they need to take to deal with them. Although the increasing trend of agile teams working within a hybrid context is relatively new, our results indicate that the scrum masters have undergone a learning process to deal with the communication challenges that have arisen. They have identified challenges with the hybrid way of working and implemented a range of measures to address these challenges.

In software engineering, technical debt (TD) has been widely investigated, but debt regarding social issues, people, and processes has not been explored as much. It should be noted here that we use nontechnical debt (NTD) as an umbrella term to cover social, process, and people debts. Although the number of studies on NTD in software is increasing, the majority of them are descriptive rather than rigorous, and there is no systematic development of cumulative knowledge. As a result, identifying the fundamental causes of NTD and the associated mitigation techniques in software engineering is challenging. Therefore, this study investigates the scientific evidence regarding NTD till date by conducting a systematic mapping review of software engineering research between January 2000 and October 2021. The search strategy resulted in 175 studies, 17 of which were identified as unique and relevant primary papers. The primary studies show that NTD and TD are inextricably linked. In addition, this study also captured a plethora of causes and mitigation strategies for managing NTD and thus makes four important contributions: (i) highlighting state-of-the-art NTD research; (ii) identification of the reported causes and mitigation strategies in the primary papers; and (iii) determination of opportunities for future NTD research.

Research on project management and new product development (NPD) identifies both strategy and tactics as important for success. Whilst there is a lot of attention on strategy, few studies address the role of tactics in NPD projects. In the pursuit for increasing organisational abilities to manage uncertainty, agile is increasingly getting traction in large firms. Both tactical activities and agile methodology deal with adapting to emergent challenges and handling uncertainty in projects. This motivated this study of how an agile transformation initiative influences tactical activities within NPD projects. The paper is based on a longitudinal case study of Volvo Car Group's autonomous car project. The case firm's transformation from waterfall to agile method provided the possibility to understand how tactical activities differ between the two methods. By using observations from the case, we argue that agile development method facilitates the use of tactics in NPD projects. © 2024 Inderscience Enterprises Ltd.. All rights reserved.

Psychological safety, a pivotal factor in team dynamics, has been proposed as a crucial determinant of success in agile software development (ASD) teams and learning. However, the extent of its influence within the domain of large-scale agile (LSA) software development teams remains underexplored. This research investigates the multifaceted dimensions of psychological safety within LSA teams, examining both its precursors and outcomes. This study conducted semi-structured interviews with software professionals actively involved in LSA projects within a Swedish software consultancy company. The findings underscore the intricate nature of establishing a psychologically safe environment within LSA teams, revealing it as a multidimensional construct necessitating a proactive leadership approach, fostering open communication, and cultivating an ecosystem of constructive feedback. The study highlights the critical importance of intentionally shaping teams to facilitate continuous learning, ensuring remuneration safety, and implementing a comprehensive onboarding process for incoming team members. By fostering psychologically safe settings, LSA teams enhanced teamwork dynamics, heightened job satisfaction, and facilitation continuous learning and development. Notably, the absence of such an environment exacerbates the phenomenon of brain drain, exposing the tangible consequences of overlooking this fundamental aspect of organizational culture. This study proposes avenues for future research directions, aiming to further unravel the nuances of psychological safety and its cascading effects within the realm of contemporary LSA software development context., NODLA

This study investigates how value stream management enables operational alignment between business and software development. The present paper employs a single-case study design within a Swiss-based bank and its IT subsidiary. Qualitative data were collected, analyzed, and synthesized, offering comprehensive insights into an organization operating under the value stream paradigm. Expanding on operational alignment theory, this research introduces a revised model for the operational alignment of software value streams. The derived model includes three aggregated dimensions: Seek Value, Foster Transparency, and Enable Proximity. The findings suggest that software value streams require product-centric teams, featuring designated roles at the interface between business and development. Moreover, value streams and the product team strive for transparency to disclose the actions and decisions of driving companies’ value. This study provides insights into the complex landscape of software development to align the operational dynamics between business and IT to pave the way for success.

This study demonstrates an effective systematic control design procedure by applying H∞ Loop-Shaping with a structured controller on an agile aerospace vehicle with a focus on automation. The gain-scheduled implementation is additionally described and tested with non-linear simulations, including a realistic moving point-hit scenario with guidance. The imposed robustness and performance requirements are met for most linear design points and for the non-linear simulations. The resulting autopilot design procedure is deemed effective in both the design procedure and implementation. It is subject to certain recommendations for improvement and extension., Aerospace Engineering

Reflective learning diaries can help students develop self-regulated learning (SRL), a critical skill for success. Forteachers such learning diaries can be a valuable tool for formative evaluation of SRL. However, there is limitedresearch on the use of reflective diaries in software engineering and information systems education. To address thisgap, we conducted a case study in which reflective learning diaries were used in a course. The goal of this research isto investigate the potential of using reflective diaries to formatively evaluate three key features of SRL: conceptions ofknowledge, conceptions of learning, and strategies for monitoring and regulating learning. Our findings suggest thatreflective diaries is a valuable tool for formative evaluation of SRL in software engineering education. Reflection onlearning experiences helps students develop self-awareness of their SRL skills and identify areas for improvement.Instructors can use this information to provide students with targeted feedback and support. By using reflective diariesto promote dialogic feedback, instructors can help students to develop a deeper understanding of their own learningand to become more effective self-regulated learners. The study conclude with lesson learned that provide practicalrecommendations for educators who are swiftly moving towards online teaching.

This paper explores the relationship between self-organisation andtailored roles in large agile software development teams. The casestudy examines a Swedish IT company that has introduced the roleof “Security Master” in Scrum teams. The teams are developing avery large and secure 5G solution. Twenty semi-structuredinterviews were conducted and deductively analysed. The resultsshed light on the Security Master role, its need, responsibilities andimpact on secure coding. The paper concludes with a discussion oflessons learned and recommendations for future research in thecontext of large, security-sensitive projects., NODLA

The TNVS HR 4 is a module designed specifically for the Philtransure System, one of the proposed solutions that TNVS Company can utilize. Its main focus is accurately profiling employees, including personal data information, qualifications, salary, and rates. The module consists of four parts: Core Human Capital Management, Compensation Planning and Administration, HR Analytics and Payroll.   Core Human Capital Management involves practices an organization uses to recruit, manage, develop and optimize its employees to increase their value to the company. Compensation Planning and Administration manage employee salaries based on their skill set, knowledge, and experience rather than their job title or position. Employees are motivated to strive towards their preferred salary level. HR Analytics measure and collect current data, including employee satisfaction and performance, to make informed decisions. Payroll involves calculating gross pay, mandatory contributions and deductions, withholding taxes, net pay, and issuing employee paychecks.   The Agile methodology was used to avoid lengthy software processing times due to errors in the early stages of system development. This method relies on keeping accurate employee records and is an iterative and incremental software approach to transport software development. It involves collaborative efforts to focus on flexibility and speed to meet the needs of the Admin, Manager, and Staff. &nbsp

The Registrar is the official responsible for keeping a register of official records. A registrar often manages registration requests, schedules and maintains class lists, enforces class entry and exit regulations, and maintains a permanent record of grades and marks. In schools with selective admission requirements, a student’s involvement with the Registrar’s formal acts does not begin until after admission. The Registrar’s duty at Bestlink College of the Philippines – Bulacan Campus is no longer just that of a record keeper. Data analysis and management for school planning and decision-making have progressed beyond storing and protecting student information.    The Agile Methodology is used by the scrum master, who will give a task to all group members, and the team will focus on the task and improve their skills. By making this system, the Administrator will have access to the full student information details.    The project outcome revealed that a program was developed that can meet the needs of the students and employees of the school. It can be used to improve the system in storing information of the students. This contains the type of bundle and all the package development, writing, and testing/validating. This project is expected to have an outsourced unit.   Future researchers will gain from this study because it can provide them with crucial data that will aid in their understanding of the proper flow and interaction between students and schools. This study discusses the accurate way of storing students’ information. They discuss valuable information like grades, year level, and course. &nbsp

The business case for Philtransure's Logistic 1 (TNVS) Transport Network Vehicle System outlines the project's benefits, recommendations, reasoning, and how it will address current business challenges. It also details project objectives, performance metrics, assumptions, constraints, and alternative options. Logistics are critical to a successful supply chain as they aid companies involved in product manufacturing, warehousing, and delivery to increase sales and profitability. Even a small error in logistics can cause production delays and financial losses.   The approach used is agile methodology, which is designed for rapid development. The suggested system development process includes Requirement Analysis, Design Document, Prototype, Iteration, Demo and Feedback, fault detection and resolution, and Production and Technical Support. This methodology is widely used and highly recommended for guiding the development team towards their desired output system. To facilitate their communication, users can create and link with other departments for their transactions and information needs. Users need to have transparency when interacting with other departments.

The importance of effective monitoring and data collection in Transport Network Vehicle Services cannot be overstated. The Philtransure system has been proposed to address the current limitations, which aims to enhance the monitoring processes and gather more data on drivers and commuters.    In software development, the Agile Methodology is often employed to ensure that the development process is broken down into manageable phases. This approach allows for continuous evaluation and adjustment throughout the project's lifecycle, including planning, analysis, design, testing, maintenance, and implementation. Once the project completes an iteration, gathering feedback from stakeholders is crucial to ensure that the end result meets their expectations. This step is significant in avoiding plagiarism and ensuring originality in the final product.     &nbsp

This study focuses on the Logistic II of "Philtransure Transport Network Vehicle System". Logistic II is a systematic process that manages the flow of TNVS resources, from their acquisition storage to eventual transportation to their destination. The project has several sub-modules, including Fleet Management, Document Tracking System, Vehicle Reservation, Vendor Portal, and Audit Management, which ensure the accuracy of all transactions, tasks and activities. Fleet Management allows users to track vehicle movement, while Vehicle Reservation organises using vehicles for transportation or other purposes. The Document Tracking System monitors and traces all company documents to take proper action. The Vendor Portal lets the company view all procurement approvals and enables company transactions.   The development team used an Agile approach to build the proposed system. They conducted a requirement analysis, gathered data, and held a formal consultation to develop the proposed system's idea. The Document Design and Prototype phase planned a solution for the problems identified in the requirements. Iterations, demos and feedback in this phase ensured that the specific needs and wants of the company were met. The Identify Defects and Resolve Bugs phase is determined when the function reaches the requirement. Finally, the Production and Technical Support phase ensured the proposed system was fully functional.

TNVS is a ride-hailing service that operates on a pre-arranged basis, where the driver approves the commuter's request. This service is particularly beneficial for Filipinos who do not own cars and rely on well-known modes of transportation used in other countries. Despite the cultural significance of taxis, they have significantly impacted society.   Agile methodology is a short-term project management approach that breaks down projects into phases. It involves stakeholders' ongoing engagement and continuous development at every stage. The team plans, executes, and assesses as they progress through the project. This method helps teams become more efficient and effective, and it is also flexible and adjustable for the project's development timeline. TNVS Core 2 used this approach to manage their system's development timeline by dividing the project into two sprints, each lasting 2-3 weeks, to maximize scheduling and organize daily tasks. In summary, TNVS Core 2 utilized agile methodology to ensure timely and organized system completion by dividing it into several phases.

Our platform, the Transport Network Vehicle System, connects drivers who use their vehicles with clients to provide transportation services for compensation. We also have a Financial Management System that helps organisations monitor their assets, revenue and costs to maximise profits and ensure long-term success. This system improves the accuracy and flexibility of financial records, which is crucial for supporting economic growth.   We used an agile methodology to develop our proposed system. The project team gathered data for requirement analysis and conducted interviews to develop a solution. We then designed a prototype and received feedback to identify bugs and fix issues. This process allowed us to tailor our solution to meet the precise needs and desires of the company. &nbsp

Bureaucratic constraints often impede organizations from implementing timely changes. This issue is particularly prevalent in aviation degree programs, specifically in the context of curriculum change processes. Despite the widespread adoption of agile methods in project management, their application in various aspects of project execution, such as curriculum modifications in higher education institutes, remains limited. This case study aims to assess the utilization and impact of agile methods in aviation degree programs, focusing on curriculum changes. The examined programs face challenges imposed by accreditation agencies and the Federal Aviation Administration (FAA). Data collection involved surveys, interviews, and reviews of institutional procedures. The study found three major themes relating to the current curriculum change processes: Organizational efficiency and effectiveness, industry dynamics, and aviation education standards. These themes help answer the three research questions posed relating to agility utilization, current curriculum change processes and their effectiveness, and sustainability of the degree programs as a result.

This thesis investigates the socio-technical factors influencing the use of Agile methods within project teams in local government organizations in the Netherlands, aiming to develop a practical framework to enhance Agile practices. The primary research question is: How can project teams in local governments stimulate the use of Agile methods? To answer this, the study addresses three sub-questions: (1) What team archetypes represent the typical use of Agile methods in local governments? (2) WWhat barriers and drivers towards the use of Agile methods are experienced by the teams? (3) How do different types of (Agile) team management impact the perceived performance by team members? Data was collected through qualitative methods, including interviews with team representatives of 15 teams across three local government organizations, and surveys with team members from one of these government organizations. The study categorizes teams into archetypes based on their Agile methodologies, reason to change, experience levels, and management support. Key barriers include lack of management support, lack of focus, lack of knowledge, unclear roles, lack of alignment and organizational resistance to change. Important drivers for Agile adoption include Agile mindset, Agile coaching, dedicated key roles, dedicated management and freedom to experiment and structure. No significant difference in perceived performance was observed between team archetypes, indicating that perceived performance may be influenced by a broader range of factors beyond the scope of this study. The theoretical contribution extends the understanding of Agile adoption in public sector contexts, while the practical framework provides actionable steps for local government teams to navigate barriers and leverage drivers. Future research should broaden the scope to include diverse local government contexts, integrate quantitative data, and explore the long-term impacts of Agile practices and the application, Management of Technology (MoT)

The Agile Software Development Manifesto prioritizes people and relationships over procedures and equipment. However, managers can more effectively track the development of software projects by using software tools. An analysis of agile project management tools is presented in this report. This study on automation in agile projects could be beneficial to project managers. In the modern IT world, efficient software project management is typically the most crucial component in the success of numerous businesses, as well as their managers and engineers. Software managers oversee, direct, and oversee numerous projects at once. Agile project management insights are offered by the study. In order to comprehend the supported features that could affect their choice, the goal is to investigate and identify the top Agile project management solutions utilized by software project management teams and their managers. This paper examines a case study of a software project that automated software agile projects through the use of several software agile project management technologies. Automation of project planning, scheduling, and estimating can not only improve project success rates but also save project costs, completion times, and resource requirements. Agile project automation improves the likelihood that a project will be completed on time. Ultimately, the sum of these factors raises the software project success rate.

In every industry manual working process is ending and moving to the software technology. Rapid change in the technology software development organization need to update and improve their development process. In software programming techniques agile practices focus on the client comfort and responsive to change. Retrospective practices are important activities for process improvement in Agile software development as they increase the collaboration between the team members. With the help of these retrospective practices, challenges and problem in the development process are identified and suitable solutions are provided. Team velocity are managed according to the progress of the previous sprint. Retrospective practices are initially difficult for new team and take about 3-5 meeting to make mindset on the retrospective meeting. In this research a case study is conducted to analyze whether retrospective practices are followed by the Pakistani software industry. Our analysis shows that retrospective practices are followed by the Pakistani software industry for process improvement but they have both positive and negative impact on the software quality and improvement of the team. In Pakistani industry, various retrospective practices are followed according to software quality requirements but mostly teams are satisfied by the practices followed in their teams.

Businesses within the physical product domain seek to transform the way they manage new product development, through more flexible approaches. Traditionally, this was done through a fixed approach, characterized by linear and rigid workflow. In this context, however, a complete transition over to a flexible approach, characterized by iterative workflow and adaptability, is not feasible in most cases. To increase flexibility more suitably, hybrid approaches emerged, which combine elements from fixed- and flexible project management approaches. Existing literature lacks in the area of suitability assessment for when and how to combine these two approaches. Therefore, this exploratory study set out to identify factors that affect the suitability of any of the three approaches, fixed, flexible, or hybrid. The thesis took a qualitative approach, collecting data from semi-structured interviews and company documents. Interviewees included project managers and developers. Thematic analysis was used for data analysis. The findings revealed a total of 19 relevant factors within four primary areas, Communication & Engagement, Knowledge & Principles, Contextual Constraints, and Risk & Change Management. Stakeholder- and Team Communication and engagement were shown to be highly influential and recurrent factors. The practical contributions of the thesis aim towards increasing the assessment capabilities amongst managers, trying to determine the suitability of any particular project management approach. By evaluating the factors, conditions regarding the characteristics of a project can be established and more appropriate management approaches can be adopted., Tillverkande organisationer inom den fysiska produkt-domänen som strävar efter att förbättra sättet de hanterar utvecklingen av nya produkter, kan vända sig till flexibla metodiker. Traditionellt sett gjordes detta genom mer fasta metodiker som kännetecknas av linjära och stela arbetsflöden. I denna kontext är det oftast inte optimalt att helt övergå till ett flexibelt arbetssätt, som kännetecknas av iterativa arbetsflöden. För att öka flexibiliteten på ett mer lämpligt sätt har hybrida metoder utvecklats, vilket kombinerar element från både fasta och flexibla projektledningsmetoder. Den befintliga litteraturen brister när det kommer till lämplighetsbedömning för när och hur organisationer ska kombinera dessa två. Därför syftar denna explorativa studie till att identifiera faktorer som påverkar lämpligheten för någon av de tre arbetssätten: fast, flexibel eller hybrid. Studien använde sig av en kvalitativ forskningsmetodik och samlade in data genom semistrukturerade intervjuer och företagsdokument. Intervjupersonerna inkluderade projektledare och utvecklare inom studierelevanta områden. Analys av samtlig data skedde genom metoden Tematisk analys. Resultaten visade på totalt 19 relevanta faktorer inom fyra huvudsakliga områden: Kommunikation & Engagemang, Kunskap & Principer, Kontextuella Begränsningar samt Risk- & Förändringshantering. Intressent- och Team Kommunikation & Engagemang visade sig vara mycket påverkande och återkommande faktorer. Studiens praktiska bidrag syftar till att öka förmågan hos företagsledare att bedöma lämpligheten hos en specifik projektledningsmetod. Genom att utvärdera faktorerna kan förhållanden gällande ett projekts karaktärsdrag fastställas och mer lämpliga projektledningsmetoder tillämpas.

The study's primary objective is to investigate the obstacles associated with agile implementation in ICT public services and the importance of government facilitation and removal of these obstacles. It employs a case study strategy which includes data collection and analysis methods. The case study's purpose is to investigate the challenges of implementing the agile methodology in Kuwait's public services, and the findings are presented at the end. Thus the study is formulated around the following research questions: “What are the challenges of implementing agile methodology into the Kuwait ICT public services?” and “What are the recommendations for the government side to facilitate adopting agile transformation?”. In order to gain a better understanding, the study uses the appropriate approach for producing thematic analysis results in a table of themes, categories, and codes covering ICT managers and decision-makers in the public and private sectors who participated in semi-structured interviews. The conclusions are based on the data collected and analyzed, and the study provides evidence to support the final recommendations. The study concludes that implementing Agile methodology in Kuwait's public services faces several challenges, including cultural or regulation factors. The study provides recommendations for the Kuwaiti government to facilitate adopting Agile transformation, including developing a clear vision, providing training and support, and creating a culture of trust and collaboration. The findings also suggest that the Kuwaiti government can adopt an agile methodology to provide public services in the IT domain with faster response and feedback while changing the bureaucratic culture and ancient rules to be more adaptive and reasonable.

This thesis explores the opportunities and challenges of integrating recent Natural Language Processing (NLP) Artificial Intelligence (AI) advancements into IT project management and delivery (PM&D). Using a qualitative design through hermeneutic phenomenology strategy, the study employs a semi-systematic literature review and semi-structured interviews to delve into NLP AI's potential impacts in IT PM&D, from both theoretical and practical standpoints. The results revealed numerous opportunities for NLP AI application across Project Performance Domains, enhancing areas such as stakeholder engagement, team productivity, project planning, performance measurement, project work, delivery, and risk management. However, challenges were identified in areas including system integration, value definition, team and stakeholder-related issues, environmental considerations, and ethical concerns. In-house and third-party model usage also presented their unique set of challenges, emphasizing cost implications, data privacy and security, result quality, and dependence issues. The research concludes the immense potential of NLP AI in IT PM&D is tempered by these challenges, and calls for robust strategies, sound ethics, comprehensive training, new ROI evaluation frameworks, and responsible AI usage to effectively manage these issues. This thesis provides valuable insights to academics, practitioners, and decision-makers navigating the rapidly evolving landscape of NLP AI in IT PM&D.

With the introduction of the Agile Manifesto, Lean Software Development, and Dev-Ops, documentation has become lower in quality and lesser in quantity leading to knowledge evaporation. The Agile Manifesto values working software over comprehensive documentation, and Lean Software Development considers everything that does not contribute to customer value as waste. In Dev-Ops, documentation is primarily found in infrastructure-as-code to keep up with continuously changing legislation and demands for fast time-to-market. Next to the developments above, another issue causing knowledge evaporation concerns the reluctance of software developers to write down information about a software product. In general, software developers and other stakeholders dislike reading documentation; in short, TL;DR. New team members must invest substantial time in comprehending the intentions behind the source code, particularly understanding the reasons for its functioning and extracting insights into how it operates, all directly from the source code itself. The source code alone cannot reveal design decisions or their rationale. Consequently, preserving knowledge necessitates primarily capturing design decisions, rationale, architecture and justification. To mitigate knowledge loss, we formulated three primary research questions that subsequently informed the development of a framework consisting of three approaches and their corresponding artifacts. The first question poses challenges due to culture, loss of focus, and a wide array of tools and processes. The second question examines the characteristics of gls{csd}, including cultural traits defined by values, principles, practices, and processes, life cycle attributes of constant change, systematic challenges like lack of control, and the impact of bugs and new features. The third research question proposes a framework with approaches and artifacts. The approaches in the framework are `Just Enough Upfront', ‘Executable Documentation'

Project management is a complex topic that has been studied for several decades. With the constant change in the business andtechnological environment, it is important to know future trends to support the development of organizations and promote success in their projects, in addition to preparing professionals for future demands. Therefore, this article seeks to identify trends and opportunities for future practices in project management for the coming years in the perception of experts in Brazil. In this way, the study contributes to having an integrated view of project management research in terms of its evolution and thematic trends for an understanding of future directions. In this sense, the evidence indicated that there is a strong concern for people in the business environment due to the influence of technology, which creates a challenging and connected environment. Migration to agile and hybrid methodologies is a strong trend in Brazil. In addition, professionals need to seek constant updating and development to meet current demands, as management practices are spreading to all areas of society, creating new job opportunities for trained professionals. Skills required include people management, leadership, behavioral skills, technology, business acumen and change management. This study can serve as a source of insight into trends and challenges in the field of project management, offering guidance for professionals to prepare to lead change and promote success in their organizations and projects, A gestão de projetos é um tema complexo que tem sido objeto de estudos há várias décadas. Com a constante mudança do ambienteempresarial e tecnológico, é importante conhecer tendências futuras para apoiar o desenvolvimento das organizações e propiciar o sucesso em seus projetos, além de preparar o profissional para as demandas futuras. Portanto, este artigo busca identificar as tendências e oportunidades de práticas futuras em gerenciamento de projetos para os próximos anos na percepção de especialistas doBrasil. Desta maneira, o estudo contribui para se ter a visão integrada da pesquisa em gerenciamento de projetos em termos de sua evolução e tendências temáticas para uma compreensão das direções futuras. Neste sentido, as evidências indicaram que há forte preocupação com as pessoas no ambiente empresarial devido à influência da tecnologia, que cria um ambiente desafiador e conectado. A migração para metodologias ágeis e híbridas é uma tendência forte no Brasil. Além disso, os profissionais precisam buscarconstante atualização e desenvolvimento para atender às demandas atuais, pois as práticas de gerenciamento estão se difundindo em todas as áreas da sociedade, criando novas oportunidades de trabalho para osprofissionais capacitados. As capacidades exigidas incluem gestão de pessoas, liderança, habilidades comportamentais, tecnologia, visão de negócio e gestão de mudanças. Este artigo pode servir como fonte de insightssobre as tendências e desafios no campo de gestão de projetos, oferecendo orientações para os profissionais se prepararem para liderar a mudança e promover sucesso em suas organizações e projetos.

Esta colección de documentos proporciona un resumen de los resultados obtenidos en el proyecto UVagile durante el curso 2022-2023: - Presentación general del proyecto “UVagile 5.0”, en el marco del Laboratorio de Innovación Docente de la Universidad de Valladolid (LIDUVa) - Artículo y presentación del trabajo “Una metodología basada en prácticas ágiles para la realización de Trabajos Fin de Grado”, publicado en las Actas de las Jornadas sobre Enseñanza Universitaria de la Informática (JENUI): https://aenui.org/actas/. - Póster “Hacia el examen como instrumento de aprendizaje y evaluación”, presentado en la VII Jornada de Innovación Docente de la Universidad de Valladolid - #JIDUVa., Departamento de Informática (Arquitectura y Tecnología de Computadores, Ciencias de la Computación e Inteligencia Artificial, Lenguajes y Sistemas Informáticos)