| fullrecord |
[{"key": "dc.contributor.advisor", "value": "Marttiin, Pentti", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.advisor", "value": "Suoraniemi, Kimmo", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Karplund, Elias", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2023-05-17T10:34:22Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2023-05-17T10:34:22Z", "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/87018", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "T\u00e4m\u00e4 pro gradu -tutkielma k\u00e4sittelee skaalautuvia ketteri\u00e4 kehitysmenetelmi\u00e4 ja niiden haasteita asiakasarvoon perustuvan kehityksen tukemiseksi. Ketter\u00e4 ohjelmistokehitys ja sen periaatteet manifestinsa my\u00f6t\u00e4 ovat muuttaneet ohjelmistoalaa merkitt\u00e4v\u00e4sti ja ovat t\u00e4n\u00e4 p\u00e4iv\u00e4n\u00e4 valtavirtaa. Sen edut ovat saaneet my\u00f6s suuret ja vakiintuneet yritykset kiinnostumaan sen soveltamisesta niiden toimintaan, mik\u00e4 on luonut tarpeen skaalautuville menetelmille, jotka pyrkiv\u00e4t muovaamaan pienempiin konteksteihin tarkoitetuista alkuper\u00e4isist\u00e4 ketterist\u00e4 menetelmist\u00e4 suuriin organisaatioihin soveltuvia. \nSkaalautuvat metodit kuten SAFe eiv\u00e4t kuitenkaan ole pulmattomia ja niiden onnistunut k\u00e4ytt\u00f6 edellytt\u00e4\u00e4 organisaatioilta suuria ponnisteluita haasteiden v\u00e4ltt\u00e4miseksi ja lievent\u00e4miseksi. N\u00e4m\u00e4 haasteet voivat liitty\u00e4 muun muassa metodien k\u00e4ytt\u00f6\u00f6n, konflikteihin eri metodien v\u00e4lill\u00e4, kulttuurillisiin tai toimialakohtaisiin erityispiirteisiin sek\u00e4 monimutkaisuuteen. Ketteryyden konstein yritykset pyrkiv\u00e4t yh\u00e4 enemmiss\u00e4 m\u00e4\u00e4rin perustamaan kehitystoimenpiteit\u00e4\u00e4n asiakasarvoon sek\u00e4 tuomaan sen vaikutuksia k\u00e4yt\u00e4nt\u00f6\u00f6n. Asiakasarvoa on jo pitk\u00e4\u00e4n tarkasteltu markkinoinnin tutkimuksessa, mutta sill\u00e4 ei ole yhten\u00e4ist\u00e4 m\u00e4\u00e4ritelm\u00e4\u00e4 eik\u00e4 vakiintuneita metodeja sen m\u00e4\u00e4r\u00e4lliseen mittaamiseen asiakaskokemusmittareita, kuten NPS:\u00e4\u00e4 lukuun ottamatta. Metodeja sen objektiiviseen huomiointiin ketter\u00e4ss\u00e4 kehityksess\u00e4 ei my\u00f6sk\u00e4\u00e4n k\u00e4yt\u00e4nn\u00f6ss\u00e4 ole. \nTutkimus toteutettiin teemahaastatteluina vakiintuneelle Suomessa toimivalle teleoperaattorialan yritykselle, joka on jo useamman vuoden ajan hy\u00f6dynt\u00e4nyt SAFe 5-viitekehykseen pohjautuvaa mallia kehitystoiminnassaan. Aineiston analyysissa k\u00e4ytettiin teema-analyysia, jossa tunnistettiin teemoja tutkimuskontribuutioille ja parannusehdotuksille. Skaalautuvien kehitysmenetelmien tutkimuksessa todettujen haasteiden todettiin olevan laajalti l\u00e4sn\u00e4 my\u00f6s kohdeyrityksess\u00e4, vaikkakin sen mallin vakiintumisen n\u00e4htiin muovanneen t\u00e4m\u00e4nhetkisi\u00e4 haasteita kasvukivuista toimialakohtaisempiin piirteisiin. Asiakasarvon mittaaminen kohdeorganisaatiossa vastasi sen v\u00e4hyytt\u00e4 tutkimuksessa ja se ei ollut suoraan k\u00e4yt\u00f6ss\u00e4 objektiivisena mittarina priorisoinnissa. Konkreettisiksi keinoiksi asiakasarvon roolin kasvattamiseksi yrityksen kehitystoimissa l\u00f6ydettiin muun muassa asiakasn\u00e4k\u00f6kulmien s\u00e4\u00e4nn\u00f6llisempi esilletuonti alkuvaiheen analyysiin, arvovirtakohtaisempi rakenne ja asiakasarvoa heijastavan mittarin k\u00e4ytt\u00f6\u00f6notto kehityskohteiden priorisointimekanismiin.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "This thesis deals with scaled agile software development methods and their challenges to support customer value-based development decisions. Principles of agile software development from its manifesto have disrupted the software industry and are now mainstream. Its benefits have also attracted large and incumbent organisations to apply it to their operations, creating a need for scalable methodologies that seek to transform the original agile methodologies from their smaller contexts into those suitable for large organisations.\nHowever, scaled agile methods such as SAFe come with their own challenges and their successful use requires significant efforts from organisations to avoid and mitigate them. These challenges can be related to the methods them-selves, conflicts between different methods, cultural or domain-specific issues, and complexity. Through the concepts of agility companies are increasingly seeking to base their development efforts on customer value and to bring its impact into practice. Customer value has long attracted widespread interest particularly in marketing research but there is no unanimous definition of it nor standard methods for quantifying it, apart from customer experience measures such as NPS. Despite customers being on the forefront of agility, there practically are no established methods to incorporate it objectively to agile development.\nThe study was conducted with thematic interviews from its commissioning organisation which is an established telecom provider in Finland. It has been using a SAFe 5 framework-based development model for several years. Thematic analysis was used in the analysis of the data, from which themes for contributions and suggestions were recognised. The challenges identified in the research of scaled agile methods were found to apply in the target company, although the maturity of the model had shaped the current challenges from growing pains to more domain-specific direction. In terms of customer value, its measurement in the company was consistent with the few metrics in literature and it was not used as an objective metric in prioritisation. Concrete ways to increase the role of customer value in the company's development model were found to include more regular introduction of customer perspectives to first phases of analysis, a more value stream-oriented structure, and the implementation of a customer value component to the prioritisation mechanism.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Paivi Vuorio (paelvuor@jyu.fi) on 2023-05-17T10:34:22Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2023-05-17T10:34:22Z (GMT). No. of bitstreams: 0\n Previous issue date: 2023", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "111", "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": "agile software development", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "scaling agile", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "customer value", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "measuring", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "Scaling agile to deliver customer value : mapping challenges and role of customer value in the development model of a telco company", "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-202305173082", "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.collaborator", "value": "business", "language": "", "element": "contractresearch", "qualifier": "collaborator", "schema": "yvv"}, {"key": "yvv.contractresearch.funding", "value": "2800", "language": "", "element": "contractresearch", "qualifier": "funding", "schema": "yvv"}, {"key": "yvv.contractresearch.initiative", "value": "student", "language": "", "element": "contractresearch", "qualifier": "initiative", "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": "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": "priorisointi", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "ketter\u00e4t menetelm\u00e4t", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "asiakkaat", "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": "asiakaskokemus", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "prioritisation", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "agile methods", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "customers", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "software development", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "customer experience", "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"}]
|