| fullrecord |
[{"key": "dc.contributor.advisor", "value": "Abrahamsson, Pekka", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Kivikangas, Laura", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Mulari, Markus", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2021-10-26T07:11:00Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2021-10-26T07:11:00Z", "language": null, "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2021", "language": "", "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/78323", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "T\u00e4ss\u00e4 pro gradu -tutkielmassa selvitet\u00e4\u00e4n kirjallisuuskatsauksen avulla, millaisia menestystekij\u00f6it\u00e4 ja haasteita skaalautuvien ketterien menetelmien k\u00e4ytt\u00f6\u00f6notossa ja k\u00e4yt\u00f6ss\u00e4 esiintyy. Yleisimmin esiintyvist\u00e4 menestystekij\u00f6ist\u00e4 ja haasteista tehd\u00e4\u00e4n kipupistemalli, jossa menestystekij\u00e4t ja haasteet kuvataan kipupistein\u00e4. Kipupistemalli sis\u00e4lt\u00e4\u00e4 my\u00f6s ratkaisuehdotukset kipupisteiden selvitt\u00e4miseksi. Kipupistemallissa on kahdeksan kipupistett\u00e4, jotka ovat muutosvastarinta, konseptien ja ketteryyden m\u00e4\u00e4rittely, tiimin koordinointi ja autonomia, johtaminen: tuen puute, uusien ja vanhojen toimintatapojen kohtaaminen, laadunvarmistus, ketter\u00e4 osaaminen ja valmennus: osaamisen ja valmennuksen puute ja viestint\u00e4: huono viestint\u00e4.\nTutkielmassa toteutetaan tapaustutkimus, jonka avulla tutkimuksen kohteena olevan j\u00e4rjestelm\u00e4kehityshankkeen kehitysmenetelm\u00e4\u00e4 tutkitaan ja arvioidaan kipupistemallin pohjalta. Toteutimme hankkeessa seitsem\u00e4n teema-haastattelua, joiden pohjalta kuvasimme ja vertasimme hankkeessa k\u00e4yt\u00f6ss\u00e4 olevaa kehitysmenetelm\u00e4\u00e4 skaalautuviin ketteriin menetelmiin SAFe:en, LeSS:iin, DA:han ja Essenceen. Rooleista teimme vastaavan vertailukuvion. L\u00f6ysimme hankkeen menetelm\u00e4ss\u00e4 ja rooleissa vastaavuuksia kaikkiin vertailtuihin menetelmiin. Hankkeen menetelm\u00e4ss\u00e4 oli my\u00f6s kolme elementti\u00e4: PO-aika, refaktorointiviikko ja arkkitehtuurikokous ja yksi rooli: hankep\u00e4\u00e4llikk\u00f6, joita emme t\u00e4ysin vastaavana l\u00f6yt\u00e4neet vertailtavista menetelmist\u00e4.\nTarkastellessa haastatteluiden tuloksia kipupistemalliin saimme selville, ett\u00e4 hankkeessa esiintyy kipupistemallin mukaisia kipupisteit\u00e4, joita on tunnistettu ja ainakin osittain ratkaistu ja kipupisteit\u00e4, joita ei ole ratkaistu. Hankkeessa esiintyv\u00e4t kipupisteet, joita on tunnistettu ja ainakin osittain ratkaistu ovat tiimin koordinointi ja autonomia, ketter\u00e4 osaaminen ja valmennus: osaamisen ja valmennuksen puute, viestint\u00e4: huono viestint\u00e4 ja konseptien ja ketteryyden m\u00e4\u00e4rittely. Esiintyv\u00e4t kipupisteet, joita ei ole ratkaistu ovat konseptien ja ketteryyden m\u00e4\u00e4rittely, uusien ja vanhojen toimintatapojen kohtaaminen ja laadunvarmistus. Kipupistemallissa esiintyvi\u00e4 muutosvastarintaa ja johtaminen: tuen puutteeseen viittaavia kipupisteit\u00e4 ei havaittu.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "In this Master\u2019s Thesis we conduct a literature review on the factors affecting success and failure for the use and adoption of scaled agile frameworks. The most common success and failure factors are used to construct a pain point model in which success and failure factors are described as pain points. The pain point model also suggests solutions for overcoming pain points. The eight pain points in our model are change resistance, defining concepts and agility, team\u2019s coordination and autonomy, management: lack of support from management, clash of old and the new ways of working, quality management, agile skills and training: lack of skills and training and communication: bad communication.\nWe also conduct a case study in which a software project development method is evaluated and compared to our pain point model. We interviewed seven people working on the same development project. From these theme interviews we described and compared the methods used in the project to scaled agile methods SAFe, LeSS, DA, and Essence. We did an equivalent comparison to the roles used in the project. We discovered corresponding methods and roles to all examined methods. The project\u2019s development method also had three elements: PO time slot, refactoring week, architecture meeting, and role: project chief. These three elements and one role were not found as such from the compared methods. \nComparing the results from the interviews to the pain point model we discovered that the project holds identified and partly resolved pain points and pain points that are unresolved. Identified and partly resolved pain points in the project are team\u2019s coordination and autonomy, agile skills and training: lack of skills and training, communication: bad communication, and defining concepts and agility. Unresolved pain points are defining concepts and agility, clash of old and the new ways of working and quality management. Change resistance and management: lack of support from management pain points were not met.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Paivi Vuorio (paelvuor@jyu.fi) on 2021-10-26T07:11:00Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2021-10-26T07:11:00Z (GMT). No. of bitstreams: 0\n Previous issue date: 2021", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "109", "language": "", "element": "format", "qualifier": "extent", "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": "skaalautuva ketteryys", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "Skaalautuvat ketter\u00e4t menetelm\u00e4t : tapaustutkimus kipupisteist\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-202110265353", "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.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": "ketter\u00e4t menetelm\u00e4t", "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": "haasteet (ongelmat)", "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.rights.url", "value": "https://rightsstatements.org/page/InC/1.0/", "language": null, "element": "rights", "qualifier": "url", "schema": "dc"}]
|