Projektstyrning är viktig och IT-projektledaren har en avgörande roll för ifall IT- projekt lyckas eller inte. Dock är det en stor utmaning att leda IT-projekt och att få den effekt som önskas genom exempelvis tidplan, budget och resurser. Samtidigt tar digitaliseringen hela tiden samhället framåt och kunskapen som samlas in efter avslutade IT-projekt gör att lärdomarna ständigt växer. Likväl är det fortsatt få IT- projekt som lyckas. Enligt tidigare forskning är två av huvudfaktorerna som avgör huruvida ett projekt anses lyckas eller inte, tid och budget. Vidare utgör IT-projektledaren dess mest betydande roll i början av projektet, men att löpande och god kommunikation, samt med ett flexibelt ledarskap, är viktiga hörnstenar för att lyckas med projektet. Denna studies syfte har varit att undersöka och få en bättre förståelse för varför IT- projekt lyckas eller inte lyckas utifrån projektledares perspektiv. För att besvara detta syfte har följande forskningsfrågor ställts: Hur beskriver projektledare de kritiska framgångsfaktorerna i ledningen av ett IT-projekt? och Hur beskriver projektledare utmaningarna i ledningen av ett IT-projekt?. En kvalitativ undersökningsmetod har tillämpats där semistrukturerade intervjuer har genomförts med sex IT-projektledare vid ett stort IT-företag i Sverige. Intervjufrågorna har behandlat områden som projektledning och vilka framgångsfaktorer samt utmaningar projektledare upplever vid IT-projekt. Resultatet av studien visar att för att lyckas med ett IT-projekt utifrån projektledarens perspektiv, är nyckeln för framgång god kommunikation, att kunna prioritera rätt, samt god kravhantering. Vidare bör projektledaren ha en god förståelse för systemet, besitta tekniska färdigheter, samt ha en god förståelse för IT-komponenter såsom beroenden och kopplingar. Slutligen utgör även resurser, budget och avsatt tid avgörande faktorer. Projektledarna menar samtidigt att på grund av den komplexitet IT-projekt ofta utgörs av, är det utmanande att göra relevanta ändringar i projektet som passar samtliga intressenter, den egna projektgruppen inkluderat. Det är dessutom ofta en utmaning för projektledaren att kunna förstå och förklara den kundnytta ett IT-projekt kan medföra, återigen på grund av komplexiteten vid IT- projekt. Att som projektledare även kunna prioritera rätt, samt att ha de rätta resurserna redo, har visat sig vara en utmaning för många. Sedan är det utmanande när intressenter har ett tydligare fokus på business än den tekniska delen. / Project management is important and the IT project manager has a crucial role in whether IT projects succeed or not. However, it is a great challenge to lead IT projects and to get the desired effect through, for example, schedule, budget and resources. At the same time, digitalization is constantly moving society forward and the knowledge that is gathered after completed IT projects means that the lessons are constantly growing. Nevertheless, there are still few IT projects that succeed. According to previous research, two of the main factors that determine whether a project is considered successful or not are time and budget. Furthermore, the IT project manager has its most important role at the beginning of the project, but that continuous and good communication, and with a flexible leadership, are important cornerstones for success with the project. This study’s purpose has been to investigate and gain a better understanding of why IT projects succeed or fail from the project manager's perspective. To answer this purpose, the following research questions have been asked: How does the project manager describe the critical success factors in the management of an IT project? and How do project managers describe the challenges in managing an IT project?. A qualitative survey method has been applied where semi-structured interviews have been conducted with six IT project managers at a large IT company in Sweden. The interview questions have dealt with areas such as project management and what success factors and challenges project managers experience in IT projects. The results of the study show that to succeed with an IT project from the project manager's perspective, the key to success is good communication, being able to prioritize correctly, and good requirements management. Furthermore, the project manager should have a good understanding of the system, possess technical skills, and have a good understanding of IT components such as dependencies and connections. Finally, resources, budget and time allotted are also important factors. At the same time, the project managers believe that due to the complexity that IT projects often consist of, it is challenging to make relevant changes to the project that suit all stakeholders, including their own project group. In addition, it is often a challenge for the project manager to be able to understand and explain the customer benefit an IT project can bring, again due to the complexity of IT projects. As a project manager, being able to prioritize correctly, as well as having the right resources at hand, has proved to be a challenge for many. Furthermore, it is challenging when stakeholders have a clear focus on business rather than the technical part.

The high rate of failed IT projects has become a real and relevantconcern of many businesses. Businesses are dissipating theirresources on failed IT projects. More often, IT projects fail toachieve most of their intended purpose of increasing productivity,lowering operating costs, improving the quality of work. Althoughthere have been many studies done through the years in an attemptto find the causes behind IT-project failure, there is still noconsensus about the underlying causes. The question itself iscomplex with many different aspects to consider. The researcherswithin this field mostly acknowledge this problem. Against thisbackground, the primary focus of this study is to explore what theclients within the IT-projects think about the way IT-projects areconducted and what they think has to be done to better the chancesof success for these projects. For the outcome of this study to bewell-founded interviews were also done with those responsible onthe supplier side in order to cover both sides viewpointconcerning the IT-projects. The way IT-projects are conducted nowseems to have a process-based approach to the problem that has tobe solved, this is because the project has to go through a numberof steps that have been defined before the project has even begun.The fact that the upcoming project has a predefined plan to followis not the problem since it is reasonable to have a plan for theupcoming project. Having a predefined plan for the upcomingproject without really understanding the problem that has to beaddressed in detail through the IT-project is a major problem. This study has proven that it is very common that the peopleinvolved in an IT-project do not understand each other whilediscussing the project. This leads to the conclusion that the waythat IT-projects are conducted right now, where the supplier ofthe IT-solutions even if they have extensive experience fromconducting IT-projects and therefor say that “we know what has tobe done” to put more emphasis into understanding the problem thathas to be solved through consultation with the client. The need toput more emphasis on understanding the client is something that isalso confirmed through various models presented in this study.

<p><strong>Problem: </strong>How does project managing appear in small IT-consulting companies and how does the project manager carry out their projects to create successful solutions for their customers?</p><p><strong>Purpose: </strong>The research has the purpose to analyze and review how IT-consults in small companies work and lead their projects to create profitability for the company, which leads to a good development for the company. </p><p><strong> </strong><strong>Methodology: </strong>The research is made on eight research objects in IT-consulting business and the sizes of them are between 1-49 employees. The research is made with a qualitative method to get closer to the research objects. Therefore the research is made in forms of interviews. The analysis is grounded on a comparison between the research data and the theories that are used in the research.</p><p><strong>Theoretical perspectives: </strong>The theories which have been used in the research are Involvement theory (Fill, 1999), PAFF-metoden (Marcusson & Ahlin, 2002), Projektledning (Tonnquist, 2006), Jakten på det effektiva projektet (Engwall, 1999) och Mervärde (Grönroos, 2002)</p><p><strong>Empirical foundation: </strong>The research data<strong> </strong>are founded from the interviews of the eight research objects, they have the fictive names: Gondor, Minas Morgul, Minas Tirith, Mordor, Osgiliath, Rivendell, Rohan and The Shire.</p><p><strong> </strong><strong>Analysis/Result:</strong> Each study object starts their projects with a pre-study phase, as the PAFF-method describes it. Each study object majorly involves their customers, which is equal to Fill’s theory about high involvement buying processes. This shows that the study objects are aware that they sell solutions that require high involvement of the customers. Four of the study object enjoy seeing that the customer contributes with high engagement and maintain a good level of ambition for the project; this is consistent with Engwall’s theory about organizational ideal types. </p><p><strong>Conclusion:</strong> The project manager chooses not to rupture the present institutionalism. The project manager initiates the project with a pre-study phase. The project manager is sure to involve their customers. The service guaranty the project manager uses is “problem-free-guaranty”. The role of the project manager is to plan and organize the project; the project manager should also be a good communicator.<strong></strong></p>

Problem: How does project managing appear in small IT-consulting companies and how does the project manager carry out their projects to create successful solutions for their customers? Purpose: The research has the purpose to analyze and review how IT-consults in small companies work and lead their projects to create profitability for the company, which leads to a good development for the company.   Methodology: The research is made on eight research objects in IT-consulting business and the sizes of them are between 1-49 employees. The research is made with a qualitative method to get closer to the research objects. Therefore the research is made in forms of interviews. The analysis is grounded on a comparison between the research data and the theories that are used in the research. Theoretical perspectives: The theories which have been used in the research are Involvement theory (Fill, 1999), PAFF-metoden (Marcusson &amp; Ahlin, 2002), Projektledning (Tonnquist, 2006), Jakten på det effektiva projektet (Engwall, 1999) och Mervärde (Grönroos, 2002) Empirical foundation: The research data are founded from the interviews of the eight research objects, they have the fictive names: Gondor, Minas Morgul, Minas Tirith, Mordor, Osgiliath, Rivendell, Rohan and The Shire.  Analysis/Result: Each study object starts their projects with a pre-study phase, as the PAFF-method describes it. Each study object majorly involves their customers, which is equal to Fill’s theory about high involvement buying processes. This shows that the study objects are aware that they sell solutions that require high involvement of the customers. Four of the study object enjoy seeing that the customer contributes with high engagement and maintain a good level of ambition for the project; this is consistent with Engwall’s theory about organizational ideal types.  Conclusion: The project manager chooses not to rupture the present institutionalism. The project manager initiates the project with a pre-study phase. The project manager is sure to involve their customers. The service guaranty the project manager uses is “problem-free-guaranty”. The role of the project manager is to plan and organize the project; the project manager should also be a good communicator.

This dissertation investigates how executives engage in information technology projects and how organizational control of IT projects forms and evolves over time. It contains an in-depth account of a large, multi-year IT project in a financial company. The story of the “New Deposit System” project provides insights into the dynamics of IT projects in organizations and the challenges facing executives engaging in the governance of these complex undertakings. Several characteristics of IT projects, such as their abstract nature, technological complexity and non-repetitiveness, render several of the manager’s trusted forms of control impracticable. Even the ideal of “strong top management support” is found to be problematic: it is an extraordinary measure unlikely to translate well into regular organizational practice. What we find instead are actors in search of means and ways to exercise influence. We find control to be reciprocal and dynamic, influenced by the organization and its history, by the principles and practices of corporate IT management and by the values and norms of the IT profession. In this environment, selection of key people, evolving trust, other people’s assessments and the construction and reshaping of a project image become important parts of the managerial repertoire for IT project governance. / Diss. Stockholm : Handelshögskolan, 2002

Det finns forskning från flera olika perspektiv som har studerat kritiska framgångsfaktorer gällande arbete i projekt. Det problem som finns är att det inte finns ett specifikt genomförande för att uppnå lyckat resultat inom projektarbeten. Belassi och Tukel (1996) har tagit fram en teori att analysera projektgenomförande utifrån. Modellen behöver utvecklas med tiden och förändras för att anpassas till specifika typer av projekt, till exempel interna IT-projekt som denna undersökning behandlar. I den här studien har en fallstudie genomförts på två verksamheter där det i varje verksamhet finns ett intern IT-projekt som anses vara lyckat och ett som anses vara misslyckat. Med grund i Belassi och Tukels (1996) teori Critical success/failure factors in projects har kvalitativa intervjuer genomförts i syfte att ta reda på vilka framgångsfaktorer som är kritiska för lyckade och misslyckade interna IT-projekt. Vidare är syftet även att se om det finns andra kritiska framgångsfaktorer som kan utveckla teorin. Den insamlade empirin analyserades genom kategorisering och studiens resultat visar vilka de kritiska framgångsfaktorerna är för de två verksamheternas utvalda interna IT-projekt. Det har även skapats en utvecklad modell med kritiska framgångs- och misslyckandefaktorer som inte tidigare fanns omnämnda i teorin men som visade sig ha en inverkan på projektets resultat. Studien visade att ledarskap och kommunikation var viktiga faktorer för att uppnå framgångsrika projekt. Det visade sig också att det inte enbart var projektdeltagarnas tekniska bakgrund som spelade in utan även annan kompetens hos individerna. I de fall då det inte uppfattats som att någon utvärdering var gjord ansåg flera individer att det hade varit bra om det hade genomförts. Projektdeltagarnas kompetens och utvärdering av projektets genomförande var därför, tillsammans med externa leverantörer och användarnas stöd, faktorer som valdes att kompletteras i den vidareutvecklade modellen. Projektgruppen engagemang tas redan upp i Belassi och Tukels (1996) teori, men det framhävs i undersökningen att engagemanget bör vara objektivt. / There is research from several different perspectives that have studied the critical success factors regarding to project work. The problem is that there is not a specific project transact to achieve success in projects. Belassi and Tukel (1996) has developed a theory that can be used to analyze the implementation of projects. The theory needs to evolve over time and change in order to adapt to specific types of projects such as internal IT projects that this study addresses. In this study a case study carried out in two organizations where each one of them consist one internal IT project that is considered successful and one that is considered a failure. Based on Belassi and Tukels (1996) theory Critical success/failure factors into projects, qualitative interviews were conducted in order to determine which success factors that are critical to the success and failure of internal IT projects. Furthermore, the aim is also to see if there are other critical success factors that can develop the theory. The collected empirical data was analyzed by categorization and the results of this study show which the critical success factors is in the internal IT projects. A new model was created and developed with critical success and failure factors that did not exist in the previously mentioned theory but which turned out to have an impact on the project results. The study showed that leadership and communication were key factors in achieving successful projects. It also turned out that not only was the project participants' technical backround important to project success but also other skills of the individuals. In cases where it is not perceived as an evaluation was made most of the informants said that it would have been good if it had been done. Project participants' skills and evaluation of the realization of the project was therefore, together with external suppliers and user support, factors that were chosen to be supplemented in the refined model. The project team commitment are already addressed in Belassi and Tukels (1996) theory, but it is emphasized in the survey that the commitment should be objective.

Agila metoder och modeller ses ofta som nytänkande och används idag flitigt av företag och organisationer runt om i värden. I realiteten är grunden till det agila metoderna idag 13 år och mycket har hänt, både teknisk och kring sättet vi arbetar, sedan 2001. Den agila metodiken baseras på två dokument, det agila manifestet och de agila principerna, där principerna är till för att konkretisera manifestet. Eftersom principerna är konkreta anser vi att de har en stark koppling till hur agil utveckling de facto bedrivs. Vi har därför valt att undersöka hur principerna står sig bland utvecklarna över ett decennium efter att de skrevs samt om utvecklarna ser ett behov av revidering och vilka delar de i så fall skulle vilja förändra. För att ta reda på detta genomförde vi fyra intervjuer med utvecklare som alla hade olika erfarenhet av agilt arbete samt utgick från en tidigare kvantitativ undersökning i ämnet. Slutsatsen av undersökning är att de agila principerna fortfarande står sig bra bland utvecklarna men att det finns ett behov av revidering. Original utformningen är dock så pass väl fungerande att behovet inte är omedelbart. Det finns flera ämnen som våra respondenter tagit upp som är viktiga att ta hänsyn till där kvalitet och dokumentation är de ämnen som står ut i mängden. I mångt och mycket överensstämmer vårt resultat med den undersökning vi utgått från vilket tyder på att den bild som förmedlas av de båda undersökningarna har en god förankring hos utvecklarna, även om det finns områden där våra resultat skiljer sig från varandra. / Agile methodology and models has a wide group of supporters among organizations and companies and is often seen as innovative. The agile methods are now 13 years and a lot has happened since then, both in our ways of working and in the technology we use. The agile methodology is based on two documents, the agile manifesto and the agile principles. The principles embodies the manifesto and in our view creates a strong connection with reality and by that a strong connection with how software is developed. To find out if the principles still are viable and used among developers and if a revision of them is needed we performed a survey based on four interviews and a previously conducted quantitative study. The conclusion of this survey is that the principles are used and works well in development projects and are well thought of by the developers but there is still a need for a revision. How this revision would look and when it should be done is hard to say, the need for it aren’t urgent because of the general support of the original principles are still strong. There are a couple of different areas that our respondents point out as important where quality and documentation stands out as the most important that organizations working agile have to focus on in their daily work. Our survey and the study we used as an inspiration ends up in mostly the same conclusions with only few differences, which we see as a confirmation that our study reflects the developers’ view.

IT är ett naturligt hjälpmedel för många företag och organisationer. Det är därför vanligt att företag försöker effektivisera och förbättra sin verksamhet genom att införa nya affärssystem. När ett nytt affärssystem ska införas startas ofta ett IT-projekt med en utsedd projektledare som ansvarig för att nå önskat resultat. IT-projekt är av teknisk karaktär och fokuserat mot själva affärssystemet. Det krävs dock i många fall mer än den nya teknologin för att ett företag ska öka sin lönsamhet och förbättra verksamheten. I dessa fall krävs det även någon typ av förändring eller omstrukturering inom företaget för att nå det önskade målet. I de fall någon typ av förändring utöver införande av ett affärssystem krävs, inträffar det att projektledaren får ta på sig uppgiften att även leda denna förändring. Organisationen kan dock göra valet att låta den förändringen ledas av en förändringsledare. En förändringsledares uppgift är att ansvara för att ett förändringsarbete når sitt mål med önskat resultat. Syftet med denna uppsats är att undersöka och beskriva vilka betydelser rollerna projektledare och förändringsledare har i IT-projekt vars syfte är att införa ett affärssystem. För att skapa klarhet i detta har litteratur inom ämnet studerats. Utöver litteraturen har vi även tagit del av artiklar från olika tidskrifter. För att få en aktuell verklighetsanknytning har ett antal intervjuer genomförts med personer som arbetar i projektmiljö och har kontakt med projekt- och förändringsledarskap dagligen. Denna kombination av informationskällor, anser vi, skapar en aktuell och tydlig bild av området. I förstudien bör målet med projektet analyseras för att säkerställa att rätt åtgärder genomförs. Vi har kommit fram till att rollerna projekt- och förändringsledare har stor betydelse och positiv inverkan för att önskat resultat ska nås i IT-projekt. Projektledaren står för den tekniska kompetensen, medan förändringsledaren arbetar med de mänskliga faktorerna. Det kan därför vara fördelaktigt för projektet om rollerna innehas av separata personer. På detta sätt får de mycket utbyte och hjälp av varandra vilket leder till större möjligheter att IT-projektet når önskat resultat och införandet av affärssystemet lyckas. / In the business environment of today IT systems have a significant role in many enterprises and organisations. A focus for many companies is to enhance profitability and efficiency buy improving and developing their enterprise systems. When a decision is made to redesign or implement a new business system it’s common that an IT-project is started and a dedicated project leader is assigned to the project, committed to deliver the requested results. An enterprise system is usually technical in it’s nature and focuses on technical aspects, but to reach desired results in profitability and efficiency, several other aspects than the pure technical ones needs to be taken into consideration to reach the desired results. In these cases, a reorganisation of the business or other structural changes might be needed to reach the goals of the project. When an implementation of a business system reaches beyond the pure technical aspects and demands structural changes to the organisation, it’s not uncommon that the IT-project leader is assigned responsibility for the entire project. The organisation can on the other hand choose to assign a change manager to govern for the structural changes. The change manager is responsible for the whole change process and is assigned responsibility that the process reaches the pre defined targets. The purpose of this paper is to analyse and describe the roles of a project leader and change manager and their importance within an IT project aiming at implementing a new enterprise system. The sources of information to this paper is literature, scientific articles within the area and several interviews with professionals working in project environments, including project management and change management, on a day-to-day basis. We believe that this mix of information sources enables this paper give a clear and up to date view of the area of scope. In the pre study to a project is of sheer importance that the actual targets are analysed to ensure that the right decisions and actions are made. Our conclusion is that the roles of the project leader and the change manager are of significant importance to the outcome of the project. It is desirable that the two positions are assigned to two different persons, which enables them to share experiences and support each other. The project leader possesses the technical know how and the change manager focuses on the human and organisational aspects of the project. By setting the project up with clear areas of responsibility, but working beside each other, they can exchange experiences and help each other. This is beneficial for the project and increases the possibilities that the project reaches desired results and that the implementation of the new enterprise system is successful.

The main goal of this diploma thesis is to investigate the possibilities of the usage of Kanban system within a banking environment. To achieve this goal, the history, advantages, disadvantages and main areas of its usage are analyzed and described. Another goal of this thesis is to define the suitable terminology for Czech environment and to inspect the extent to which the concept of Kanban is compatible with the existing approaches and methodologies to project management. The market analysis of available software tools to support the concept of Kanban is performed (criteria definition, evaluation and final comparision). Based on all the previously described outputs a methodology to implement Kanban in banking environment is designed.This methodology is then used in the final chapter of the thesis -- the case study from an international bank, providing middle management with a step by step guide to successfuly implement Kanban system.

This thesis deals with theory and practice of learning organizations applied to the IT project team. In theoretical part key definitions and terms related to the problems of the learning organization and the information society. At the same time gives a demonstrative interpretation of the self-learning organization by various authors and presents their specific models. As the fundamental, this thesis uses the theory of Peter Senge, with which it is being worked also in the practical part, where the IT project team is analysed of their behaviour, and compared to the results obtained with the theory of the five disciplines of Peter Senge. In conclusion there is a set of recommendations that could improve the functioning of the IT development team and achieve a greatest compliance with the learning organization concept.