| fullrecord |
[{"key": "dc.contributor.advisor", "value": "Sepp\u00e4nen, Ville", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Aalto, Ilari", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Kumpukoski, Johannes", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2020-06-18T07:49:01Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2020-06-18T07:49:01Z", "language": null, "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2020", "language": "", "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/70060", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Tutkimuksessa selvitettiin, mit\u00e4 ohjelmistojen tuotekehityksen hukalla ja sen hallinnalla tarkoitetaan ja miten organisaatiot tunnistavat ja hallitsevat hukkaa. Tutkimuksen l\u00e4ht\u00f6kohtana ja tarkoituksena oli selvitt\u00e4\u00e4, mink\u00e4laista hukkaa eri ohjelmistojen tuotekehityksen tasoilla syntyy ja miten sit\u00e4 pyrit\u00e4\u00e4n minimoimaan ja hallitsemaan erilaisilla menetelmill\u00e4. Tutkimuksen kohteena oli eri ohjelmistojen tuotekehityksen tasot ja niiden erilaiset hukan tunnistamistavat ja menetelm\u00e4t hukan hallintaan. Tutkimuskysymys oli: Miten voidaan tunnistaa ja minimoida hukkaa eri ohjelmistojen tuotekehityksen tasoilla? Aineiston keruu suoritettiin puolistrukturoiduilla teemahaastatteluilla. Aineisto analysoitiin teemoittelun avulla. Tutkimusaineisto koostui kolmesta eri ohjelmistojen tuotekehityst\u00e4 tekev\u00e4st\u00e4 yrityksest\u00e4. N\u00e4ist\u00e4 yrityksist\u00e4 haastateltiin henkil\u00f6it\u00e4 kolmelta eri ohjelmistojen tuotekehityksen tasolta: 1) Portfoliotaso, 2) tuotetaso ja 3) tuotekehitystaso. Haastatteluiden tulokset osoittavat, ett\u00e4 ohjelmistojen tuotekehityksess\u00e4 syntyy hukkaa kaikilla tasoilla, joita tutkimuksessa tutkittiin ja yritykset pyrkiv\u00e4t aktiivisesti minimoimaan hukan riski\u00e4 ja hallitsemaan hukkaa erilaisilla menetelmill\u00e4. Toisissa yrityksiss\u00e4 hukan tunnistaminen ja hallitseminen oli suuremmassa roolissa kuin toisessa. Hukka ymm\u00e4rrettiin lis\u00e4arvoa tuottamattomina prosesseina tai teht\u00e4vin\u00e4 ohjelmistojen tuotekehityksen aikana ja niiden poistaminen n\u00e4htiin ohjelmistojen tuotekehityst\u00e4 tehostavana seikkana kaikilla eri ohjelmistojen tuotekehityksen tasolla. Tutkimustulokset osoittavat, ett\u00e4 hukan tunnistamista, sen riskin v\u00e4ltt\u00e4mist\u00e4 ja toteutuneen hukan hallintaa tehd\u00e4\u00e4n p\u00e4\u00e4s\u00e4\u00e4nt\u00f6isesti erilaisten ohjelmistojen tuotekehityksen menetelmien ja prosessien kautta. Yrityksill\u00e4 ei ollut omia menetelmi\u00e4 hukan tunnistamiseksi. Tutkimuksen perusteella voidaan p\u00e4\u00e4tell\u00e4, ett\u00e4 ohjelmistojen tuotekehityksen hukka on yrityksille ep\u00e4mieluinen asia ja sit\u00e4 aktiivisesti pyrit\u00e4\u00e4n hallitsemaan. Yrityksill\u00e4 ei ole konkreettisia keinoja tai menetelmi\u00e4 hukan tunnistamiseen, riskin minimoimiseen tai hallintaan. Johtop\u00e4\u00e4t\u00f6ksen\u00e4 esitet\u00e4\u00e4n, ett\u00e4 ohjelmistojen tuotekehityksen hukan aktiivinen tunnistaminen, sen riskin minimointi ja toteutuneen hukan hallinta tehostavat ohjelmistojen tuotekehityst\u00e4 ja tekev\u00e4t eri ohjelmistojen tuotekehityksen prosesseista enemm\u00e4n arvoa tuottavia ohjelmistolle.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "The study explored what is waste in software development and how organizations identify and manage waste in software development. The purpose of the research was to find out what kind of wastes are there in software development and how the risk of the waste is minimized and managed in the different levels of software development. The subject of the study was the different levels of software development and the different methods of identifying, minimizing the risk and managing the waste. The research question was: How can an organization identify, minimize the risk and manage waste in software development. The research material for the study was collected by using qualitative research method through semi-structured theme interviews, which were analyzed by theming the results of the interview\u2019s answers. The research material consisted three different organizations interviews of the: 1) portfolio level, 2) product level and 3) software development level. The results of the study show, that the waste occur in every level that were studied, and companies try to actively to identify, minimize the risk and manage the waste with different methods. In other companies the identifying and managing the waste was in bigger role than in others. Waste was seen as a process or task that did not produce any value during the software development process and removing waste was seen to improve the effiency on all levels of the software development process. The research results also show that the identifying, minimizing the risk and management of waste is mainly done through different software development methods. The organizations did not have their own methods on waste management in software development. The organizations in the study did not have concrete measures or methods to identify waste, minimize the risk or manage it. Based on the study, it can be concluded that waste in software development is undesirable and the organizations try to manage it actively. The conclusion is that when waste is actively identified, the risk of it is minimized and realized waste is managed, the software development is more efficient and the process of software development produces more value to the software.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Miia Hakanen (mihakane@jyu.fi) on 2020-06-18T07:49:01Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2020-06-18T07:49:01Z (GMT). No. of bitstreams: 0\n Previous issue date: 2020", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "93", "language": "", "element": "format", "qualifier": "extent", "schema": "dc"}, {"key": "dc.format.mimetype", "value": "application/pdf", "language": null, "element": "format", "qualifier": "mimetype", "schema": "dc"}, {"key": "dc.language.iso", "value": "fin", "language": null, "element": "language", "qualifier": "iso", "schema": "dc"}, {"key": "dc.rights", "value": "In Copyright", "language": "en", "element": "rights", "qualifier": null, "schema": "dc"}, {"key": "dc.subject.other", "value": "Ohjelmistojen tuotekehitys", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "hukka", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "ohjelmistoyritykset", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "Hukka ohjelmistojen tuotekehityksess\u00e4", "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-202006184271", "language": "", "element": "identifier", "qualifier": "urn", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Pro gradu -tutkielma", "language": "fi", "element": "type", "qualifier": "ontasot", "schema": "dc"}, {"key": "dc.type.ontasot", "value": "Master\u2019s thesis", "language": "en", "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.accesslevel", "value": "openAccess", "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": "tietotekniikkayritykset", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "ohjelmistokehitys", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "tuotekehitys", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "liiketoiminta", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "ohjelmistot", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "tuotteet", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.format.content", "value": "fulltext", "language": null, "element": "format", "qualifier": "content", "schema": "dc"}, {"key": "dc.rights.url", "value": "https://rightsstatements.org/page/InC/1.0/", "language": null, "element": "rights", "qualifier": "url", "schema": "dc"}, {"key": "dc.type.okm", "value": "G2", "language": null, "element": "type", "qualifier": "okm", "schema": "dc"}]
|