Prioritering av icke-funktionella krav i praktiken
Ur ett agilt perspektiv
AgilePrioritizationRequirementsRequirements managementSoftware developmentAgilKravKravhanteringMjukvaruutvecklingPrioritering
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. I investigate prioritization of non-functional requirements and possibilities for agile project development. The results contribute to developing an overall understanding of the agile way of working.The methodology of this report follows a qualitative approach. It is based on secondary data from literature and documents, but also on data collected via interviews.The results are acknowledging earlier findings from the literature and illustrate with examples actual prioritization of non-functional requirements, and how and why prioritization is a complex activity at a company. However, according to one of the most important findings of this study, the strict use of prioritization techniques is not the most urgent necessity for the success of a project.