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.

This paper explores the ideas of culture and leadership as a unified phenomenon and a means to face challenges caused by implementing new ways of working in knowledge intensive organizations. By creating a supportive culture and trusting in employees, managers can give decisive authority to employees, which will increase motivation, and enable managers to focus on strategy and vision. The research was conducted as a case study at one of the larger Nordic banks. The findings suggest that a cultural perspective on leadership can be used to increase motivation, and help understand the challenges of complex organizations. / Den här uppsatsen utforskar idéer kring kultur och ledarskap som ett gemensamt fenomen och som ett verktyg för att bemöta utmaningar som uppstår då nya sätt att arbeta implementeras i kunskapsintensiva organisationer. Genom att skapa en stödjande kultur och genom att lita på de anställda kan chefer beslutande ansvar till de anställda, vilket kommer öka motivationen bland de anställda samt ge cheferna mer tid till att fokusera på att utveckla strategi och vision. Forskningen utfördes som en case-studie på en av de större nordiska bankerna. Slutsatserna i den här uppsatsen pekar mot att kulturellt ledarskap kan användas som ett verktyg för att öka motivation, och för att förstå och bemöta the utmaningar som uppstår i komplexa organisationer.

Several studies have been conducted regarding the importance of knowledge managementwithin an organization. Furthermore, due to the successful outcome of the implementation ofagile project management approaches within the IT-sector, they have been implemented inother sectors as well. The purpose of this master thesis is to examine how agile projectmanagement influences knowledge sharing within a project team in an engineeringconsultancy firm.The study was conducted through a qualitative approach at a Swedish engineeringconsultancy firm. Data was gathered from observations of project meetings and interviewswith consultants involved in projects that have implemented agile methods. Moreover,interviews were conducted with external experts with expertise in agile project managementin order to obtain additional perspective. Semi-structured interviews were conducted withmodified questions for consultants and agile experts. Thereafter, the empirical findings wereinterpreted by the theoretical concepts in order to sum up the report with conclusions.Firstly, the study confirmed that the implemented agile methods influence explicit knowledgesharing whereas the tacit knowledge sharing is not enabled sufficiently within a project team.Secondly, it could be concluded that the implemented agile methods influence projecttransparency, team-collaboration and communication. This positive influence enablesknowledge sharing within a project team. Lastly, the conducted research concluded that agilemethods influence consultants to share knowledge due to the nature of required inputs inthese methods. Since tacit and explicit knowledge sharing and its documentation is equallyimportant for the success of a project and the consultancy company subsequently, thisresearch has concluded that a hybrid of traditional management approaches and agile methodsis essential to share and document both types of knowledge for alike consultancy firms.Consequently, the research findings resulted in recommendations which aim to improve theprocess of creating and implementing a hybrid of management approaches. / Flera studier har genomförts avseende betydelsen av kunskapshantering inom en organisation.Som en följd av flera framgångsrika resultat av implementerade metoder inom agilaprojektledning inom IT-sektorn har dessa metoder även börjat implementeras i andra sektorerSyftet med detta examensarbete är att undersöka hur agil projektledning påverkarkunskapsdelning i ett projektteam i ett tekniskt konsultföretag.Studien genomfördes med ett kvalitativt tillvägagångssätt vid ett tekniskt konsultföretag iSverige. Data samlades genom observationer av projektmöten och intervjuer med konsultersom deltar i projekt där agila metoder har implementerats. Dessutom genomfördes intervjuermed externa experter med kompetens inom agil projektledning för att få ytterligareperspektiv. Semi-strukturerade intervjuer genomfördes med modifierade frågor för konsulteroch agila experter. Därefter tolkades de empiriska resultaten med de teoretiska koncepten föratt sammanfatta studien med slutsatser.För det första konstaterade studien att de implementerade agila metoderna påverkar denexplicita eller uttalade kunskapen medan den underförstådda eller tysta kunskapsdelningeninte påverkas tillräckligt inom ett projektteam. För det andra kan det konstateras att deimplementerade agila metoderna påverkar ett projekts transparens, samarbetet i ett team ochkommunikation. Detta positiva inflytande möjliggör en kunskapsdelning inom ettprojektteam. Slutligen konstaterade studien att agila metoder påverkar konsulternas vilja attdela med sig av kunskap på grund av metodernas karaktärer vilka fordrar input. Eftersom tystoch explicit kunskapsdelning är lika viktiga för ett projekts framgång har den härundersökningen dragit slutsatsen att en hybrid av traditionell projektledning och agila metoderär avgörande för att upprätthålla båda typerna av kunskapsdelning för konsultföretag avlikadant slag. Forskningsresultaten resulterade följaktligen i rekommendationer som syftar tillatt förbättra processen att skapa och genomföra en hybrid av projektledningsmetoder.

Agila metoder används främst inom IT-sektorn och syftet med dessa metoder är att uppnå en ökad effektivitet och produktivitet. Metoderna främjar ett närmare samarbete mellan projektgrupper och kund. En ökad involvering av kund inom utveckling resulterar i kontinuerlig återkoppling på resultat och projektgrupper kan enklare försäkra sig om projektet håller sig inom ramen för att nå slutmålet med produkten. Metoderna bidrar även till en ökad flexibilitet och hantering av krav och förändringar som tillkommer under projektets gång. Teorin bakom agila metoder är tydlig, dock saknas studier som visar huruvida teorin stämmer överens med agila metoders användning i praktiken. Denna kandidatuppsats ämnar studera skillnaden mellan dessa. Studien baseras på en kvalitativ undersökning och ett omvänt deduktivt angreppssätt. Tre respondenter med olika yrkesroller inom systemutveckling har deltagit i studien för att ge ett bredare perspektiv. Resultatet visar en överenstämmelse mellan teori och praktik. Teorin beskriver utförligt hur en agil metod bör användas, vilka komponenter och roller som bör inkluderas för att nå ett tillfredställande resultat. Praktiken visar att verksamheter komponerar ihop egna metoder mer anpassade efter verksamheten och dess arbetsuppgifter. Verksamheter utgår från synsättet att ingen enskild metod är prefekt. Slutsatsen baserad på resultatet styrker praktiken, verksamheter undviker den begränsningen som medföljer genom att enbart nyttja en metod. Verksamheter som tidigare inte arbetat agilt inleder med att implementera en metod för att erhålla kunskaper kring hur arbetet bör utföras för att nå ett mer agilt tillstånd och vid ett senare skede utveckla dessa metoder för att anpassa dessa efter verksamheten. / Agile methods are most commonly used within system development and allow increased efficiency and productivity. Agile methods promote close collaboration between project groups and customers. Increased involvement of customers in the development process results in continuous feedback on the results, hence, project groups can more easily ensure that project requirements are met. Further, agile methods contribute to increased flexibility and management of requirements and changes that will occur during the project. The theory behind agile methods is clear, however, there are no studies that show whether the theory is consistent with the use of agile methods in practice. This thesis aims to study the difference between theoretical guidelines and the practical use. The study is based on a qualitative and deductive approach. Three respondents with two different professional roles in system development participated in the study to provide a broad perspective. The theory describes in detail how an agile method should be used, what components and roles should be included to yield positive outcome. The practice shows that companies compose their own methods more adapted to the business, based on the view that no single method is perfect. However, companies that have not previously worked agile began to implement a single method for gaining knowledge about how to most efficiently achieve a more agile state and later develop these methods to adapt the to the specific business. These results suggest a consistency between theory and practice. The conclusion based on the results reinforces the practical view, businesses avoid the constraint that comes with using only a single method.

Traditionellt har inköpsprocessen inom offentlig sektor utgått från projektmodellen vattenfall med tydliga faser och milstolpar. För att skapa större flexibilitet och effektivitet har IT-branschen frångått den traditionella projektmodellen och istället övergått till agila arbetsmetoder. En utmaning som uppstått genom detta är att inköpsprocessen inom den offentliga sektorn sällan är anpassad till agila arbetssätt. Den offentliga sektorn är en stor inköpare av IT men en betydande del av de offentliga IT-projekten misslyckas idag i form av överskriden budget. En orsak till detta kan vara att den traditionella inköpsprocessen har svårt att möta de förutsättningar som krävs för ett agilt arbetssätt, då den hindrar effektiviteten och måluppfyllelsen vid inköp av IT.   I denna studie undersöks vilka möjligheter och utmaningar som finns inom en agil inköpsprocess för IT, samt hur en agil inköpsprocess skulle kunna struktureras och tillämpas i syfte att öka effektiviteten, kundnyttan och harmoniseringen mellan inköp av IT och implementeringen.   En kvalitativ studie har genomförts där primärdata insamlats genom intervjuer. Totalt har 23 djupintervjuer genomförts med olika aktörer inom inköpsprocessen såsom beställare, upphandlare och leverantörer. Den största delen av datainsamlingen är genomförd på Luleå kommun men intervjuer har även utförts med externa respondenter med kunskap om agila arbetssätt inom offentlig sektor. Intervjuerna har analyserats genom en tematisk analys, som resulterat i ett flertal identifierande möjligheter och utmaningar för agilt inköp av IT samt ett ramverk för agilt inköp av IT.   Studien visar att det finns både möjligheter och utmaningar inom en agil inköpsprocess för IT. Offentliga organisationer som bland annat genomsyras av de agila grundvärderingarna, med motiverade och förändringsbenägna individer och förtroende för leverantörer har goda möjligheter att arbeta med agilt inköp. Utmaningar finns inom ett ökat behov av struktur, högre grad av effektstyrning, proaktiv uppföljning, en förändrad anbudsutvärdering och en kulturell omställning.   I studien har ett ramverk för agilt inköp av IT inom offentlig sektor framtagits. Ramverket är baserat på den nationella inköpsprocessen och de agila grundvärderingarna. Inom varje fas i inköpsprocessen presenteras aktiviteter som bidrar till att skapa en agil inköpsprocess. Aktiviteterna innefattar bland annat att skapa självorganiserande team, ställa krav på effektmål, skapa en jämn riskfördelning och arbeta med incitament för effektivitet. Studien bidrar med ny kunskap inom hur ett agilt arbetssätt kan anammas inom inköpsprocessen för IT inom offentlig sektor. Genom att använda det agila ramverket kan offentliga organisationer skapa en ökad harmonisering mellan inköpsprocessen och implementeringen av IT, med förhoppningen att det ökar effektiviteten och kundnyttan. / Traditionally, the public procurement process has originated in the waterfall project model, with distinct phases and gates. To gain more flexibility and efficiency, the IT industry have adapted agile project methods instead. A challenge that has arisen due to this change is that the traditional procurement process rarely is adapted to agile project methods. Furthermore, the public sector is a large buyer of IT, but a significant part of all public projects within IT are failing in terms of exceeded budget. One reason for this could be that the traditional procurement process has difficulties in meeting the conditions required for agile methods, since it prevents the efficiency and goal achievement of IT procurement.   In this study, the possibilities and challenges of an agile procurement process for IT was researched. The study also included how the procurement process could be structured and applied, with the aim to increase the efficiency, the customer value and the harmonization between procurement of IT and the implementation.   The research questions were answered by a qualitative study where primary data was collected through interviews. A total of 23 deep interviews were conducted with different participants in a procurement process such as purchasers, suppliers and clients. The largest amount of data was collected at Luleå kommun, but interviews were also conducted with external respondents with knowledge of agile methods in the public sector. The interviews were analyzed through a thematic analysis, which resulted in several opportunities and challenges concerning agile procurement, together with a framework for agile procurement of IT.   The study shows that there are both opportunities and challenges in an agile procurement process of IT. Public organizations that for example is permeated of the agile ground values, with motivated individuals with a likeness of change and trust towards the suppliers, have good opportunities to work with agile procurement. Challenges exists in an increased need of structure, a change in purchasing and contract procedures and the need of education and a culture shift.  In the study, a framework for agile procurement of IT in the public sector has been developed. The framework is based on the national procurement process in Sweden and the agile ground values. In each procurement process phase activities that characterize agile methods are presented. The activities include for example creating self-organizing teams, setting requirements based on impact goals, creating a model for shared risk and work with incentives for efficiency. The study contributes to new knowledge of how agile methods can be incorporated in the public procurement process. By using the agile framework public organization can increase the harmonization between the procurement process and the implementation of IT, with the aim to increase the customer value and efficiency.

La question de la transition numérique est primordiale en conception architecturale. L’objectif de notre recherche est de proposer des pratiques collaboratives afin de faciliter cette transition numérique. Nous nous concentrons sur des pratiques dites « agiles » permettant d’améliorer la communication et la coordination entre architectes, ingénieurs ou encore le maître d’ouvrage. Ces pratiques doivent permettre à ces acteurs d’échanger leurs intentions architecturales et de les évaluer tout en s’assurant que leurs propositions sont satisfaisantes vis-à-vis des besoins du client. Ces pratiques consistent à remplir collaborativement un cahier d’intentions, nécessitant alors confrontations d’opinions, à jouer à un jeu de cartes obligeant tous les concepteurs à prendre la parole, à réaliser des réunions courtes et quotidiennes afin d’expliquer son avancement ou encore à être un coach dont l’objectif est de faciliter la vie de ses collaborateurs. / The question of digital transition is a key issue in architectural design. The objective of our research is to propose collaborative practices to facilitate this digital transition. We focus on so-called "agile" practices to improve communication and coordination between architects, engineers or project owner. These practices must allow these actors to exchange their architectural intentions and evaluate them while ensuring that their proposals are satisfactory concerning the client's needs. These practices consist in collaboratively filling out a book of intentions, requiring confrontations of opinions, playing a card game obliging all designers to speak out, holding short, daily meetings to explain their progress or being a coach, whose objective is to make life easier for their employees.

A crescente demanda por sistemas e a alta velocidade com que seus requisitos evoluem têm evidenciado que desenvolvimento de software exige flexibilidade, pois muitas decisões precisam ser tomadas durante o projeto. Além disso, as dificuldades para a produção de sistemas vão muito além das questões técnicas. Fatores estratégicos, comerciais e humanos são responsáveis por algumas das variáveis que contribuem para tornar o desenvolvimento de sistemas de software uma atividade altamente complexa. Modelos tradicionais de desenvolvimento de software propõem processos prescritivos que não consideram toda essa complexidade. Por outro lado, Métodos Ágeis de desenvolvimento de software sugerem uma abordagem mais humanística com foco na entrega rápida e constante de software com valor de negócios. Porém, para conseguir isto, é preciso escolher um conjunto de práticas de desenvolvimento adequado às características do projeto e da equipe. Desta forma, a natureza única de cada projeto e a necessidade de alta qualidade e produtividade tornam importante a busca por práticas de desenvolvimento. A partir de projetos que conduzimos usando métodos ágeis na academia e na indústria, identificamos e descrevemos 22 práticas para desenvolvimento de software que podem ser adotadas por equipes para aumentar o seu desempenho e/ou a qualidade do software. / The growing demand for systems and the high speed with which their requirements evolve has shown that software development requires flexibility because many decisions need to be taken during the project. Also, the difficulties for the production of software systems go far beyond the technical issues. Strategic, commercial and human factors are responsible for some variables that contribute to make the software development a highly complex activity. Traditional models of software development propose prescritive processes that do not consider all this complexity. On the other hand, Agile Methods of software development suggest an humanistic approach focused on fast and often business valuable software deliveries. But, in order to get it, one needs to choose an appropriated group of development practices accordingly to the project and team features. In this way, the individuality of each project and the need for better quality and productivity motivate the search for software development practices. Based on projects that we conducted by using agile methods in academic and industry environments we identified and described 22 software development practices that can be used by teams to increase their performance and/or the software quality.

Métodos ágeis foram criados para sanar fraquezas reais e perceptíveis dos métodos tradicionais de desenvolvimento de software. Devido à pressão na entrega de produtos de software dentro do prazo, muitas vezes requisitos de segurança são pouco mensurados ou até deixados de lado. Durante o desenvolvimento ágil de software é importante detectar possíveis vulnerabilidades. Esta dissertação descreve um survey aplicado a membros de equipes de desenvolvimento de software que aplicam métodos ágeis. Para tanto, foram identificados por meio da rede de profissionais LinkedIn 110 membros de equipes ágeis que implantaram, estão em processo de implantação ou ainda irão implantar técnicas e ferramentas para detecção de vulnerabilidades. Além disso, foram entrevistados nove gerentes de equipes ágeis. O questionário e o roteiro da entrevista foram baseados em três conhecidos processos de desenvolvimento de software seguro, a saber, Processo de McGraw, OWASP CLASP e as atividades de Howard e Lipner. A coleta de dados se deu por meio de questionários e entrevistas. A análise dos resultados utilizou técnicas de estatística descritiva e análise de conteúdo. Elas indicaram os métodos ágeis mais utilizados, o uso atual das técnicas e ferramentas, as aptidões, os interesses e as necessidades em treinamento em técnicas e ferramenta para detecção de vulnerabilidades. Além disso, os benefícios obtidos com a implantação das técnicas e ferramentas, as motivações, as estratégias, as dificuldades, as limitações e as lições aprendidas foram identificadas. Os resultados indicam que existe motivação para a implantação de segurança, mas ainda não se dá atenção especial à detecção de vulnerabilidades nas equipes ágeis cujos membros participaram do survey / Agile methods were created to address real and perceived weaknesses of traditional software development methods. Due to the pressure to delivery software products on time, security requirements are often poorly addressed or even neglected. During agile software development it is important to detect possible vulnerabilities. This dissertation describes a survey applied to members of software development teams who apply agile methods. Thus, 110 members of agile teams were identified through LinkedIns network of professionals who deployed, are in the process of being deployed or will still implement techniques and tools for vulnerability detection techniques and tools were identified. The questionnaire was based on three known safe software development processes, namely, the McGraw Process, OWASP CLASP, and the activities of Howard and Lipner. Data were collected through questionnaires and interviews. The analysis of the results used techniques of descriptive statistics and content analysis. They indicated the most widely used agile methods, the current use of techniques and tools, the skills, interests and training needs of agile teams in vulnerability detection techniques and tools. In addition, the benefits of implementing the techniques and tools, the motivations, the strategies, the difficulties, the limitations and the lessons learned were identified. The results suggest that special attention is still not given to detection of vulnerabilities in the agile teams whose members participated in the survey

Compared to traditional project management methods, agile methods are new. The use of project work keeps increasing, including the number of projects, with varying characteristics. In a world with a growing speed of change and with growing demands, there’s a need for adjustment, something which agile methods offer. However, agile methods are not suitable for all types of projects. The aim of the study was to broaden the understanding of what motivates implementation and usage of agile methods in projects and operations, challenges and advantages that can emerge through implementation and usage of agile methods, and if expectations of agile methods were confirmed. The study was qualitative and was made through semi-structured interviews, which were recorded and later transcribed. Collected data was analyzed based on thematic qualitative analysis. A total of three analyses were made - one per research question. All together the three analyses resulted in a total of thirteen themes. Motives for working agile varied, whereas primary motives for implementing and working with agile methods were increased efficiency, increased participation, and increased visualization of work. During on-going implementation, knowledge and training was crucial, including management, employees and customers. Agile methods were adjusted to reality and operations. Customers wanted to take part in working with agile methods, while their knowledge was inadequate. Expectations that existed before the implementation were confirmed. Agile methods hold what it promises.

Information Security nowadays is becoming a very popular subject of discussion among both academics and organizations. Proper Data Governance is the first step to an effective Information Security policy. As a consequence, more and more organizations are now switching their approach to data, considering them as assets, in order to get as much value as possible out of it. Living in an IT-driven world makes a lot of researchers to approach Data Governance by borrowing IT Governance frameworks.The aim of this thesis is to contribute to this research by doing an Action Research in a big Financial Institution in the Netherlands that is currently releasing a Data Lake where all the data will be gathered and stored in a secure way. During this research a framework on implementing a proper Data Governance into the Data Lake is introduced.The results were promising and indicate that under specific circumstances, this framework could be very beneficial not only for this specific institution, but for every organisation that would like to avoid confusions and apply Data Governance into their tasks. / <p>Validerat; 20151222 (global_studentproject_submitter)</p>