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.

Currently many organizations are transitioning from the traditional approach to the agile approach regarding systems development methods. It is evident that research has mainly focused on smaller organizations transitioning, whilst less focus has been given t0 larger organizations. We find this interesting and the purpose of this study is to gain a deeper and broader knowledge concerning the following research question: How is system development work affected by a change from traditional system development methods to Scrum in large global organizations. We also investigate how Scrum can be adapted to complex projects with an internal client. The study is based on a case study, which takes a qualitative approach with semi-structured interviews for information gathering and was conducted on a major Swedish telecom company.

Internal communication is an important factor in organisations today. For many system development teams it?s critical that the communication works well. Without communication, success would be impossible. This study aims to highlight the effect communication has on the members of agile project teams.

This thesis was made possible by the company Verendus system AB, which is the leading developer of dealership management systems in the caravan and camper market. The goal of the thesis was to create a statistics module for a new producer system envisioned by Verendus. The new system is aimed at manufacturers and importers of caravans and campers, with the goal of enabling its users to create more effective production lines. By providing statistical data to mentioned users they will be able to predict market trends and customize their production lines accordingly. Today such software does not exist which leads Verendus to think that its arrival would lead to a success on the market.Before the development and design of the producer system began, a new agile method had to be developed, MAM (Minimum Agile Method).

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.

The Thesis purpose is in the context of system development validate the Scrum Methodology. Projects concerning information technology are difficult to manage and tend to fail in quality, time or costs. Scrum presents a new view of the system development. Better cooperation between customers and developers, continuous follow-up on daily basis and extensive communication in the development team are all characteristics of Scrum. Scrum is described as a new paradigm by its founders but has been criticized by experts of system development too.

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.

This thesis examines the multiplatform design issues of a development project using agile project methods and how they were resolved. Data was gathered through observation, photography and keeping of a journal using action research as a methodological framework. The thesis is concluded with recommendations on how to deal with these issues in similar projects under similar conditions..

Internal communication is an important factor in organisations today. For many system development teams it?s critical that the communication works well. Without communication, success would be impossible. This study aims to highlight the effect communication has on the members of agile project teams.

Projects are often spoken of in the terms of rational systems. However, some researchers point out the relevance of viewing projects as sets of relationships. Little is published about what aspects of relationships that are important for the managing of projects. We have argued for the necessity of such research. With previous research, our case study and interviews we indentified communication, responsibility, cooperation, togetherness and trust as important relational aspects in projects.The overall perceived success for projects in this case, was increased with the adoption of new Agile methods.

 AbstractSystem 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.

In a dynamic and unpredictable reality, either rigid structures or silo architectures areappropriate ways to organize an agile organization. This thesis enlightens these relationsbetween Service Oriented Architecture (SOA) and an organization who acts in a varied andconstantly changing business environment. In other words, this thesis enlightens the question:?How suitable is SOA to organize the enterprise who will meet a constantly changing andheterogenic business environment?.The thesis presents a model where an efficient organization must be agile to be able to actquickly in the business environments with constantly changing desires, needs, expectations,desires etc. According to the same model a Service Oriented Architecture organizes theenterprise elements such as processes, resources, competences, responsibilities, informationsystems etc.

Systems development methods has always been an important part of the systems development process. It affects not only the product, but also the organization itself. Today more and more companies are abandoning the more rigid traditional methods for the more flexible agile ones. A transition like this is bound to affect the product and the organization, but in what ways? Is it a difficult transition to make, and how does it affect social environment and dynamics? Does it change how people communicate information to each other? This study was conducted at a local branch of a larger international IT-company.

Bakgrund:Företagens villkor utifrån ett konkurrensperspektiv ändras idag fortare än någonsin och möjligheterna att nå framgång bygger i högre grad på en förmåga att förutse, anpassa sig till och agera på omvärldens snabbt föränderliga krav. Flertalet forskare redogör för att företags lednings- och styrkoncept måste förändras för att tillgodose de behov som den moderna globala marknadens dynamik ställer. De senaste decennierna har Lean och Agile trätt fram som två lednings- och styrkoncept som vunnit i popularitet och anammats av många företag som önskar effektivisera sin verksamhet. Både Lean och Agile använts främst inom produktion och det finns relativt lite forskning kring hur dessa två lednings- och styrmodeller appliceras inom andra verksamhetsområden samt hur de kan kombineras.Syfte:Syftet med denna studie är att undersöka hur ledningsgrupper inom en global IT- organisation använder sig av och kombinerar Lean och Agile, samt hur ledningsgrupperna upplever att detta påverkar deras arbetssätt och leveransförmåga.Metod:Studien är genomförd i form av en kvalitativ fallstudie av företaget Volvo IT. Insamling av data har skett via intervjuer med representanter för olika ledningsgrupper inom Volvo IT samt genom att sitta med vid möten och föra anteckningar och via insamlad dokumentation från websidor och intern företagsinformation.Slutsats:Resultaten visar på att Lean och agila arbetssätt tycks fungera bra ihop och kompletterar varandra väl.