In recent years, Agile software development methods have become increasingly popular throughout the world. Today there are a number of different Agile methods and they all rest on the Agile Manifesto that was formulated in 2001 as a reaction to the traditional software processes.The aim of this thesis is to make a survey of some of the Agile methods used today and to see how they are being used in practice. It consists of two parts: a literature study and an interview study with people working in the software business. First, a definition of Agile methods is proposed and a number of different Agile methods are described. Second, the interviews are being analysed with special focus on communication, collaboration, expectations and results.

I detta arbete undersöker vi likheter och skillnader av hur litteraturen respektive utvecklare beskriver begreppet Agile. För att komma fram till ett svar på frågeställningen gör vi en litteraturstudie där vi genom att jämföra dem olika agila utvecklingsprocesserna tar fram kriterier för hur begreppet Agile beskrivs. Därefter gör vi intervjuer med representanter för 12 olika företag. Resultatet från dessa intervjuer ger oss ett svar på hur utvecklare beskriver Agile..

Agile as an idea was created in 2001 through the Agile Manifesto with focus on social relationships, communication and flexibility. This was a reaction to the traditional, hierarchical organization with the goal of restoring balance within organizations in the IT business. Today we can see a transit of Agile from the IT-industry to other industries and areas, such as HRM.There is a challenge in attempting to traditionally control a social idea such as Agile, and there is a lack of empirical studies of the organizational context and its effect on the interpretation of Agile in practice. This study is an attempt to connect Agile to the science of business administration.The purpose with this study is therefore to research the organizational contexts effects on the interpretation of Agile in practice, within IT and HRM. Where Agile is established or well known.To fulfill our purpose we chose social constructivism as our scientifically approach, and conducted 12 in-depth interviews.

Agile systems development has in recent years become very popular, and many companies today claims to be working Agile. At the same time there are studies about Agile system development that indicate that there are difficulties in fully adopting the Agile way. The purpose of this qualitative study has been to examine how true Swedish IT-companies conduct their Agile system development compared to Agile theory, and we have specifically for the purpose of the study designed a framework that has been used as an analytical tool. The framework helped us to maintain a structured and objective approach when we examined the participating companies and their practices. The study showed that there were differences regarding how true to Agile theory the different companies conducts their Agile projects, and that the differences in part depends on how long the companies have been working Agile.

This paper is a degree project on the C-level, 15 points at University West, Department of Business and IT dept. Informatics. This study is about Agile methodology and its impact on IT projects. Requirements management is a process within an IT project, where customer has certain requirements that must be met by an IT system. The difference between the traditional and Agile development is in the requirements management process and it can cause problems in a project.

Lean och Agile är två arbetsmetodsfilsofier utvecklade från produktion respektive IT. Denna rapport ämnar besvara hur dessa är relaterade och om filosofierna med fördel kananvändas inom motstående område. En teoretisk litteraturstudie har genomförts med sökningar i databaser efter relateradforskning. Detta gav en god inblick om de både områdena var för sig och även omanvändandet av Lean inom IT. Däremot saknades information om Agile inom produktion.

In recent time, Agile methods have been devoted much attention, and the concept is widely used in the IT industry in particular. An increasing number of companies are interested in this way of working. The following report is the result of a study on the ability to create value for customers in business development through the use of Agile methods. We ask what the advantages and limitations of Agile methods are in the creation of customer value. Grounded Theory and an initial literature review was used to answer this question.

In recent time, Agile methods have been devoted much attention, and the concept is widely used in the IT industry in particular. An increasing number of companies are interested in this way of working. The following report is the result of a study on the ability to create value for customers in business development through the use of Agile methods. We ask what the advantages and limitations of Agile methods are in the creation of customer value. Grounded Theory and an initial literature review was used to answer this question.

This paper is a degree project on the C-level, 15 points at University West, Department of Business and IT dept. Informatics. This study is about Agile methodology and its impact on IT projects. Requirements management is a process within an IT project, where customer has certain requirements that must be met by an IT system. The difference between the traditional and Agile development is in the requirements management process and it can cause problems in a project.

Detta arbete är ett examensarbete på C-nivå, 10 poäng vid Luleå Tekniska Universitet, avd. Data och Systemvetenskap. Arbetet behandlar traditionell systemutveckling jämfört med Agile tänkandet. Detta sker genom en jämförelse av vilka olika faktorer som påverkar utvecklingsprocessen tidsmässigt i vattenfallsmodellen jämfört med Extrem Programmering. Vi har identifierat tiden som en av faktorerna vilka bidrar till att många projekt misslyckas under traditionella systemutvecklingsprocesser.

Due to fast growing and rapid changes in markets today, most of the organizationsthat are trying keep up with these changes have a high demand for software that areof high quality and comes with a low price. To meet these goals software companieshave to implement new methods to develop software that are suited for rapidchanges. The concept of Agile methods can fulfill this need. Our purpose with thisthesis was to investigate how well Agile methods could be applied in organizationsthat could be identified as adhocracies. A case study was conducted in anorganization which we could identify as an adhocracy.

This paper aims to investigate whether a small organization with small development teams can find a value in leaving a functioning development process to follow a formal systems development methodology, if these organizations can find support in an Agile systems development method and in such case the method needs to be adjusted according to the organizations unique conditions.A traditional plan-driven system development methodology includes a number of phases that are carried out sequentially and a completed phase can basically not be resumed. All requirements are specified at the beginning of a project and at the end of the project only one delivery of software take place. This can cause difficulties in for example dealing with changing requirements. Agile system development methods intend to deal with changing requirements and to enable continuous delivery of valuable, working software.In this paper, both the traditional plan-driven methods and Agile methods will be explained. Research methodology and existing system development theories will be discussed and a company where the study has been conducted will be presented.

Under sent 1990-tal bo?rjade utvecklare att bli mer och mer missno?jda med ra?dande arbetsformer i projekt. Utvecklarna upplevde att modeller som vattenfallsmodellen inte la?ngre speglade verkligheten fo?r utvecklingen. Detta missno?je resulterade i att en ma?ngd nya arbetsmodeller uppstod och 2001 samlades de under Agile Manifesto.

Det finns många undersökningar som över tid visar att större delen av alla IT-projekt som påbörjas upplevs som misslyckade av beställaren.De agila metoderna involverar beställaren i hög grad i projektet. Frågan vi vill få svar på är: Vilka effekter får ett projektarbetssätt, med sin grund i Agile Manifestos värderingar, på beställarens upplevelse av projektet och systemet som utvecklas? Vi ville undersöka om ett agilt arbetssätt bidrar på ett positivt sätt till systemutveckling vad gäller beställarens nöjdhet med projektet och leveransen. För att sammanfatta olika agila metoder konstruerade vi ett ramverk. I detta ingår Agile Manifesto samt ett antal, av oss identifierade, kärnbegrepp och styrmedel.

Requirements management is an important part of the software development process. The success of a project may depend on how this is handled. Even though several research studies indicates that more attention should be paid on non-functional requirements, the primary focus in practical projects still regards identifying functional requirements. Especially the prioritization of the non-functional requirements has been proven to be of great importance for the success of a project.This report investigates basics in Agile requirements management involving opinions from experts from a software development company. This is done with help of existing literature and interviews with key actors involved in prioritization at the company.