Byte av systemutvecklingsmetod : En verksamhetsnytta eller en nödvändighet?

Abstract System methodology is in the very heart of system development, it is a crucial part of how you define your work, how you choose to approach the actual problem at hand and how to solve it. Researchers in the system development field has shown that not all methods in theory are in compliance with how it is practiced by the companies who use them. In our thesis we have studied a larger international IT- company and one of their local offices in Sweden, who some years back changed their system development method from a more traditional to an agile one. Our aim of this study has been to establish whether both of these methods has differed between theory and in actual use, and if so, why this has occurred and what the underlying rationality might have been to promote this change. Our questions that we sought to answer were; 1. Why did the company change system development method in the first place? 2. If the methods, applied by the company, differs between theory and practice, why do they differ and what is the underlying rationality to pander this change? Our study has shown that in both cases, there has been a need to tailor the methods to fit the organizational objectives and goals but also the current working climate. Reasons for this has been, amongst others, that the methods at hand has not been in complete compliance with how they perform their work in practice. Statements from the interviewees were that it is hard to follow a method in strict accordance with how a method is written in theory, you have to conform it to the actual organization for it to be effective