| fullrecord |
[{"key": "dc.contributor.advisor", "value": "Sepp\u00e4nen, Ville", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.advisor", "value": "Palola, Timo", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Merisalo, Mikko", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2020-12-09T11:05:04Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2020-12-09T11:05:04Z", "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/73061", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Ohjelmistokehityksess\u00e4, kuten yleisesti liiketoiminnassa, on hy\u00f6dyllist\u00e4 k\u00e4ytt\u00e4\u00e4\nmittareita toiminnan tukena. Ohjelmistokehityksess\u00e4 k\u00e4ytet\u00e4\u00e4n nykyisin varsin\nusein niin sanottuja ketteri\u00e4 ohjelmistokehitysmenetelmi\u00e4, joista yksi suosituimmista\non Scrum. Ketterien menetelmien tueksi on listattu useita erilaisia ja\npaljon k\u00e4ytettyj\u00e4 mittareita. Suosituimmat mittarit eiv\u00e4t v\u00e4ltt\u00e4m\u00e4tt\u00e4 sovellu\nsuoraan kaikkiin tilanteisiin, vaan k\u00e4ytt\u00f6\u00f6n otettavat mittarit olisi hyv\u00e4 valita\nkohdealueen ja tarpeiden mukaan.\nT\u00e4m\u00e4n tutkimuksen tarkoituksena oli selvitt\u00e4\u00e4 tutkimuksen kohteena olevan\nScrum-tiimin n\u00e4k\u00f6kulmasta tiimin ohjelmistokehityksen tueksi k\u00e4ytt\u00f6\u00f6notettavia\nmittareita. Mittareiden selvitt\u00e4misen pohjustukseksi toinen tutkimuksen\ntarkoitus oli kuvata kohdetiimin ohjelmistokehitysprosessia, jossa Scrumviitekehyksen\nohella hy\u00f6dynnettiin esimerkiksi DevOps-k\u00e4yt\u00e4nteit\u00e4. Tutkimusmenetelm\u00e4n\u00e4\nk\u00e4ytettiin iteratiivista design science -otetta, miss\u00e4 tuloksia\nt\u00e4ydennettiin vaiheittain tiimin kanssa keskustellen. Tutkimuksen tuloksena\nsyntyi vuokaavioita tiimin ohjelmistokehitysprosessista ja mittarilistauksia.\nTiimin ohjelmistokehitysprosesseissa kuvattiin tiimin kehitysjonon teht\u00e4vien\netenemisen prosessi ja miten sen osana n\u00e4kyy esimerkiksi koodien katselmointi\npull request \u2013pohjaisesti ja koodin automaattinen julkaiseminen. Automaatio\non yksi DevOpsin ulottuvuuksista ja hyv\u00e4 kohde mittareille esimerkiksi\nautomaattisen ja ajantasaisen datan ansiosta. Kehitysjonoteht\u00e4vien prosesseista\nkuvattiin featuren, user storyn, taskin ja bugin vaiheet sek\u00e4 keskustelussa t\u00e4rke\u00e4ksi\nnostettu release-suunnittelu yleisesti. Mittareita ker\u00e4ttiin useaa eri tiimin\ntoimintaa koskettavan osa-alueen kirjallisuusviitteist\u00e4 226 mittarin listaukseen,\njosta iteratiivisesti rajattiin lopullinen 13 mittarin joukko, miss\u00e4 yhdeks\u00e4n mittaria\noli kirjallisuuden pohjalta ker\u00e4tyst\u00e4 listasta ja nelj\u00e4 keskustelun pohjalta listaan\nlis\u00e4tty\u00e4 mittaria.\nOhjelmistokehitysprosessien kuvaaminen ei vain pohjustanut mittarikeskustelua,\nmutta my\u00f6s mahdollisti tiimille keskustelun oman ohjelmistokehitysprosessinsa\ntilasta ja sen tulevaisuudesta, sek\u00e4 loi havainnollistavan kuvauksen\nkehitysprosessista tiimille. Iteratiivinen ja kirjallisuuteen pohjaava mittareiden\nkartoittaminen auttoi tiimi\u00e4 rajaamaan usealta eri osa-alueelta joukon eniten\ntiimi\u00e4 itse\u00e4\u00e4n kiinnostavia mittareita, joka ei vain ole listaus suosituimmista\nmuualla k\u00e4yt\u00f6ss\u00e4 olevista mittareista.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "In software business, as in any business, metrics can be a useful tool to support\nmanagerial business decisions. Nowadays many of the methods used to build\nsoftware products are part of agile development method family, out of which\none of the most popular is Scrum. Several studies present metrics to support\nagile software development methods. However, these are often the most popular\nand most used metrics, which might not suit for every situation. Thus, metrics\nshould be selected based on the target domain and observed needs.\nThe purpose of this study is to determine metrics from the target Scrum\nteam\u2019s perspective to support the team in their software development process.\nIn order to help mapping the metrics, another purpose for this study is to model\nthe team\u2019s software development process, which along with Scrum includes\nfor example DevOps practices. Design science type method used builds the results\niteratively based on discussions done with the team. The results of this\nstudy are software development process models and metrics lists.\nThe process models describe the handling of the team\u2019s backlog items and\nhow are, for example, pull request based code review and continuous delivery\nincluded in the process. Automation is one of the main features of DevOps.\nBased on its automatic and timely data creation, it is a very suitable target for\nvarious metrics. Backlog item process models include models for feature, user\nstory, task and bug iterations and a general process for release planning, which\nwas brought up in the team discussions as an important process area. An original\nlist of 226 metrics from articles categorized as coming from various sectors\nwithin the team\u2019s area of operation narrowed down to a list of 13 metrics during\nthe discussion. Nine of the final metrics are from the original article list and\nfour new were suggested in the team discussions.\nSoftware process models, in addition to giving basis to the metrics discussion,\nalso facilitated a discussion on how the team want to develop and run\ntheir software development now and in the future. It also forms a visualization\nfor the team of their development process. Defining metrics iteratively from a\nlist of metrics used in various agile software development sectors enabled the\nteam to form a list of metrics that are suitable to the specific situation and to the\nneeds of the team themselves. Not just a list of the most used metrics in the industry.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Paivi Vuorio (paelvuor@jyu.fi) on 2020-12-09T11:05:04Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2020-12-09T11:05:04Z (GMT). No. of bitstreams: 0\n Previous issue date: 2020", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "72", "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": "ohjelmistomittarit", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "Scrum", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "DevOps", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "Kartoitus mittareista osaksi Scrum-tiimin ohjelmistokehityst\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-202012097002", "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.collaborator", "value": "public", "language": "", "element": "contractresearch", "qualifier": "collaborator", "schema": "yvv"}, {"key": "yvv.contractresearch.funding", "value": "0", "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.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": "ohjelmistokehitys", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "mittarit (mittaus)", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "kehitt\u00e4minen", "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.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"}]
|