The success of requirement elicitation in IT-projects

IT-projektit ovat monitahoisia ja kompleksisia kokonaisuuksia, joiden hallitseminen sekä läpivieminen annetussa ajassa sekä budjetissa on haastavaa. Hyvin usein projektin aikana kohdatut ongelmat kulminoituvat projektin suunnitteluvaiheeseen ja vaatimusten määrittelyyn, jotka näin ollen ovat kriitti...

Full description

Bibliographic Details
Main Author: Soini, Helka
Other Authors: Informaatioteknologian tiedekunta, Faculty of Information Technology, Informaatioteknologia, Information Technology, Jyväskylän yliopisto, University of Jyväskylä
Format: Master's thesis
Language:eng
Published: 2023
Subjects:
Online Access: https://jyx.jyu.fi/handle/123456789/86888
_version_ 1826225725695328256
author Soini, Helka
author2 Informaatioteknologian tiedekunta Faculty of Information Technology Informaatioteknologia Information Technology Jyväskylän yliopisto University of Jyväskylä
author_facet Soini, Helka Informaatioteknologian tiedekunta Faculty of Information Technology Informaatioteknologia Information Technology Jyväskylän yliopisto University of Jyväskylä Soini, Helka Informaatioteknologian tiedekunta Faculty of Information Technology Informaatioteknologia Information Technology Jyväskylän yliopisto University of Jyväskylä
author_sort Soini, Helka
datasource_str_mv jyx
description IT-projektit ovat monitahoisia ja kompleksisia kokonaisuuksia, joiden hallitseminen sekä läpivieminen annetussa ajassa sekä budjetissa on haastavaa. Hyvin usein projektin aikana kohdatut ongelmat kulminoituvat projektin suunnitteluvaiheeseen ja vaatimusten määrittelyyn, jotka näin ollen ovat kriittisiä vaiheita projektin onnistumisen kannalta. Vaatimusten kerääminen on iteratiivinen prosessi, jonka aikana projektitiimi pyrkii keräämään projektin ja lopputuleman tärkeimmät ominaisuudet sidosryhmien avustuksella. Vaatimusten keräämisessä on tunnistettu useita eri haasteita, jotka saattavat aiheuttaa ongelmia projektin muissa vaiheissa. Tämän pro gradu-tutkielman tarkoituksena on selvittää, minkälaisia toimintatapoja käyttämällä kerätyt vaatimukset toteuttavat tärkeimpiä vaatimusten keruun onnistumistekijöitä ja johtavat onnistuneeseen projektin lopputulokseen. Aiheen tutkiminen on ensisijaista, sillä aiempi tutkimustieto on keskimäärin vanhentunutta ja lisäksi keskittyy suurimmaksi osaksi haasteiden tunnistamiseen kuin niiden ratkaisemiseen. Kvalitatiivinen tutkimus toteutettiin haastattelemalla Yrityksen X projekteissa mukana olleita henkilöitä, jotka osallistuivat vaatimuksen määrittelyyn ja keräämiseen. Haastatteluissa selvisi, että yleisimmät vaatimusten keräämisen haasteet ovat jatkuvasti muuttuvat vaatimukset, kommunikaatio, sekä tärkeimpien sidosryhmien osallistaminen. Iteratiivinen työskentely, optimoitu sidosryhmien osallistaminen, taustatutkimus, sopivan keräystekniikan valitseminen, riskien tunnistaminen sekä selkeän kommunikaatiotavan luonti todettiin edesauttavan vaatimusten keruun onnistumista. Vaikka vaatimusten keruu oli haastateltavien mielestä erittäin tärkeää, sen koettiin olevan selkeästi puutteellinen ja kiireellä tehty kaikissa kohdeprojektissa. Tutkimustulokset ovat merkityksellisiä, mutta hyvä huomata, että esimerkiksi iteratiivisuus, kommunikointi ja riskien hallinta ovat jo ennalta tunnistettuja elementtejä projektin suunnitteluvaiheessa, eikä näin ollen ole täysin uusia löydöksiä projektin hallinnassa. IT-projects are all-around and complex entities, which are challenging to manage and complete within the given time and budget, and very often the challenges culminate in the planning phase of the project and the requirement analysis. The purpose of this Master's thesis is to find out, what kind of good practices should be implemented to the requirement elicitation process to achieve the most important success factors of the requirement elicitation and lead to a successful project outcome. The qualitative research was carried out by interviewing the people involved in IT-projects of Company X, who participated the requirement analysis and elicitation processes. Empirical research revealed the problems usually occurring during the requirement elicitation are constantly changing requirements, communication issues, and involving correct stakeholders into elicitation in an efficient way. Iterative way of working, effective involvement of the stakeholders, feasibility study, choosing a suitable elicitation technique, identifying risks, and creating a clear communication strategy were found as good practices to implement in the requirement elicitation. Although the interviewees regarded the requirement elicitation being very crucial activity, the process was experienced incomplete and executed in a rush in every target project. Therefore, the importance of requirement elicitation should be emphasized among all stakeholders in the beginning of the project requirement analysis. The research results are significant and extensive, but the topic requires more investigation to be able to give more specific results in the future.
first_indexed 2023-05-11T20:02:07Z
format Pro gradu
fullrecord [{"key": "dc.contributor.advisor", "value": "Clements, Kati", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Soini, Helka", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2023-05-11T05:40:59Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2023-05-11T05:40:59Z", "language": null, "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2023", "language": "", "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/86888", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "IT-projektit ovat monitahoisia ja kompleksisia kokonaisuuksia, joiden hallitseminen sek\u00e4 l\u00e4pivieminen annetussa ajassa sek\u00e4 budjetissa on haastavaa. Hyvin usein projektin aikana kohdatut ongelmat kulminoituvat projektin suunnitteluvaiheeseen ja vaatimusten m\u00e4\u00e4rittelyyn, jotka n\u00e4in ollen ovat kriittisi\u00e4 vaiheita projektin onnistumisen kannalta. Vaatimusten ker\u00e4\u00e4minen on iteratiivinen prosessi, jonka aikana projektitiimi pyrkii ker\u00e4\u00e4m\u00e4\u00e4n projektin ja lopputuleman t\u00e4rkeimm\u00e4t ominaisuudet sidosryhmien avustuksella. Vaatimusten ker\u00e4\u00e4misess\u00e4 on tunnistettu useita eri haasteita, jotka saattavat aiheuttaa ongelmia projektin muissa vaiheissa. T\u00e4m\u00e4n pro gradu-tutkielman tarkoituksena on selvitt\u00e4\u00e4, mink\u00e4laisia toimintatapoja k\u00e4ytt\u00e4m\u00e4ll\u00e4 ker\u00e4tyt vaatimukset toteuttavat t\u00e4rkeimpi\u00e4 vaatimusten keruun onnistumistekij\u00f6it\u00e4 ja johtavat onnistuneeseen projektin lopputulokseen. Aiheen tutkiminen on ensisijaista, sill\u00e4 aiempi tutkimustieto on keskim\u00e4\u00e4rin vanhentunutta ja lis\u00e4ksi keskittyy suurimmaksi osaksi haasteiden tunnistamiseen kuin niiden ratkaisemiseen. Kvalitatiivinen tutkimus toteutettiin haastattelemalla Yrityksen X projekteissa mukana olleita henkil\u00f6it\u00e4, jotka osallistuivat vaatimuksen m\u00e4\u00e4rittelyyn ja ker\u00e4\u00e4miseen. Haastatteluissa selvisi, ett\u00e4 yleisimm\u00e4t vaatimusten ker\u00e4\u00e4misen haasteet ovat jatkuvasti muuttuvat vaatimukset, kommunikaatio, sek\u00e4 t\u00e4rkeimpien sidosryhmien osallistaminen. Iteratiivinen ty\u00f6skentely, optimoitu sidosryhmien osallistaminen, taustatutkimus, sopivan ker\u00e4ystekniikan valitseminen, riskien tunnistaminen sek\u00e4 selke\u00e4n kommunikaatiotavan luonti todettiin edesauttavan vaatimusten keruun onnistumista. Vaikka vaatimusten keruu oli haastateltavien mielest\u00e4 eritt\u00e4in t\u00e4rke\u00e4\u00e4, sen koettiin olevan selke\u00e4sti puutteellinen ja kiireell\u00e4 tehty kaikissa kohdeprojektissa. Tutkimustulokset ovat merkityksellisi\u00e4, mutta hyv\u00e4 huomata, ett\u00e4 esimerkiksi iteratiivisuus, kommunikointi ja riskien hallinta ovat jo ennalta tunnistettuja elementtej\u00e4 projektin suunnitteluvaiheessa, eik\u00e4 n\u00e4in ollen ole t\u00e4ysin uusia l\u00f6yd\u00f6ksi\u00e4 projektin hallinnassa.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "IT-projects are all-around and complex entities, which are challenging to manage and complete within the given time and budget, and very often the challenges culminate in the planning phase of the project and the requirement analysis. The purpose of this Master's thesis is to find out, what kind of good practices should be implemented to the requirement elicitation process to achieve the most important success factors of the requirement elicitation and lead to a successful project outcome. The qualitative research was carried out by interviewing the people involved in IT-projects of Company X, who participated the requirement analysis and elicitation processes. Empirical research revealed the problems usually occurring during the requirement elicitation are constantly changing requirements, communication issues, and involving correct stakeholders into elicitation in an efficient way. Iterative way of working, effective involvement of the stakeholders, feasibility study, choosing a suitable elicitation technique, identifying risks, and creating a clear communication strategy were found as good practices to implement in the requirement elicitation. Although the interviewees regarded the requirement elicitation being very crucial activity, the process was experienced incomplete and executed in a rush in every target project. Therefore, the importance of requirement elicitation should be emphasized among all stakeholders in the beginning of the project requirement analysis. The research results are significant and extensive, but the topic requires more investigation to be able to give more specific results in the future.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Paivi Vuorio (paelvuor@jyu.fi) on 2023-05-11T05:40:59Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2023-05-11T05:40:59Z (GMT). No. of bitstreams: 0\n Previous issue date: 2023", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "82", "language": "", "element": "format", "qualifier": "extent", "schema": "dc"}, {"key": "dc.language.iso", "value": "eng", "language": null, "element": "language", "qualifier": "iso", "schema": "dc"}, {"key": "dc.rights", "value": "In Copyright", "language": null, "element": "rights", "qualifier": null, "schema": "dc"}, {"key": "dc.subject.other", "value": "IT-project", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "requirement analysis", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "requirement elicitation", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "The success of requirement elicitation in IT-projects", "language": "", "element": "title", "qualifier": null, "schema": "dc"}, {"key": "dc.type", "value": "master thesis", "language": null, "element": "type", "qualifier": null, "schema": "dc"}, {"key": "dc.identifier.urn", "value": "URN:NBN:fi:jyu-202305112967", "language": "", "element": "identifier", "qualifier": "urn", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Master\u2019s thesis", "language": "en", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Pro gradu -tutkielma", "language": "fi", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.contributor.faculty", "value": "Informaatioteknologian tiedekunta", "language": "fi", "element": "contributor", "qualifier": "faculty", "schema": "dc"}, {"key": "dc.contributor.faculty", "value": "Faculty of Information Technology", "language": "en", "element": "contributor", "qualifier": "faculty", "schema": "dc"}, {"key": "dc.contributor.department", "value": "Informaatioteknologia", "language": "fi", "element": "contributor", "qualifier": "department", "schema": "dc"}, {"key": "dc.contributor.department", "value": "Information Technology", "language": "en", "element": "contributor", "qualifier": "department", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "Jyv\u00e4skyl\u00e4n yliopisto", "language": "fi", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.contributor.organization", "value": "University of Jyv\u00e4skyl\u00e4", "language": "en", "element": "contributor", "qualifier": "organization", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Tietoj\u00e4rjestelm\u00e4tiede", "language": "fi", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Information Systems Science", "language": "en", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "yvv.contractresearch.funding", "value": "0", "language": "", "element": "contractresearch", "qualifier": "funding", "schema": "yvv"}, {"key": "dc.type.coar", "value": "http://purl.org/coar/resource_type/c_bdcc", "language": null, "element": "type", "qualifier": "coar", "schema": "dc"}, {"key": "dc.rights.copyright", "value": "\u00a9 The Author(s)", "language": null, "element": "rights", "qualifier": "copyright", "schema": "dc"}, {"key": "dc.rights.accesslevel", "value": "restrictedAccess", "language": null, "element": "rights", "qualifier": "accesslevel", "schema": "dc"}, {"key": "dc.type.publication", "value": "masterThesis", "language": null, "element": "type", "qualifier": "publication", "schema": "dc"}, {"key": "dc.subject.oppiainekoodi", "value": "601", "language": "", "element": "subject", "qualifier": "oppiainekoodi", "schema": "dc"}, {"key": "dc.subject.yso", "value": "vaatimusm\u00e4\u00e4rittelyt", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "projektit", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "menestystekij\u00e4t", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "requirement specifications", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "projects", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "success factors", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.rights.url", "value": "https://rightsstatements.org/page/InC/1.0/", "language": null, "element": "rights", "qualifier": "url", "schema": "dc"}, {"key": "dc.rights.accessrights", "value": "The author has not given permission to make the work publicly available electronically. Therefore the material can be read only at the archival workstation at Jyv\u00e4skyl\u00e4 University Library (https://kirjasto.jyu.fi/collections/archival-workstation).", "language": "en", "element": "rights", "qualifier": "accessrights", "schema": "dc"}, {"key": "dc.rights.accessrights", "value": "Tekij\u00e4 ei ole antanut lupaa avoimeen julkaisuun, joten aineisto on luettavissa vain Jyv\u00e4skyl\u00e4n yliopiston kirjaston arkistoty\u00f6semalta. Ks. https://kirjasto.jyu.fi/kokoelmat/arkistotyoasema..", "language": "fi", "element": "rights", "qualifier": "accessrights", "schema": "dc"}]
id jyx.123456789_86888
language eng
last_indexed 2025-02-18T10:54:43Z
main_date 2023-01-01T00:00:00Z
main_date_str 2023
publishDate 2023
record_format qdc
source_str_mv jyx
spellingShingle Soini, Helka The success of requirement elicitation in IT-projects IT-project requirement analysis requirement elicitation Tietojärjestelmätiede Information Systems Science 601 vaatimusmäärittelyt projektit menestystekijät requirement specifications projects success factors
title The success of requirement elicitation in IT-projects
title_full The success of requirement elicitation in IT-projects
title_fullStr The success of requirement elicitation in IT-projects The success of requirement elicitation in IT-projects
title_full_unstemmed The success of requirement elicitation in IT-projects The success of requirement elicitation in IT-projects
title_short The success of requirement elicitation in IT-projects
title_sort success of requirement elicitation in it projects
title_txtP The success of requirement elicitation in IT-projects
topic IT-project requirement analysis requirement elicitation Tietojärjestelmätiede Information Systems Science 601 vaatimusmäärittelyt projektit menestystekijät requirement specifications projects success factors
topic_facet 601 IT-project Information Systems Science Tietojärjestelmätiede menestystekijät projects projektit requirement analysis requirement elicitation requirement specifications success factors vaatimusmäärittelyt
url https://jyx.jyu.fi/handle/123456789/86888 http://www.urn.fi/URN:NBN:fi:jyu-202305112967
work_keys_str_mv AT soinihelka successofrequirementelicitationinitprojects AT soinihelka thesuccessofrequirementelicitationinitprojects