Software development projects often fail. Recently the agile software development frameworks have been massively adopted and used to overcome the root causes of the project failure. The use of the agile frameworks results in the more successful delivery of smaller software development projects. Companies however implemented in the past many generic project management frameworks and still use them to manage the full portfolio of their projects especially the medium and large software development projects. In such cases the agile development teams are organized in projects that are managed by project managers according to these generic project management frameworks. Both these frameworks must be analysed and tailored carefully to be successfully applied together. The objective of this dissertation thesis is to design the agile software development project management framework based on PRINCE2 and Scrum frameworks. The benefits of this new framework are the enrichment of the simple agile framework Scrum by project management elements and the enrichment of the generic project management framework PRINCE2 by the agile principles and agile team management practices. The first part of the thesis is focused on the analysis of project management and agile development frameworks. The main focus is on the current usage, the measurement of the project success and the identification of problems that the projects face to. Prior to the design of the new framework the research was executed in the global company to discover the specific problems in software development projects and to measure the actual project success rate. The framework is then designed in the next part. The framework was successfully implemented in the same global company and the project success rate was again analysed. The result is positive and the implementation of this framework resulted in the improved project success rate. Also two additional case studies were conducted to check the viability of the designed framework.

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.