Agile Requirements Engineering with Prototyping in Small Software Projects: An Action Research Case

dc.contributorAalto-yliopistofi
dc.contributorAalto Universityen
dc.contributor.advisorKujala, Sari
dc.contributor.authorMonkam Ngatcheu, Marie
dc.contributor.schoolPerustieteiden korkeakoulufi
dc.contributor.supervisorKauppinen, Marjo
dc.date.accessioned2021-03-21T18:10:53Z
dc.date.available2021-03-21T18:10:53Z
dc.date.issued2021-03-15
dc.description.abstractThe pace in which businesses evolve, compel them to respond to changes, opportunities and market demand. For software products, it is even more challenging given the evolution of technology and the law of obsolescence. For this reason, agile requirements engineering (RE) provides the industry with several techniques to help coping with those challenges, and agile prototyping is one of them. Several studies focus on showing how these practices and techniques support agile prototyping and validation of requirements for large-scale projects. However, at least to our knowledge, small projects are disregarded, and not enough research is done to show how agile RE techniques support prototyping. The goal of this thesis was to investigate how agile RE techniques can support prototyping in small software projects. We used action research on the case of a digital service that promotes sustainable eating experience at lunch restaurants. We conducted brainstorming sessions, interviews, prioritization sessions and prototype reviews. The results are based on open feedback, observation and data coding. Our results show that prototyping can be supported in agile requirements elicitation by techniques such as project documentation analysis, observation, customer journey map, interviews and brainstorming. We also found out that use cases and user stories can support prototyping in requirements analysis and representation. The same goes with requirements prioritization, and by extension extreme prioritization, which helps in planning and lightening the agile prototyping process. Finally, our results show that, when conducted with different project stakeholders, review meetings with a prototype are a good means to get rich feedback for further iterations.en
dc.format.extent69 + 11
dc.identifier.urihttps://aaltodoc.aalto.fi/handle/123456789/103132
dc.identifier.urnURN:NBN:fi:aalto-202103212411
dc.language.isoenen
dc.programmeMaster’s Programme in Computer, Communication and Information Sciencesfi
dc.programme.majorSoftware and Service Engineeringfi
dc.programme.mcodeSCI3043fi
dc.subject.keywordagile REen
dc.subject.keywordRE techniquesen
dc.subject.keywordaction researchen
dc.subject.keywordagile prototypingen
dc.titleAgile Requirements Engineering with Prototyping in Small Software Projects: An Action Research Caseen
dc.typeG2 Pro gradu, diplomityöfi
dc.type.ontasotMaster's thesisen
dc.type.ontasotDiplomityöfi
local.aalto.electroniconlyyes
local.aalto.openaccessno
Files