O alinhamento do portfólio de projetos das empresas às estratégias de negócios das organizações é uma relevante e complexa tarefa. A Governança Corporativa e a Governança de Tecnologia da Informação são apontadas como importantes elementos para atingir esse objetivo. Entretanto, ainda são recentes os estudos sobre os benefícios e a importância da Governança de TI nas empresas e na condução de projetos de TI. Nesta dissertação, é apresentado um estudo sobre a percepção dos consultores e gerentes de projetos quanto à importância da Governança de Tecnologia da Informação na implementação de Sistemas de Informações Gerenciais (SIGs). Adotou-se, como método, a pesquisa exploratória que utilizou como delineamento um estudo de caso, com abordagem qualitativa. Os dados foram obtidos pela aplicação de um questionário e analisados por meio das técnicas estatístico-descritivo. Os resultados obtidos apontam que o uso das melhores práticas de Governança de TI, na percepção dos consultores e gerentes de Projetos de TI, são importantes para o sucesso na implementação de SIG. Com destaque para as questões de planejamento que apresentaram maior relevância em contrapartida as questões de controle consideradas de menor relevância. / The alignment of the project portfolio of the companies to the business strategies of the organizations is an important and complex task. The Corporate Governance and Governance of Information Technology are identified as important elements to achieve this goal. However, recent studies are still about the benefits and importance of IT governance in enterprises and conducting IT projects. This dissertation presents a study on the perceptions of consultants and project managers on the importance of Information Technology Governance implementation of Management Information Systems. It was adopted as a method, exploratory research design that used as a case study, with qualitative approach. Data were collected through questionnaire and the results based on descriptive statistical method. The results indicate that the best practices of IT governance, perceptions of consultants and managers of IT projects are important to the success of Management Information Systems implementation. Highlighting the issues of planning that was more relevant, on the other hand, control issues was considered less relevant.

Diploma thesis proposes the project for voicebot implementation. The thesis explains possible use of this technology in the context of the company and analyzes the current situation. Using project management tools the project is designed which can be used for implementation of this technology.

The rise of Agile project methodologies has increased the success rate of software development projects, but recent studies show that, even though the risk of failing has lessened, only 31% of the completed software development projects are declared as successful while the rest are declared either challenged or failed. A concept called Pair Programming that derives from agile methodologies is widely and basically always used by developers but in present time as we are heading towards a more remote environment and Distributed Pair Programming has become a hot topic. At its core, it is the same as Pair Programming, but the coding session is conducted in a distributed setting, meaning, the two developers are not sitting next to each other. There are little to no studies conducted about DPPs impact on software development projects and if DPP has the potential to mitigate risk factors that may arise while implementing code in an agile software development project.   The purpose of this thesis has been to research and discover what the perceived benefits and drawback of Distributed Pair Programming (DPP) are and which factors that are the most harmful to a software development project and if DPP can facilitate higher success rates. To answer the research questions, a qualitative research method has been used. The empirical data have been gathered by conducting 6 semi structured interviews with developers. Further, a thematic analysis has been carried through with the intent to easily map out the different themes that appears during the interviews.     The findings from the conducted study shows that there are multiple drawbacks and benefits. According to the informants, the benefits outweigh the drawbacks in such a manner that by not conducting DPP, they set themselves up for setbacks. It is very beneficial when onboarding a new team member and when tackling tougher problems. When it comes to implementing DPP in a successful manner there is a need for a digital infrastructure that supports verbal communication, web camera, screensharing and collaboration tools. / Ökningen av agila projektmetoder har ökat framgångsfrekvensen för programvaruutvecklingsprojekt, men nyare studier visar att även om risken för att misslyckas har minskat, förklaras endast 31 % av de avslutade programvaruutvecklingsprojekten som framgångsrika medan resten förklaras antingen utmanade eller misslyckades. Ett koncept som kallas för parprogrammering som härrör från gila metoder används i stor utsträckning och i princip alltid av utvecklare, men för närvarande är vi på väg mot en mer digital miljö och distribuerad parprogrammering(DPP) har blivit ett hett ämne. I grunden är det samma sak som parprogrammering men kodningssessionen genomförs i en distribuerad miljö, vilket innebär att de två utvecklarna inte sitter bredvid varandra. Det finns väldigt få studier utförda om DPPs inverkan på programvaruutvecklingsprojekt och om DPP har potential att mildra riskfaktorer som kan uppstå när kod implementeras i ett agilt programvaruutvecklingsprojekt. Syftet med detta examensarbete har varit att undersöka och upptäcka vad de upplevda fördelarna och nackdelarna med DPP är och vilka faktorer som är mest skadliga för ett programvaruutvecklingsprojekt och om DPP kan främja högre framgångsfrekvens. För att besvara forskningsfrågorna har en kvalitativ forskningsmetod använts. Empirin har samlats in genom att genomföra 6 semistrukturerade intervjuer med utvecklare. Vidare har en tematisk analys genomförts i syfte att enkelt kartlägga de olika teman som framställts under intervjuerna. Resultaten från den genomförda studien visar att det finns flera nackdelar och fördelar. Enligt informanterna uppväger fördelarna nackdelarna på ett sådant sätt att man genom att inte bedriva DPP dukar upp för problem. Det är mycket fördelaktigt när en ny teammedlem ska introduceras och när du tar itu med ett tufft problem. När det gäller att implementera DPP på ett framgångsrikt sätt finns ett behov av bra digital infrastruktur som stödjer verbal kommunikation, webbkamera, skärmdelning och samarbetsverktyg.

<p>  </p> <p>This research aimed to explore whether the PMBOK risk management process needs to change to facilitate successful project execution in the future, due to the impacts of the recent covid 19 crises. </p> <p>The researcher conducted the SLR and found no specific result addressing the need to change the PMBOK risk management process. Nevertheless, this research showed that the project manager would need to be more flexible during the planning stage of the risk management process and expand the risk identification process to plan for significant disruptive risks like the covid 19. </p> <p>The findings also suggest that project managers need to adapt to challenging situations in such a crisis. One vital theme was the need to provide psychological safety for employees. During disruptions, project managers would need to pay close attention to the effects of the crisis on individuals' psychology to ensure they work effectively </p>

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.

The implementation of an Identity and Access Management (IAM) solution is a complex process to manage, consuming multiple years and involves organizational changes. In its nature, several challenges tend to appear to different stakeholders involved in the process. However, prior research has mainly addressed the technical components of an IAM-solution, hence the technical challenges that emerge during development and implementation. Therefore, the non-technical challenges of the IAM-project work and the challenges that constitute the client implementation are understudied. The purpose of this thesis is to visualize the challenges that emerge when an IAM-solution is implemented. In addition, the challenges when organizational changes occur. The empirical data is conducted through a series of semi-structured interviews with individuals in the IAM line of business. In addition, secondary data is gathered through the review of papers and reports in Information Systems (IS) and Information Technology (IT) projects and outsourcing projects, as well from a non-academical organization with in-depth knowledge of IAM implementations. A qualitative case study of IAM implementations was conducted to investigate the studied complex phenomenon. The findings display the challenges of Insight, Communication, and Endurance (ICE), which tend to be obstacles for all stakeholders involved. Additionally, the organizational changes describe three further challenges of Anchoring, Communication, and Vision (ACV). These challenges mainly appear in client changes, which IAM implementations initiate. The thesis display connections and incoherent with prior research on IS/IT-projects and IAM-projects. In addition, newly uncovered aspects that contribute to research areas are highlighted. The thesis is summarized with some implications and possibilities for future research. / En IAM implementeringen är en komplex och utdragen process som kan ta flera år samt skapar en förändringsresa hos kund. I sin natur skapas flera utmaningar till olika involverade aktörer. Tidigare forskning har främst fokuserat på de tekniska komponenterna som en IAM lösning baseras på, därav de tekniska utmaningarna som tillkommer. Till följd har de icke-tekniska utmaningarna inom IAM projekt och utmaningarna med en implementation hos kund fått bristande uppmärksamhet där få studier har genomförts. Syftet med detta examensarbete är att visualisera de utmaningar som uppstår vid en IAM implementering. Arbetet fokuserar även på utmaningarna med organisatorisk förändring, vilket genomförandet av en IAM lösning skapar. Den primära datainsamlingen genomförs av halvstrukturerade intervjuer med personer inom IAM-branschen. Dessutom samlas sekundär data in från informationssystem (IS) och informationsteknik (IT) projekt samt outsourcingprojekt. Därtill några icke akademiska rapporter med fördjupande information om IAM implementeringar. Examensarbetet är gjort som en kvalitativ fallstudie av IAM implementeringar, detta för att förstå komplexiteten av ämnet. Resultatet visar utmaningar som Insikt, Kommunikation och Uthållighet, vilket tenderar att vara hinder för alla involverade aktörer. Dessutom beskriver de organisatoriska förändringarna tre ytterligare utmaningar för Förankring, Kommunikation och Vision. Dessa utmaningar förekommer hos kund som implementerar en IAM lösning. Uppsatsen visar sammanhängande och osammanhängande aspekter med forskningen inom IS/IT projekt och IAM projekt. Dessutom framhävs nya upptäckta insikter som bidrar till forskningsområdena. Slutligen sammanfattas arbetet med några implikationer samt förslag på vidare forskning.

Bakgrund:  Digitaliseringens framfart påverkar i princip allting i dagens samhälle. Detta har lett till att företagens IT-landskap blir alltmer komplexa. För att hantera detta introduceras många olika IT-projekt inom organisationer. Dessa IT-projekt har dock en historia av att misslyckas och det finns därför mängder av rekommenderade implementationsprocesser samt litteratur som beskriver hur man bör hantera projektkomplexitet. Däremot saknas forskning som utreder om verksamhetsarkitektur bidrar till projektkomplexiteten samt empiriska undersökningar angående hur detta hanteras.  Syfte: Syftet med studien är att undersöka hur verksamhetsarkitektur kan påverka projektkomplexitet och i sin tur implementation av nya affärssystem. Vidare ämnar studien skapa förståelse för hur projektkomplexitet hanteras i implementeringsprocesser.   Metod: Denna studie är en kvalitativ fallstudie, där vi undersökt ett företag inom miljö- och återvinningsbranschen. Empirin har samlats in genom fem semistrukturerade intervjuer där urvalet varit målstyrt. Slutsats: Denna studie visar att verksamhetsarkitekturen påverkar de faktorer som ingår i projektkomplexitet. I detta fall har det även påverkat implementeringen av nya affärssystem negativt. Vidare visar studien en bristfällig hantering av projektkomplexitet då fallföretaget inte haft något tillvägagångssätt för att vare sig förebygga komplexitet eller hantera det utmaningar som uppstått. / Background: The advance of digitalisation affects almost everything in today's society. This has led to an increasingly complex IT landscape for businesses. To cope with this, many different IT projects are being introduced within organisations. However, these IT projects have a history of failing and there is therefore a wealth of recommended implementation processes and literature describing how to deal with project complexity. However, there is a lack of research investigating whether enterprise architecture contributes to project complexity and empirical studies on how this is managed. Purpose: The purpose of this study is to investigate how architecture has affected project complexity and in turn the implementation of new business systems. Furthermore, the study intends to provide an understanding of how project complexity is handled within implementation processes.   Completion: This study is a qualitative case study, in which we investigated a company in the environmental and recycling industry. The empirical data have been collected through five semi-structured interviews where the sample was purposive.  Conclusion: This study shows that the enterprise architecture influences the factors of project complexity. In this case, it has also negatively affected the implementation of new enterprise systems. Furthermore, the study shows a poor management of project complexity as the case company had no approach to either prevent complexity or manage the challenges that arose.

This research focuses on the role that polychronic Communication (PC) plays in the productivity and project success of Information Technology (IT) Project Managers (PMs). PC refers to a communication style where the communicator switches rapidly between several conversations, irrespective of topic similarity, instead of completing one conversation before starting another. An online questionnaire collected data from Information Technology workers in multiple industries across the globe. The data consisted out of two distinct groups: IT PMs (n = 202) and IT project team members (n = 122). Statistical analysis on the dataset considered the perspectives of both participant groups, first separately and then combined. The results showed relationships between: 1. IT PMs’ individual polychronicity and their PC. 2. IT PMs’ PC and their opinion of the influence of PC on the success of the projects that they are managing. 3. IT PMs’ PC and their opinion of the influence of PC on their productivity. 4. IT PMs’ PC and the corporate polychronicity of their employers. In addition, when IT PMs rate their PC, the rating is lower than when other IT project team members rate the IT PMs’ PC. By contrast, there was no difference between IT PMs rating the influence of their PC on their project success and productivity versus IT project teams rating the influence of the IT PMs’ PC on their project success and productivity. These findings contribute to the factors that a corporation has to consider in hiring new IT PMs or training their current IT PMs. / Information Science / M. Sc. (Information Systems)

Uppsatsen presenterar vilka faktorer som bidrar till effektivitet inom distribuerade team som arbetar med mjukvaruutveckling och hur dessa faktorer påverkar effektiviteten i arbetsprocessen. Det utgör en utmaning att arbeta effektivt inom mjukvaruutvecklingsprojekt och den distribuerade faktorn, att projektmedlemmarna är utspridda över mer än ett kontor, bidrar med ytterligare komplexitet. Genom studien vill vi bidra till att göra denna komplexitet mer hanterlig. Vi har genomfört en kvalitativ fallstudie där vi har studerat ett utvalt distribuerat projekt vid ett mjukvaruutvecklingsföretag. Det empiriska underlaget har samlats in genom semistrukturerade intervjuer och analyserats utifrån identifierade teman. Vi har huvudsakligen identifierat sociala faktorer, men även några tekniska faktorer, som bidrar till en effektiv arbetsprocess. Faktorerna innefattar kommunikation, gruppidentitet, stämning, kultur och normer samt ledarskap. De innefattar bland annat att genomföra väl anpassad kommunikation och dokumentation, hålla frekventa möten, ha få grupperingar, gemensamma IT-verktyg, att främja social kommunikation, ha transparent ledarskap och att teammedlemmarna är ansvarstagande. Utöver att lista faktorerna beskriver vi i slutsatsen även hur de bidrar till att effektiva arbetsprocesser uppnås. / This thesis presents which factors contribute to efficiency in distributed teams working with software development, and how these factors affect the efficiency of the work process. Working effectively in software development projects is a challenge and the distributed factor, that project members are distributed across more than one office, brings additional complexity. Through the study, we want to help make this complexity more manageable. We have carried out a qualitative case study where we have studied a selected distributed project at a software development company. The empirical data has been collected through semi-structured interviews and analyzed based on identified themes. We have mainly identified social factors, but also some technical factors that contribute to an efficient work process. The factors comprise communication, group identity, mood, culture and norms as well as leadership. They include, among other things, implementing well-adapted communication and documentation, holding frequent meetings, few groupings, common IT tools, promoting social communication, having transparent leadership and the team members having a high level of responsibility. In the conclusion we also describe how the listed factors help to achieve an efficient work processes.

This research focuses on the role that polychronic Communication (PC) plays in the productivity and project success of Information Technology (IT) Project Managers (PMs). PC refers to a communication style where the communicator switches rapidly between several conversations, irrespective of topic similarity, instead of completing one conversation before starting another. An online questionnaire collected data from Information Technology workers in multiple industries across the globe. The data consisted out of two distinct groups: IT PMs (n = 202) and IT project team members (n = 122). Statistical analysis on the dataset considered the perspectives of both participant groups, first separately and then combined. The results showed relationships between: 1. IT PMs’ individual polychronicity and their PC. 2. IT PMs’ PC and their opinion of the influence of PC on the success of the projects that they are managing. 3. IT PMs’ PC and their opinion of the influence of PC on their productivity. 4. IT PMs’ PC and the corporate polychronicity of their employers. In addition, when IT PMs rate their PC, the rating is lower than when other IT project team members rate the IT PMs’ PC. By contrast, there was no difference between IT PMs rating the influence of their PC on their project success and productivity versus IT project teams rating the influence of the IT PMs’ PC on their project success and productivity. These findings contribute to the factors that a corporation has to consider in hiring new IT PMs or training their current IT PMs. / Information Science / M. Sc. (Information Systems)