The thesis topic is linking of knowledge from psychology and psychodiagnosis within project management. The thesis has several aims, which are all introduced in the first chapter. One of those aims is the introduction of contemporary ways, methods and standards used in project management. Another aim is equipping a project manager with knowledge from psychology and psychodiagnosis, which still constitute a comparatively neglected area of project management. What their utilization can actually do is to increase the efficiency and performance of project teams. The final aim is to come up with a solution to identified problems based on the conducted research. The second chapter of the thesis explains basic terms of project management, its standards and methodology, and duties of a project manager. The part devoted to psychology deals with personality, psychodiagnostic methods, team and motivation. The fourth chapter pursues the conduct and evaluation of research of contemporary project management. Finally, problems identified based on the findings from questionnaire survey are dealt with within the fifth chapter. It contains instructions for choice of appropriate way of project management, draft of the process of building a project team and a concept to achieve greater work satisfaction of team members.

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.

Productivity improvement in the software industry is one of the major challenges facing many software development companies in this century. Most companies have adopted agile methodologies in order to profit from the benefits claimed for them. Agile methodologies are characterised by frequent software delivery, short feedback loops, quicker response to change, and problem identification earlier in the development process. The agile approach has been recognised as paving a way for companies to acquire higher software productivity, delivering good-quality and cost-effective software, enabling software development companies to respond to business challenges with their demands for high quality, high performance and high development speed in delivering the final product. For companies that adopt agile methodologies, understanding the factors that influence their teams’ software development productivity is a challenging task for management and practitioners today. In this research, an analysis is presented that identifies productivity factors that affect agile teams. It is a study of agile methods to identify common agile practices and/or values that have impact on productivity, and describes suitable metrics that could be used to measure agile team productivity. A qualitative research approach was used, and the case study was chosen as the research strategy. Two South African companies that are located in two different provinces and that adopted agile methodologies in their software development, were selected for the case studies. Qualitative content analysis was used in the research to permit subjective interpretation of factors that influence agile team productivity, and to analyse to what extent these factors affected productivity. This research has shown that an understanding of the factors that influence an agile team’s productivity gives significant insight into the way agile teams work, motivates team members to work together, and leads to uniform metrics in tracking each team’s progress. The study indicates that tracking an agile team’s work and providing adequate tools needed to execute their tasks results in improving agile team productivity. It should be recognised that using metrics to measure performance in agile teams is helpful in creating a team’s culture and trust. In this study, it was found that the factors identified in both literature and case studies affected productivity in the two companies under study, both positively and negatively. The study also found that applying the correct metrics in assessing, analysing and reviewing an agile team’s performance is important when monitoring productivity. Successful software delivery is only possible if individuals are committed to their work, are provided with the necessary tools and have access to a stable working environment. In addition, individual factors such as knowledge, skills, abilities, personalities and experience should be considered when forming agile teams. Consideration of these factors will result in grouping people that are able to work together and achieve a common goal, which is important in improving productivity. A conceptual framework for agile team productivity was proposed. The discussion of the findings is presented in more detail in this research. / School of Computing / M.Sc. (Computing)

The software is a key differentiator and driver of innovation in the automotive industry. The major challenges for software development are increasing in complexity, shorter time-to-market, increase in development cost and demand of quality assurance. The complexity is increasing due to emission legislations, variants of product and new communication technologies being interfaced with the vehicle. The shorter development time is due to competition in the market, which requires faster feedback loops of verification and validation of developed functionalities. The increase in development cost is contributed by two factors; the first is pre-launch cost, this involves the cost of error correction in development stages. Another is post-launch cost; this involves warranty and guarantees cost. As the development time passes the cost of error correction also increases. Hence it is important to detect the error as early as possible. All these factors affect the software quality; there are several cases where Original Equipment Manufacturer (OEM) have callbacks their product because of the quality defect. Hence, there is increased in the requirement of software quality assurance. The solution for these software challenges can be the early quality evaluation in continuous integration framework environment. The most prominent in today\'s automotive industry AUTomotive Open System ARchitecture (AUTOSAR) reference architecture is used to describe software component and interfaces. AUTOSAR provides the standardised software component architecture elements. It was created to address the issues of growing complexity; the existing AUTOSAR environment does have software quality measures, such as schema validations and protocols for acceptance tests. However, it lacks the quality specification for non-functional qualities such as maintainability, modularity, etc. The tool is required which will evaluate the AUTOSAR based software architecture and give the objective feedback regarding quality. This thesis aims to provide the quality measurement tool, which will be used for evaluation of AUTOSAR based software architecture. The tool reads the AUTOSAR architecture information from AUTOSAR Extensible Markup Language (ARXML) file. The tool provides configuration ability, continuous evaluation and objective feedback regarding software quality characteristics. The tool was utilised on transmission control project, and results are validated by industry experts.

Den snabba teknikutvecklingen i samhället beskrivs ofta som den största förklaringen till agila principers snabba framväxt bland IT-organisationer under de senare åren. Agila arbetsmetoder går ofta ut på att arbetet planeras i kortare iterationer där leverantören kontinuerligt stämmer av kundkraven mellan sprintarna. Ramverket ITIL är även det ett vanligt hjälpmedel IT- organisationer använder sig av för att organisera sitt arbete. Den mest använda ITIL praktiken är change management som beskriver hur verksamheter kan organisera hanteringen av ändringarna som de driftsätter. Change management processen är, tillskilland från agila arbetssätt, av sekventiellnatur. Vanliga fördomar om ITIL och change managementprocessen är att det ofta uppfattas som byråkratiskt, icke flexibelt och som agila principers raka motsats. Dock har det visat sig i denna studie att ITIL och agila arbetssätt faktiskt kan komplettera varandra mycket bra om de implementeras på rätt sätt.  Polisens IT-avdelning står inför utmaningen att få processen ur kundens perspektiv att vara effektiv och enkel att ta sig igenom trots att processen innefattar både agila team och en grupp som arbetar enligt ITILs change management, vilket ses som ett problem av fallorganisationen. Syftet med denna kvalitativa fallstudie var därmed att identifiera sätt som dessa två olika grupper kan samverka för att processen ska bli mindre komplex för kund. För att uppnå fallstudiens syfte utfördes en litteraturstudie för att undersöka vad interna kunder värderar, hur en change managementprocess med höga säkerhetskrav kan fungera i en agil verksamhet samt olika processförbättringsverktyg. Vidare utfördes intervjuer och observationer för att samla in de interna kundernas uppfattning av nulägesprocessen samt visualisera processen i en nulägeskarläggning. Dessa analyserades sedan med hjälp av teorin från litteraturstudien.  Studien resulterade dels i 24 identifierade problemområden med tillhörande förbättringsförslag. Sedan presenterades ett specifikt förbättringsförslag för hur change managementgruppen och ett agilt team kan agera mer som en enhet ur kundens perspektiv. Detta förslag skulle kunna vara ett lämpligt första steg för hur fallorganisationen kan effektivare kombinera sitt agila arbete i värdeflödet med change managementgruppen som arbetar efter en ITIL-process. Förslaget skulle bland annat kunna medföra minskat antal kontaktytor för kund, eliminerat dubbelarbete samt minskad ledtid. Andra förbättringsförslag som tagits fram är främst kopplat till förenkling av kommunikation, samverkan av likande aktiviteter, skapa förutsättningar för gemensamt ansvar och prioriteringar. Slutligen presenteras även vikten av att kontinuerligt identifiera de interna kunders behov. Detta eftersom det är en förutsättning för att fallorganisationen ska kunna arbeta med ständiga förbättringar av processen och för att säkerställa att processerna ständigt möter kundernas eventuellt förändrande behov. / The accelerated technological development in society is often described as the biggest explanation for the fast growth of agile principles among IT organizations in recent years. Agile methods often involve the work being planned in shorter iterations where the supplier continuously matches the customer requirements between the sprints. The ITIL framework is also a common tool that IT organizations use to organize their work. The most used ITIL practice is change management, which describes how companies can organize the reviewing of the changes they plan on putting into their production environment. The change management process is, unlike agile methods, of a sequential nature. Common prejudices about ITIL and the change management process are that it is often perceived as bureaucratic, inflexible and as the exact opposite of agile principles. However, it has been found in this study that ITIL and agile actually can complement each other very well if implemented correctly.  The Swedish police's IT department now faces the challenge of making their process easier and more efficient to get through, from the perspective of their internal customers, even though the process includes both agile teams and a group that works according to ITIL's change management. This is perceived as a big problem by the case organization. The purpose of this qualitative case study was thus to identify ways in which these two different groups can work together to make the process less complex for the customer. To achieve the purpose of the case study, a literature study was conducted to examine what internal customers value, how a change management process with high security requirements can work in an agile organization and various process improvement tools. Furthermore, interviews and observations were performed to collect the internal customers' perception of the current process and to visualize the current process in a process map. These were then analyzed by using the theory from the literature study.  The study resulted in 24 identified problem areas with associated improvement proposals. Then a specific improvement suggestion was presented for how change management and an agile team can act more as one unit from the customers’ perspective. This proposal could be an appropriate first step for the case organization to combine its agile work in the value stream with the change management group working after an ITIL process. The proposal could, among other things, lead to a reduced number of contact areas for customers, eliminate duplication of work and reduce the lead time. Other improvement proposals that have been developed are mainly linked to simplifications of communication, collaboration of similar activities, creating conditions for joint responsibility and priorities. Finally, the importance of continuously identifying the internal customers' needs is stated since it is a condition for the case organization to be able to work with continuous improvements of the process. Being able to change the process is necessary to be able to meet the customers’ potentially changed future needs.

Att behöva ställa om sitt arbetssätt från att arbeta fysiskt på plats till att arbeta hemifrån på distans är något som har påverkat de flesta organisationer och individer till viss utsträckning på grund av Covid-19 pandemin. Inom informatiksektorn används agila arbetssätt för att agera som en buffert för att snabbt kunna anpassa sig till nya krav eller arbetsförhållanden. Denna studie tar ett intresse i att undersöka den agila rollen Scrum master utefter ramverket Scrum. Samt studera ifall rollen har behövt göra förändringar i sina arbetsuppgifter och inom Scrum ceremonier, med anledning av övergången till ett distansbaserat arbetssätt. Genom en kvalitativ undersökning där sju certifierade Scrum masters intervjuats har personliga erfarenheter samlats in för att undersöka samband med förändringar som krävts vid omställningen av ens arbete. Där de intervjuade besvarat att deras arbete går att utföra väl även när distansarbete krävs eller blir infört i ens vardag. Utifrån resultatet bygger studien vidare på forskning kring att arbeta som Scrum master och enligt Scrums riktlinjer är en välfungerande metodik även ifall ens arbete behöver genomföras på distans. Trots detta finner studien ett skifte i Scrum masterns prioriteringar vid distansarbete där ett större fokus behövs för att bibehålla kommunikation, välmående och effektiviteten inom Scrum-team. Framför allt när ett Scrum-team blir internt distansbaserat. Detta leder även till rekommendationer som bör beaktas av organisationer eller Scrum masters som utför sitt arbete på distans. / Having to change one's way of working, from working physically on site to remote work is something that has affected most organizations and individuals to some extent due to the Covid-19 pandemic. In the informatic sector, agile working methods are used to act as a buffer to be able to quickly adapt to new requirements or working conditions. This study takes an interest in investigating the agile role of the Scrum master along the Scrum framework, as well as studying whether the role has needed to make changes in performed tasks and within Scrum ceremonies due to the transition to work remotely. Through a qualitative survey where seven certified Scrum masters were interviewed, personal experience from the interviewees has been gathered to investigate the connection with changes required in the adjustment of one's work. Where the interviewees answered that their work can be performed well even when remote based work is required or is introduced into the everyday life. Based on the results, the study extends on research regarding working as a Scrum master and according to Scrum's guidelines, is a well-functioning methodology even if one's work needs to be carried out remotely. Despite this, the study finds a shift in the Scrum master's priorities when working remotely. The study found that a greater focus is needed to maintain communication, well-being, and efficiency within the Scrum-team. Especially when a Scrum-team internally becomes remote based. Which leads to recommendations that should be considered by organizations or Scrum masters who perform their work remotely. Lastly, the following thesis is written in Swedish.

In rapidly changing environments organization and management theories have to consider more flexible approaches to match the demands (1) (2). Agile methods attempt to enable flexible efficient ways of working in team structures (1). In this thesis we empirically study a model from a constructivist approach in an attempt to contribute to knowledge on the eternal problem of people working efficiently in the structure of teams. Social processes are argued to have a major impact on the general application of agile methods (3). However, the practitioners of agile methods tend to focus more on the physical and technical infrastructure as enablers of successful teamwork rather than the social processes of team development (4). Hence, without knowing how the social processes of a team affects the usage of agile methods for team development, an organization is at risk of becoming less efficient over time without realizing why (5) (6).Therefore it is essential to study how an agile method for team development affects and influences the social processes within a team in order to understand how it can be used for efficient teamwork. The purpose of this thesis was to study how an agile method for team development can aid a software development team to improve their way of working. We empirically tested a team-level workshop-based agile method for team development, SHC, in a case study at the Swedish Police Authority IT Department. This included 14 focus group sessions with seven development teams. We posed the following main research question to fulfill the purpose of the study: how can the use of an agile method for team development help software development teams improve theirway of working? We conclude that there are several ways in which an agile method for team development can help teams improve their way of working, and that these depend on the unique social processes within each team. The purpose of the study was fulfilled by the findings of how an agile method can serve teams in different stages of team development by fulfilling different purposes, how it can assist a team in taking action, as well as the potential it has to enable Shared Leadership. / I snabbt föränderliga miljöer måste organisations-och management-teorier ta hänsyn till mer flexibla angreppssätt för att möta kraven (1) (2). Agila metoder har som mål att möjliggöra flexibla och effektiva arbetssätt i teamstrukturer (1). I denna uppsats studerar vi empiriskt en modell ur ett konstruktivistiskt perspektiv i ett försök att bidra till kunskapen om det eviga problemet i att arbeta effektivt i teamstrukturer. Sociala processer anses ha en stor påverkan på den generella appliceringen av agila metoder (3). Utövare av agila metoder tenderar dock att fokusera mer på den fysiska och tekniska infrastrukturen som mögliggörare för effektivt teamwork snarare än de sociala processerna kring teamutveckling (4). Om en organisation alltså inte vet hur de sociala processerna hos ett team påverkar användandet av en agil metod så riskerar organisationen att bli mindre effektiv över tid utan att inse varför (5) (6). Därför är det essentiellt att studera hur en agil metod för teamutveckling påverkar och influerar de sociala processerna inom ett team, för att förstå hur metoden kan användas  för effektivt teamarbete. Syftet med denna uppsats var att studera hur en agil metod för teamutveckling kan hjälpa ett mjukvaruutvecklingsteam att förbättra sitt arbetssätt. Empiriskt testade vi en workshop-baserad agil metod på team-nivå, SHC, i en fallstudie på Polismyndighetens IT-avdelning. Denna inkluderade 14 fokusgruppsessioner med 7 olika utvecklingsteam. Vi ställde följande huvudsakliga forskningsfråga: hur kan användandet av en agil metod för teamutveckling hjälpa mjukvaruutvecklingsteam att förbättra sitt arbetssätt? Vi nådde slutsatsen att det finns flera sätt som en agil metod för teamutveckling kan hjälpa team att förbättra sitt arbetssätt, och att dessa sätt beror på de unika sociala processerna inom teamet. Syftet med studien uppfylldes av slutsatserna kring hur en agil metod kan stödja team i olika stadier av teamutveckling genom att fylla olika syften, hur en agil metod kan stödja ett team i att agera, samt potentialen metoden har i att möjliggöra delat ledarskap.

Requirements engineering remains an important discipline to reduce costs, development times and improve quality in software engineering projects. With Agile methods gaining prominence in a rapidly globalized world, many requirements engineering efforts are today made in distributed contexts, with both teams and stakeholders being separated by physical and organisational distances. At the same time, it is not well understood how agile methods for requirements engineering apply to distributed contexts. This thesis investigates the implementation and use of agile methods for requirements engineering in distributed software engineering contexts. Observations made over a three-month study of the CHAMP project, a joint IT and process development effort between major European truck manufacturers Scania and MAN, are used to assess how commonly practices agile methods perform when implemented over distances. The case study of the CHAMP study suggests that the implementation of agile methods is highly context-sensitive, with limited current opportunities to formulate general heuristics for successful applications. The results of the CHAMP study indicate that distributed contexts hamper team communications when compared to co-located efforts, making it more difficult to implement an overall agile project model. However, individual methods, particularly the use of work backlogs, are found to offer increased structural flexibility beneficial to distributed workflows. Additionally, the CHAMP observations suggest implementing agile methods in new contexts requires an organisational mandate, as agile workflows are less predictable than linear models and can expose the surrounding organisation to higher uncertainty. / Kravhantering är fortsatt ett viktigt verktyg för att reducera kostnader, utvecklingstider och öka leveranskvalitet i mjukvaruutveklingsprojekt. Då agila metoder har blivit allt vanligare i en snabbt globaliserad värld, genomförs idag många kravhanteringsprocesser i utspridda sammanhang, där både projektets personal och intressenter är separerade av fysiska och organisatoriska avstånd. Samtidigt är det inte väl förstått hur agila metoder för kravhantering applicerar i utspridda sammanhang. Detta examensarbete undersöker hur agila metoder han implementeras och användas för kravhanteringsprocesser i utspridda mjukvaruutvecklingsprocesser. Observationer insamlade under en tremånadersstudie av CHAMP-projektet, ett gemensamt IT- och affärsutvecklingsprojekt mellan de stora europeiska lastbilstillverkarna Scania och MAN, används för att bedöma hur vanligt förekommande agila metoder fungerar när de tillämpas i agila sammanhang. Fallstudien av CHAMP-projektet indikerar att den specifika kontexten kan kraftigt påverka implementationen ag agila metoder, vilket för närvarande begränsar möjligheten att formulera generella tumregler för hur de framgångsrikt kan lanseras. CHAMP-studiens resultat påvisar att utspridda projekt har svårare att kommunicera jämför med samlokaliserade grupper, vilket gör det svårare att implementera sammanhållet agila projektmodeller. Samtidigt kan enskilda agila metoder, särskilt användningen av backlogs, hjälpa till att öka flexibiliteten i projekt, vilket är värdefullt i utspridda arbetsprocesser. Slutligen påvisar observationerna från CHAMP-projektet att det är viktigt med ett organisatoriskt mandat vid implementationen av agila metoder, då de är mindre förutsägbara än linjära processer och kan utsätta omkringliggande organisationer för högre osäkerhet.

Esta dissertação de mestrado fez parte do projeto Qualipso (Quality Platform for Open Source Software) que teve como principal objetivo melhorar a confiabilidade de sistemas de software livre. Nesse contexto, o enfoque desta pesquisa é um dos atributos de qualidade de software: usabilidade. As práticas de usabilidade no desenvolvimento de software livre, são aplicadas na maioria das vezes, em projetos patrocinados por grandes empresas ou que possuam especialistas em usabilidade como membros da equipe. Mas, em projetos menores da comunidade, compostos geralmente por desenvolvedores, raramente ela é considerada. Porém, a usabilidade é um atributo fundamental para a qualidade durante o uso de um sistema. Com base em valores compartilhados entre as comunidades de métodos ágeis e de software livre, esta dissertação propõe a adaptação de práticas de usabilidade no contexto de métodos ágeis para o contexto de comunidades de software livre. Por meio de pesquisa bibliográfica, levantamos as principais práticas de usabilidade tanto no âmbito de métodos ágeis, quanto no âmbito de software livre, e as classificamos de acordo com as fases do Design Centrado em Usuário, descrevendo cada uma com o formato nome-contexto-problema-solução-exemplos. As práticas foram exploradas em projetos de software livre, o que possibilitou maior entendimento de problemas enfrentados em contextos reais. Essa experiência resultou na proposta de adaptação de práticas de usabilidade ágil no contexto de comunidades de software livre. Dessa forma, descrevemos a realização de uma pesquisa-ação no projeto Arquigrafia-Brasil, um estudo de caso no projeto Mezuro e a aplicação de práticas de usabilidade em quatro projetos do Centro de Competência em Software Livre do IME-USP. / This Masters thesis was part of the Qualipso project (Quality Platform for Open Source Software) whose main objective was to improve the reliability of free and open source software systems. Within such context, the focus of this research is one of the attributes of software quality: usability. The usability practices in free and open source software development are applied most often in projects sponsored by large companies or employing usability experts as team members. But on smaller projects in the community, generally composed by developers, it is rarely considered. However, usability is an essential attribute to the quality in use of a system. Based on values shared between the communities of agile methods and free and open source software, this thesis proposes the adaptation of usability practices in the context of agile methods to the context of free and open source software communities. Through the study of the literature in the field, we gathered the main usability practices both within agile methods, as in free and open source software, and we classified according to User-Centered Design phases, describing each one with the format name-context-problem-solution-examples. The practices were explored in free and open source software projects, which enabled greater understanding of problems faced in real contexts. This experience resulted in the adaptation proposal of agile usability practices into the context of free and open source software communities. We describe the implementation of an action research in the Arquigrafia-Brazil project, a case study in the Mezuro project and the application of usability practices in four projects of the IME-USP FLOSS Competence Center.

Denna uppsats studerar förutsättningarna för att implementera mjukvaruutvecklings - metoden Continuous Delivery (CDE). Problemställningen som lade grunden för studien, var att det inte finns någon enhetlig standard för CDE. Studien ämnade att undersöka om detta innebar att metoden har varierande innebörd inom olika företag och om de således, i viss mån tillämpar skilda tillvägagångssätt med metoden. Ytterligare en aspekt var att se vilka utmaningar företagen upplevde vid övergången till CDE. Att undersöka om det var främst organisatoriska eller utvecklingsrelaterade problem som upplevts. Samt hur de hanterade kommunikation och tillit till medarbetarna och arbetet inom verksamheten under förändringen. För att belysa problemen, beskrevs teori med fokus på organisatoriska och tekniska utmaningar med Continuous - metoderna: Continuous Integration (CI), Continuous Delivery (CDE) och Continuous Deployment (CD). Teorikapitlet samt tidigare studier inkluderade även forskning om kringliggande koncept som DevOps och LEAN. Metoder, vilka kan underlätta implementationen av CDE. Datainsamlingen genomfördes med öppna individuella intervjuer med representanter från sex stycken företag, där de delade med sig av deras erfarenheter av och syn på CDE. Studien visar att anledningen till att företag väljer att arbeta med CDE, är att de vill gå från utvecklingsmetoder, vilka kräver många beslut inför varje förändring, till ett mer flexibelt arbetssätt där de funnit fördelar som: bättre kvalitet på det som levereras, snabbare leverans av affärsvärde till kunder samt kortare feedback - loopar. Företag som gör en övergång till CDE väljer dessutom ofta att inte automatisera hela vägen ut till produktion, enligt CD, då de ser utmaningar med att säkra kvalitén. Studien har identifierat ett antal faktorer som viktiga för en framgångsrik implementering av CDE, samt faktorer som kan resultera i en svår övergång. / This thesis studies the conditions needed for implementing the software development method Continuous Delivery (CDE). The problem identified for the study, is that there is no standardized approach for CDE as of today. The intentions of the study were to determine whether this means that the method will have a shifting tenor within different companies, and if so, will these companies implement the method with different approaches. Another aspect was to determine which types of challenges the companies were faced with during the transition towards CDE. To review whether the challenges were foremost organisational or development related. And how the organisations handled the communication and trust towards the co-workers and the development work within the organisation during the change towards the method. To highlight these issues, we presented theories with focus on organisational and technical challenges with the different Continuous practices were made. The practices being: Continuous Integration (CI), Continuous Delivery (CDE) and Continuous Deployment (CD). The theory chapter and former studies also contains research about surrounding concepts such as DevOps and LEAN methods, which can aim to facilitate the implementation of CDE. The empirical data collection was performed using open individual interviews with informants from six different companies, where they shared their experience and views on the method CDE. The study demonstrates that the reason organisations chose to implement CDE, is that they want to transform from software development methods, which requires a lot of decision making for any change, to a more flexible work procedure, in order to experience benefits such as: better quality of what is delivered, faster deliveries of business value to the customers and faster feedback-loops. Organisations that make the transition towards CDE also tend not to automate all the way to production, as in agreement with CD, this because the organisations identify challenges with assuring that the quality is sufficient. The study has identified a number of factors that are essential for a successful implementation of CDE, along with factors that may result in a less successful implementation.