In today’s society, IT-Companies often have a hard time estimating changed requirements. This leads to that the clients’ confidence is negatively affected and is one of the main reasons why this has to be improved. The goal with this study was to find out what the most common problems regarding this issue are in IT-companies that works with agile software development. By analyzing one IT-company through a SWOT- and pareto-analysis the most common problems have been ascertained. The SWOT analysis have been created through interviews with selected employees to get a better understanding of the problems that the IT-company is facing. Furthermore was the pareto-analysis based on a survey that was sent out to many different employees to prioritize the problems. The reason why the survey was sent to different employees was to get a more objective input. The study showed that there was many different problems that needed attention. The most important problems was that the communication towards the client regarding requirements needed to be improved, better communication internally between different departments needed to be established, a method to quickly adapt and estimate change in requirements needed to be implemented and finally a method regarding witch key employees whom need to attend the planning of the program backlog. These problems have then been studied through interviews with other IT-companies and through a literature study. The conclusions that where drawn was that the client needs to be involved and updated through the whole project. Constant monitoring and communication regarding changed requirements needs to be processed and mediated. High standards needs to be set early towards the client in order to obtain as clear an image of the requirements as possible. Many different parties need to attend to the planning process for the program backlog before the start of the project. The client needs to be aware of that changed requirements will arise and that this will lead to that the first estimation may not necessarily be absolute. As long as the client is held up to date as well as participant through the whole project and problems are detected and mediated early, change in requirements should not be a huge problem. This is after all the purpose of being agile. / I dagens läge har IT-företag svårt med att estimera förändrade krav vilket medför att förtroendet hos beställaren påverkas negativt och är en av hu-vudanledningarna till att det måste förbättras. Målet med studien har varit att försöka ta reda på de vanligaste problemområdena inom agil systemut-veckling bland IT-företag med hjälp av en SWOT- och pareto-analys. SWOT-analys konstruerades av intervjuer med anställda på ett IT-företag och an-vändes för att ta reda på problemområden. Pareto-analysen användes med hjälp av en enkät som skickades ut till anställda på samma IT-företag för att prioritera problemområdena. Enkätens svar bygger på anställda från de flesta avdelningar, vilket resulterar i en objektivare syn på resultatet. Under-sökningen har visat att det finns många områden som kan förbättras. De huvudsakliga områdena som behövde förbättras var tydligare kommunikat-ion gällande kravhantering gentemot kunden, bättre kommunikation mellan avdelningarna internt i företaget, införa en metod för att snabbt estimera samt anpassa sig till förändrade krav behövde implementeras och slutligen skapa struktur gällande vilka personer som bör delta i planeringen inför program backlog. De fyra största problemområdena har sedan undersökts med hjälp av intervjuer med andra företag och genom en litteraturstudie. Slutsatsen som drogs var att kunden behöver vara involverad och uppdate-rad genom hela projektet. Konstant uppföljning och kommunikation gäl-lande förändrade krav behöver bearbetas och förmedlas. Höga krav måste sättas på kunden i början för att få en tydlig och genomarbetad förståelse för kravspecifikationen som möjligt. Många olika parter bör vara med på planeringen inför program backlog innan projektets uppstart. Kunden bör vara medveten om att förändrade krav kommer att uppstå och att detta kommer att leda till att den första estimeringen inte nödvändigtvis kommer vara absolut. Så länge kunden är uppdaterad och delaktig genom hela pro-jektet och problem upptäcks samt förmedlas tidigt bör förändrade krav inte vara ett stort problem. Det är syftet med att vara agil.

Diploma thesis is focused on analysis of documentation method in business analysis team in chosen company. Based on this analysis it proposes elimination of identified weaknesses and risks by creating a tool for shared documentation in form of business architecture model and definitions of processes which will allow to build and maintain proposed method of documentation.

Requirements are important in software development, product development, projects, processes, and systems. However, a review of the requirements literature indicates several problems. First, there is confusion between the terms ?requirements engineering? and ?requirements management.? Similarities and/or differences between the two terms are resolved through a literature review; resulting in comprehensive definitions of each term. Second, current literature recognizes the importance of requirements but offers few methodologies or solutions for defining and managing requirements. Hence, a flexible methodology or framework is provided for defining and managing requirements. Third, requirements methodologies are represented in various ways, each with their respective strengths and weaknesses. A tabular view and hybrid graphical view for representing the requirements process are provided.

<p>Global software development has been a phenomenon of growing interest for almost past decade or so; and its adoption trend continues to gain momentum. Globally distributed work istaken up as an alternative to single-site mainly because of the economic and strategic benefits itoffers. Software development at geographically distributed environment is not a straightforwardtask and entails numerous challenges which are unique to this form of development.</p><p>Requirements change management is considered challenging even in the best of conditions andit becomes even harder when performed at geographically distributed development locations.There is no existing model for managing requirements change in globally distributed softwaredevelopment context.</p><p>This study uses qualitative research method to explore requirements change managementprocess and investigates the underlying causes of requirements change in geographicallydistributed software development. The research work proposes a model for requirementschange management for global software development. This model tries to incorporate the roles,activities and artifacts identified in the change management models.</p>

Effective management of information about client requirements in construction projects lifecycle can contribute to high construction productivity; within budget and schedule, and improve the quality of built facilities and service delivery. Traditionally, requirements management has been focused at the early stages of the construction lifecycle process where elicited client requirements information is used as the basis for design. Management of client requirements does not extend to the later phases. Client requirements often evolve and change dramatically over a facility's life. Changing client requirements is one of the principal factors that contribute to delays and budget overruns of construction projects. This results in claims, disputes and client dissatisfaction. The problems of current requirements management process also include: lack of integrated and collaborative working with requirements; lack of integrated requirements information flow between the various heterogeneous systems used in the lifecycle processes, and between the multiple stakeholders; inefficient and ineffective coordination of changes within the lifecycle processes; manual checking of dependencies between changing requirements to facilitate assessment of cost and time impact of changes. The aim of the research is to specify a better approach to requirements information management to help construction organisations reduce operational cost and time in product development and service delivery; whilst increasing performance and productivity, and realising high quality of built facilities. In order to achieve the aim and the formulated objectives, firstly, a detailed review of literature on related work was conducted. Secondly, the research designed, developed and conducted three case studies to investigate the state-of-the-art of managing client requirements information. A combination of multiple data collection methods was applied which included observations, interviews, focus group and questionnaires. Following this, the data was analysed and problems were identified; the necessity for a lifecycle approach to managing the requirements information emerged. (Continues...).

Esta dissertação aborda a gestão de requisitos ou Requirement Management (RM) e a gestão de parâmetros críticos CPM (do inglês Critical Parameters Management) relacionadas com o processo de desenvolvimento de produtos (PDP). Assim, o objetivo geral deste trabalho é analisar os parâmetros críticos através da revisão e inserção das atividades da CPM e da RM ao longo do PDP. Esta análise enfatiza a utilização de ferramentas e modelagem estatística. Este estudo contempla a reorganização das fases de RM e CPM propostas na literatura numa seqüência lógica utilizando ferramentas aplicáveis ao PDP. Esta proposta contempla fases exemplificadas por meio de um caso real. Como objetivos específicos para alcançar o objetivo traçado, citam-se: (i) demonstrar a inserção das atividades relativas à gestão de requisitos de produto e à gestão de parâmetros críticos ao longo das fases do PDP, revisando as fases e as sobreposições numa continuidade temática; (ii) apresentar uma proposta de reorganização das fases da RM para o desenvolvimento de um novo produto por meio de um exemplo didático; (iii) identificar os parâmetros críticos a partir de uma análise dos sistemas, subsistemas e componentes (SSC’s) de um novo produto utilizando opinião de especialistas e análise estatística. Para cada objetivo específico foi gerado um artigo. O método de pesquisa utilizado neste trabalho foi de natureza aplicada, de abordagem qualitativa-quantitativa com objetivo exploratório e o procedimento técnico utilizado foi o estudo de caso. Como resultados principais deste trabalho destacam-se a revisão de atividades para o desdobramento dos requisitos em parâmetros críticos relacionada ao PDP suportada por técnicas e ferramentas, proporcionando um maior entendimento de como estas atividades podem ser encadeadas e utilizadas simultaneamente. A proposta culmina com a identificação de parâmetros críticos a partir dos requisitos do produto e da análise dos SSC’s de um novo produto utilizando a opinião de especialistas e a modelagem estatística. / This thesis addresses the requirements management (RM) and critical parameters management (CPM) related to the product of development process (PDP). The objective of this work is to analyze the critical parameters through the review and integration of activities of the CPM and the RM along the PDP. This analysis emphasizes the use of tools and statistical modeling. This study includes the reorganization of methods of RM and CPM proposed in the literature in a logical sequence using tools that can be applicable to the PDP. Stages of this insertion of activities are exemplified through a real case. The specific objectives to achieve the goal tracing: (i) demonstrate a review and integration of activities related to management of product requirements and management of critical parameters during the phases of the PDP; (ii) present a proposal for reorganization of the phases of requirements management in development a new product through a didactic example and (iii) identify critical parameters through analysis on systems, subsystems and components (SSC's) of a new product, using expert opinion and statistical analysis. For each aim it was written an article. The research method in this study is of qualitative-quantitative nature and the technical objective procedure used was a case study. As main results of this work stand out the review of activities for the unfolding of the requirements in critical parameters related to the PDP supported by tools and techniques, providing a greater understanding of how these activities can be linked and used simultaneously. The proposal culminates with the identification of critical parameters from the product requirements and analysis of the SSC's of a new product using expert opinion and statistical modeling.

This diploma thesis deals with the areas of requirements management in large organizations, especially banks. Bank projects have their own characteristics, as well as the banking environment as such. The paper will analyze the problem of requirements management in general and during description of best practices and methodological procedures attention will be drawn to the peculiar characteristics of the banking environment. This thesis focuses mainly on methodological and personal aspects of requirements management - the role of the analyst and the requirements management methodology. One of the main goals is selection of requiremets management methodology suitable for use in banks. Other important objectives are the description of best practices and mapping of the description of requirements management in the most widely used software development methodologies. The paper can serve as a textbook for junior analysts and other team members, or as a reference guide. Well-educated analyst and knowledgeable project team members enhance probability of a successful completion of the project and objectives achievement within set deadlines, budget and to everyone's satisfaction.

Global software development has been a phenomenon of growing interest for almost past decade or so; and its adoption trend continues to gain momentum. Globally distributed work istaken up as an alternative to single-site mainly because of the economic and strategic benefits itoffers. Software development at geographically distributed environment is not a straightforwardtask and entails numerous challenges which are unique to this form of development. Requirements change management is considered challenging even in the best of conditions andit becomes even harder when performed at geographically distributed development locations.There is no existing model for managing requirements change in globally distributed softwaredevelopment context. This study uses qualitative research method to explore requirements change managementprocess and investigates the underlying causes of requirements change in geographicallydistributed software development. The research work proposes a model for requirementschange management for global software development. This model tries to incorporate the roles,activities and artifacts identified in the change management models.

In this thesis the software development process and in particular, the requirements management processes in a major software development company have been investigated. The current problems related to requirements quality and process performances have been identified. Process improvement measures have been proposed based on the suggestions found in the relevant literature. The current process and the improved version have been compared with respect to the process evaluation metrics proposed particularly for software process improvement.

<p>Det problemområde som behandlas i arbetet är den del av systemutvecklarens arbete avsett att hantera förändringar i kravbilden under systemutvecklingens hela livscykel, kallat Requirements Management (RM). Arbetet fokuseras på detaljer kring spårbarhet inom förändringshantering.</p><p>För att lyckas i spårbarhetsarbetet gäller det för systemutvecklaren att se hur de olika krav som finns i kravbilden är relaterade till varandra och var kraven har sitt ursprung. Det skiljs inom spårbarhetsområdet mellan framåt- och bakåtriktad spårbarhet. Vardera spårbarhetsriktningen delas sedan in i två steg från kravursprung framåt via kravdokumentation till realisering då det gäller den framåtriktade och från realisering via kravdokumentation till kravursprung då det gäller den bakåtriktade.</p><p>En studie har genomförts där litteraturens syn har jämförts med ett antal respondenters då det gäller att dels kartlägga vilka typer av spårbarhet som behövs inom systemutvecklingsprojekt och dels vilket stöd som behövs för att etablera och underhålla denna spårbarhet.</p>