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. The company's current work processes are analyzed and presented, and all collected data will be reviewed. The results of the paper shows that no initial adaptation of agile methods, Scrum in this specific case, needs to be implemented and that there is no evidence to suggest that small organizations with small development teams can not work after a formal agile methodology. Finally, a general discussion of the study will be conducted and conclusions whether the study objective has been achieved or not will be discussed. / Denna uppsats ämnar undersöka huruvida en mindre organisation med små utvecklingsteam kan finna ett värde i att lämna en fungerande utvecklingsprocess för att följa en formell systemutvecklingsmetod, ifall dessa organisationer kan hitta ett metodstöd i agila systemutvecklingsmetoder och om metoderna i så fall behöver anpassas utefter organisationens unika förutsättningar. En traditionell plandriven systemutvecklingsmetod innehåller ett antal faser som genomförs sekventiellt och en slutförd fas kan i stort sett inte återupptas. Alla krav specificeras i början av ett projekt och endast en leverans av mjukvara sker. Detta kan medföra svårigheter med att hantera till exempel förändrade krav. Agila systemutvecklingsmetoder har för avsikt att hantera förändrade krav samt möjliggöra kontinuerliga leveranser av värdefull och fungerande programvara. Under uppsatsen kommer såväl traditionella plandrivna metoder som agila metoder att förklaras närmare. Metodval för forskningen och befintliga systemutvecklingsteorier kommer att diskuteras och ett företag där studien har bedrivits kommer att presenteras. Företagets nuvarande arbetsprocess analyseras och presenteras och alla datainsamlingar kommer att gås igenom. Resultatet av uppsatsen visar på att inga initiala anpassningar av agila metoder, Scrum i det här specifika fallet, behöver genomföras och att det inte finns något som tyder på att små organisationer med små utvecklingsteam inte kan arbeta efter en formell agil metod. Slutligen kommer en allmän diskussion om studien att föras och slutsatser gällande om syftet med studien har uppnåtts kommer att diskuteras.

<p>This exam paper has been a collaboration between the writers and SYSteam Utvecklingspartner in Huskvarna. The assignment was about finding a need for a mobile application, making a requirement specification document with design documents and parallel to this constructing a prototype. The assignment is summarized in the following questions:</p><p>• How can companies in the forest industry benefit from mobile information technology?</p><p>• How can a user centered perspective be used in the process of making the requirement specification document and the design documents?</p><p>• How do guidelines for usability apply to a mobile application?</p><p>Three visits to companies in the forest industry were made to find a need for mobile information technology solutions. After a small analysis of the different companies’ problems and conditions the decision was to use Tenhults Impregneringsverk AB in the case study.</p><p>We used the FA/SIM method in our job of finding the organization needs for change and the principles of User Centered Design in the work of constructing a prototype.</p><p>The result of our work is a requirement specification with design documents and a prototype. The final prototype is an application deployed on to a PDA with a barcode scanner.</p><p>Our conclusion is that the purpose of mobile information technology often is about making the torrent of information more effective by reducing the duplication of work and securing the quality of the information.</p><p>Using a user centered perspective in the development work has in general terms worked out pretty well for us. Requirements and demands of the application have become clearer to us after each iteration, and in the end the customer and the developer organization where on the same terms.</p><p>We have been able to apply the guidelines of usability on MobSaw (is the name of the application prototype that was made during the exam work). The principles are universal; the biggest difference is about input and screen size because the hardware’s capacity is limited. The advantages of the smaller frameworks for mobile devices is that the focus on usability increases.</p>

This exam paper has been a collaboration between the writers and SYSteam Utvecklingspartner in Huskvarna. The assignment was about finding a need for a mobile application, making a requirement specification document with design documents and parallel to this constructing a prototype. The assignment is summarized in the following questions: • How can companies in the forest industry benefit from mobile information technology? • How can a user centered perspective be used in the process of making the requirement specification document and the design documents? • How do guidelines for usability apply to a mobile application? Three visits to companies in the forest industry were made to find a need for mobile information technology solutions. After a small analysis of the different companies’ problems and conditions the decision was to use Tenhults Impregneringsverk AB in the case study. We used the FA/SIM method in our job of finding the organization needs for change and the principles of User Centered Design in the work of constructing a prototype. The result of our work is a requirement specification with design documents and a prototype. The final prototype is an application deployed on to a PDA with a barcode scanner. Our conclusion is that the purpose of mobile information technology often is about making the torrent of information more effective by reducing the duplication of work and securing the quality of the information. Using a user centered perspective in the development work has in general terms worked out pretty well for us. Requirements and demands of the application have become clearer to us after each iteration, and in the end the customer and the developer organization where on the same terms. We have been able to apply the guidelines of usability on MobSaw (is the name of the application prototype that was made during the exam work). The principles are universal; the biggest difference is about input and screen size because the hardware’s capacity is limited. The advantages of the smaller frameworks for mobile devices is that the focus on usability increases.