Inom projektledning har olika metoder och agila arbetssätt utvecklas. Det har dock funnits frustration över separerande silostrukturer inom mjukvaruutveckling. DevOps har utvecklats som ett sätt att bemöta detta och istället sammankoppla olika funktioner som utveckling och operations. DevOps har effekter på ett team men det finns inget standardiserat tillvägagångssätt för dess implementering. Det behövs därför mer forskning kring implementeringsprocessen av DevOps. Det kan även vara av intresse att undersöka vilka de medföljande effekterna kan vara. Syftet med detta arbete är studera genomförandet av DevOps implementering inom IT-konsultbranschen och på vilket sätt det påverkar ett team. Det här arbetet har bedrivits som en abduktiv studie där en fallstudie genomförts. För att uppfylla arbetets syfte och besvara forskningsfrågorna har litteraturstudier och intervjuer genomförts. Insamlad teori och empiri har diskuterats och analyserats för att formulera slutsatser och rekommendationer.  En formulerad slutsats är att varje enskild implementering av DevOps behöver följa ett eget anpassat genomförande där syfte och innebörd tydliggörs. Faktorer inom kommunikation, automation, ansvar, förändringsvillighet och samarbete har också inverkan på implementeringen och de effekter teamet kan uppleva. Det kan även konkluderas att både fördelar och nackdelar kan påverka teamet men nackdelarna framstår ofta vara begränsade till implementeringens uppstart. Det praktiska bidraget utgörs av rekommendationer för implementeringen såsom att till exempel ha en dedikerad person och utbildning inom DevOps. / Within the field of project management different methods and agile approaches have emerged. However, dividing silo-structures have created frustration within software development. DevOps has surfaced as a way to address this and instead connect different functions such as development and operations. DevOps affects teams but there is no standardized approach for its implementation. Therefore, more research around the implementation process of DevOps is needed. Also, investigating what the accompanying effects could be, is of interest. The purpose of this thesis is to study the implementation of DevOps within the IT consultant industry and what impact it has on a team. This thesis was executed with abductive reasoning where a case study was carried out. To fulfill the purpose and answer the research questions literature review and interviews have been performed. Collected theory and empirical material have been discussed and analyzed in order to formulate conclusions and recommendations.  One formulated conclusion is that each implementation of DevOps needs to follow its own adapted execution where the aim and essence are clarified. Factors regarding communication, automation, responsibility, willingness to change and collaboration also impact the implementation and the effects experienced by the team. It can also be concluded that both benefits and limitations can affect the team yet, the disadvantages often appear to be contained within the start of the implementation. A practical contribution comes from recommendations for the implementation, such as having a dedicated person and education within DevOps among others.

Background Using Microsoft Platforms as a base for creating a software solution with a web front-end, the motives and research behind the technology was explored. This study identified functionalities that are split across existing media-related applications where neither has all to develop and evaluate a novel solution with useful features for sorting and indexing media. Aim Produce a solution for the development of an application with available technology, provide research and motives for chosen implementation strategies, and an evaluation of the solution. Method Design and creation was used as a strategy for the purpose of developing and evaluating a software solution. A literature review was used as data collection method, serving as motive and research behind the development of a software solution. An evaluation on accessibility, functionality and performance was chosen to estimate the worth of the proposed solution, and to be compared with Kodi and Squeezebox. Results The proposed solution suffered in performance and accessibility. In terms of functionality, it has the edge by being cloud-hosted,having offline support and supporting multiple media types. Kodi excelled in supporting more media types and formats, with an accessibility score close to Zavorite. Squeezebox excelled in performance. Both Squeezebox and Kodi has the edge in being able to playback media, a feature Zavorite does not offer. Conclusions Zavorite is a prototype evaluated alongside product-ready applications. The areas where Zavorite is lacking compared to Kodi or Squeezebox, such as performance is made up for due to being a PWA. For accessibility, the evaluation showed what should be improved for subsequent prototypes. For functionality, despite the prototype only showcasing two media types, there is the possibility of adding more with an additional row in a database table. Zavorite can be considered a combination of Kodi and Squeezebox, with user experience improvements as a PWA, limited to sorting and indexing media.

El presente trabajo de investigación identifico que el uso de las practicas Lean para mejorar la rotación de inventario y proceso de despacho en una empresa distribuidora de pinturas en polvo permitirán mejorar los indicadores clave de gestión en una MYPE distribuidora de pinturas en polvo y por consiguiente permitirá disminuir el impacto económico que las malas prácticas generan. El trabajo contiene 4 capítulos. El primero revisa el estado del arte y Marco teórico. El segundo capítulo ejecuta el diagnóstico para lo cual describimos la organización estudiada para identificar el problema, analizar sus causas y alternativas de solución. El tercer capítulo contempla la propuesta de mejora mediante el análisis y pronóstico de la demanda, usos de herramientas como el EOQ y el MRP para una correcta gestión de inventarios, además usa la estandarización de procesos y 5S. El cuarto capitulo corresponde a la validación de ingeniería y económica. Finalmente, la conclusión sostiene que gracias a la implementación de las herramientas mencionadas se logra disminuir significativamente el impacto económico que tiene como consecuencia el exceso de costos, asimismo se logran valores adecuados en los indicadores claves de control. / The present research work identified that the use of Lean practices to improve the inventory rotation and dispatch process in a powder coating distribution company will improve the key management indicators in a MYPE distributor of powder paints and therefore will reduce the economic impact that bad practices generate. The work contains 4 chapters. The first reviews the state of the art and theoretical framework. The second chapter executes the diagnosis for which we describe the organization studied to identify the problem, analyze its causes and alternative solutions. The third chapter contemplates the proposal for improvement through the analysis and forecasting of demand, uses of tools such as EOQ and MRP for a proper inventory management, also uses process standardization and 5S. The fourth chapter corresponds to engineering and economic validation. Finally, the conclusion holds that thanks to the implementation of the aforementioned tools, it is possible to significantly reduce the economic impact that excess costs have as a consequence, as well as adequate values in the key control indicators. / Trabajo de Suficiencia Profesional

About 1.5 years after the first Covid-19 lockdown, it is clear there will not be an "as before” anymore. New standards have been established among project managers in the German news media industry and hybrid and virtual working has become the New Normal. In this study, nine project managers from German news media organisations have shared their experiences on the Covid-19 pandemic. The main takeaway is that pragmatism and agile principles have been beneficial for the project managers in uncertain times. The role of a successful project manager has seen a shift towards being a facilitator who gives structure to the team but enables it to work more efficiently through communication and building strong trust. / Runt 1,5 år efter den första Covid-19-lockdown står det klart att det inte kommer att bli något "som förut" längre. Nya standarder har etablerats bland projektledare i den tyska nyhetsmediebranschen och hybrid och virtuellt arbete har blivit det Nya Normala. I den här studien har nio projektledare från tyska nyhetsmedieorganisationer delat med sig av sina erfarenheter av Covid-19-pandemin. Den viktigaste slutsatsen är att pragmatism och agila principer har varit till nytta för projektledarna i osäkra tider. Rollen som framgångsrik projektledare har förändrats till att bli en facilitator som ger teamet struktur och som gör det möjligt för teamet att arbeta mer effektivt genom kommunikation och att bygga upp ett starkt förtroende.

Background. With the growing trend in using Agile development method in thesoftware industry, the importance of "people" in the software development processhas risen up. As much as the technical aspects contribute to a better software processand products, it is ultimately people that make the software. Hence, studying thehuman factors in the perspective of software development can be considered significant especially in studying the effect of these factors on performance of the teams intoday’s Agile based development scenario. Objectives. The objective of this thesis is to identify the individual based humanfactors that influence the software team performance.Methods. For this project, we use the methods systematic literature review(snowballingstudy) and survey to identify and understand the influence of the human aspects onteam performance and possibly arrive at an understanding of these factors tendingtowards high-performing Agile teams. Results. The results of the thesis indicate that there are 19 factors that impactthe team performance. The results show that personality, professional knowledge,formal education, leadership style, work experience etc., are all impacting factorsof the performance of a team. Though, personality was the most mentioned factorfollowed by communication and professional knowledge. These results when weretried to verify through a survey showed similarities as well as some aberrations tothe results obtained from SLR. According to survey, professional knowledge has thehighest importance while personality scored lower than expected in the practitioner’sperspective. Although, many factors had similar degree of importance as for the results from both methods. Conclusions. It is essential to study the impact of the individual based factors onteam performance and several factors can be indicated that show their effect on theperformance of a team. Essentially, the study of the factors can be used to buildprocesses and teams focused to better their performance which can ultimately leadto better softwares. Individuals contribute to the team and studying the factors thatrely on their characteristics helps understand the team as a whole in a better waywhich can in-turn aid in improvement.

Der betriebliche Einsatz von Smart Glasses zur Unterstützung von manuellen Dienstleistungsprozessen bietet viele Vorteile, die mit anderen Technologien nicht erreicht werden können. Insbesondere im Bereich der Logistik kann von der Informationsversorgung bei gleichzeitiger Mobilität Gebrauch gemacht werden. Um dieses Potenzial auszunutzen, bedarf es allerdings Softwarelösungen, die auf die jeweiligen Anforderungen zugeschnitten sind. In dieser Forschungsarbeit wird daher untersucht, wie Smart-Glasses-basierte Informationssysteme zur Unterstützung der Logistik zu gestalten und zu implementieren sind. Die Forschungsarbeit folgt dabei zwei Zielen: (A) Die Unterstützung von Logistikprozessen durch Smart-Glasses-basierte Informationssysteme wird im Hinblick auf Anforderungen, Herausforderungen und Gestaltungsprinzipien untersucht, und (B) wird der Entwicklungsprozess zur Gestaltung und Implementierung von derartigen Informationssystemen im Rahmen eines Forschungsprojekts konzipiert und evaluiert. Das Vorgehen wird durch methodische Betrachtungen von Gestaltungsanforderungen und -prinzipien geleitet und entspricht so dem gestaltungsorientierten Forschungsansatz der Wirtschaftsinformatik. Die genauere Beantwortung der gestellten Forschungsfrage erfolgt in drei Schritten: (1) Methoden zur Initiierung von agilen Softwareprojekten und der Integration von Softwareentwicklung und -betrieb werden basierend auf der Wissensbasis agiler Methoden, Praktiken und Ansätze abgeleitet, (2) Grundlagen zur thematischen Fokussierung auf die Technologie Smart Glasses und die Anwendungsdomäne der Logistik werden durch multimethodische Studien geschaffen, und (3) werden entsprechende Systeme zur Mitarbeiterunterstützung instanziiert, evaluiert und die Forschungsergebnisse in ein Vorgehensframework zur Durchführung von Implementierungsprojekten überführt. Die vorliegende Dissertation trägt somit zur Wissensbasis der gestaltungsorientierten Wirtschaftsinformatik durch die erreichten Erkenntnisse zur Initiierung und Durchführung von Softwareentwicklungsprojekten zur Unterstützung von betrieblichen Prozessen durch Smart-Glasses-basierte Informationssysteme bei. Darüber hinaus bietet die Arbeit durch die bewusst praxisnahe Orientierung mit dem generierten Gestaltungswissen einen Mehrwert für Praktiker aus den betrachteten Bereichen, insbesondere für Stakeholder für die Einführung mobiler Informationssysteme in betrieblichen Umfeldern.

The software development business today is a land of constant change. The change requires the organizations who operate within this business to be flexible and quick to respond. This has led to multiple agile organization methods being developed, one of them is DevOps. A cornerstone in DevOps is self-selection - a method for assembling teams. This method gives hope of less administration, autonomy in teams and increased performance. In this essay we investigate the promises - the challenges and the possibilities - of self-selection. The case in this essay is IFS - a big software development company, implementing self-selection department by department also facing the challenges of combining traditional project values with the short iterations of an agile method. Our qualitative study investigates which the main challenges and possibilities are. We also investigate how these findings should be managed. How could the diversity, team size and autonomy be enhanced or diminished? We found that some parts of the case, and practice, were like our prior literature - but some were not. For example, the feeling of being in homogeneous teams were not always negative, and the majority of those taking part of the self-selection at IFS said they chose team by assignment - not social network as the prior literature said. Our conclusion reveals that there are several different factors to consider when having selfselection implemented in a traditional project environment. The main areas where we have found possible improvements are Team Choice, Team Diversity, Overlapping Assignments, Experienced Ownership, Management Influence and Performance.

This study focuses on agile systems development teams which work remotely during the COVID pandemic. Purpose: To identify the missing topics in informal communication and the relationship between them and team collaboration. Method: Survey is used to collect nominal data, ordinal data and qualitative data of text. 101 people participated in the survey. Analysis: An independent T-test, Spearman's rank correlation and content analysis are conducted. Result: There is a lack of discussion topics on personal information (e.g. a deeper insight into a person’s private life), social conversations (e.g. greetings and questions about weekend plans), support (e.g. giving tips and asking for help) and complaints (e.g. frustration regarding work) when they are teleworking during the COVID pandemic. Conversational topics on personal information, social conversations, support and complaints have a weak positive association with teamwork. Topics on personal information and social conversations are more strongly associated with teamwork than topics on support and complaints. The most striking results are the lack of social conversations in the age group between 30 and 39 years and those whose years of experience are between one and three years. Discussion and Conclusion: It is possible that the magnitude of topic shortages changes depending on the age and years of experience of team members, which may be a factor in how well team collaboration works. It may also become a factor determining the quality of team collaboration that causes teams to take proactive steps to increase the amount of informal communication. This study proposes to increase the amount of topics of personal information and social conversations and take serious measures to increase the amount of social conversations if the team is based on many team members whose age is between 30 and 39 years and whose years of experience are between one and three years.

No description available.

IT-projekt har misslyckats till hög grad under väldigt lång tid, studier visar på att uppemot 80% av alla IT-projekt anses vara misslyckade. Det har gjorts studier som visar på att agila metoder, såsom DevOps, kan vara lösningen till att fler IT-projekt ska lyckas. Syftet med denna studie är att bidra till förståelse för hur risker relaterade till IT-projekt har sett ut mellan 1990–2020, samt undersöka om metoder såsom DevOps är rätt väg att gå för att reducera misslyckade IT-projekt. I denna studie kartläggs de vanligaste orsakerna till misslyckade IT-projekt genom att kategorisera risker identifierade i forskning från 1990 till 2020. Detta görs och presenteras genom en litteraturstudie. Denna litteraturstudie resulterar i en överblick över hur litteraturen för de vanligaste riskerna sett ut över 30 år. Kartläggningen visar att tidigare studier mellan 1990 -2010 haft en bred spridning kring risker relaterade till IT-projekt bland samtliga kategorier. De senare åren, 2010–2020 har fokus i litteraturen legat mot lednings-, process samt personalrelaterade risker, något som även får stöd av respondenterna. Vi har även studerat DevOps och genomfört två semistrukturerade intervjuer med respondenter som har erfarenhet av DevOps, agila metoder och att driva IT-projekt. Resultatet av studien är tydligt, teori och empiri är väl överens om att agila metoder är rätt väg att gå. DevOps anses av respondenterna som en effektiv metod att använda för att nå fler lyckade IT-projekt. De två respondenterna verifierar även de riskkategorier som tagits fram i litteraturstudien och bekräftar att det är dessa som är aktuella i IT-projekt. / Literature shows that IT-projects have failed to a large extent for a long time, studies shows that up to 80 % of all IT-projects are considered as failed. There are studies that shows that agile methods, such as DevOps, can be the solution for more IT-project success. The purpose of this study is to contribute to an understanding of what risks related to IT projects that has been identified in literature between 1990-2020 and investigate if methods such as DevOps is the right way to reduce IT-project failure. This study maps all the most common causes to failed IT-projects by categorize the most frequent risks identified in research from 1990 to 2020 and is performed and presented by a literature study. This literature study results in an overview of the literature of the most frequent risks occurred in studies from the last 30 years. The overview identifies that studies between 1990 to 2020 has a range between risks related to IT-projects in all categories. In the most recent studies, from 2010- 2020, focus in research points to management-, process and personnel-related risks, which is also supported by the respondents. We have studied DevOps and completed two semi structured interviews with respondents that have experience of DevOps, agile methods and managing IT-projects. The result of this study is clear, the theory and empirics are aligned, agile methods are the right way to go. The respondents consider DevOps as an effective method to reach a higher success rate for IT-projects. The respondents verify the risk categories from the literature study and confirm these risks in their own IT-projects.