Time tracking in software maintenance service

Ohjelmistojen ylläpitovaihe vie suuren osan ohjelmiston koko elinkaaren ajasta ja rahoituksesta. Ylläpidossa kehittäjät työstävät yhtä aikaa monta rinnakkaista tehtävää. Käyttämänsä ajan he raportoivat tuntiraportille, jota käytetään asiakkaan laskutukseen ja tulevan työn työmääräarviointiin - molem...

Full description

Bibliographic Details
Main Author: Kaihlavirta, Johanna
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: 2022
Subjects:
Online Access: https://jyx.jyu.fi/handle/123456789/84170
_version_ 1826225752648974336
author Kaihlavirta, Johanna
author2 Informaatioteknologian tiedekunta Faculty of Information Technology Informaatioteknologia Information Technology Jyväskylän yliopisto University of Jyväskylä
author_facet Kaihlavirta, Johanna Informaatioteknologian tiedekunta Faculty of Information Technology Informaatioteknologia Information Technology Jyväskylän yliopisto University of Jyväskylä Kaihlavirta, Johanna Informaatioteknologian tiedekunta Faculty of Information Technology Informaatioteknologia Information Technology Jyväskylän yliopisto University of Jyväskylä
author_sort Kaihlavirta, Johanna
datasource_str_mv jyx
description Ohjelmistojen ylläpitovaihe vie suuren osan ohjelmiston koko elinkaaren ajasta ja rahoituksesta. Ylläpidossa kehittäjät työstävät yhtä aikaa monta rinnakkaista tehtävää. Käyttämänsä ajan he raportoivat tuntiraportille, jota käytetään asiakkaan laskutukseen ja tulevan työn työmääräarviointiin - molemmat hyvin tärkeitä asioita tehdä oikein. Tuntiraporttien tarkkuus voi kuitenkin vaihdella. Kirjallisuudessa tunnistetaan vaihtelulle useita syitä, mutta syiden ratkaisemista ei ole tutkittu. Tuntiraportointijärjestelmän luomiseen ja tuntiraporteilta saatavan tiedon käyttämiseen on kirjallisuudessa ehdotuksia, mutta itse tuntiraportointijärjestelmän käyttöä tarkan tiedon saamiseksi ei ole tarkasteltu. Tämä tutkimus ehdottaa ohjeistusta työtehtävien luokitteluun tuntiraportointia varten ohjelmistoylläpitotyössä. Tutkimus toteutettiin suunnittelutiedemenetelmällä konsultointiyrityksen ohjelmistoylläpitotiimissä. Tavoitteena oli helpottaa tuntiraportointiprosessia. Tiimi osallistui tehtäviensä kirjaamiseen. Kirjatut tehtävät muokattiin ohjeeksi päätöspuun muotoon. Ohje on tämän tutkimuksen ohessa tuotettu artefakti. Ohje auttoi tehtävien luokittelussa kuudenkymmenen esimerkin kautta, ja sen käyttöä arvioitiin tiimiläisten haastattelujen avulla. Tutkimuksen lopputulokseksi saatiin vahvistettua artefaktin hyödyllisyys tehtävien luokittelun opettelussa. Lisäksi tutkimus vahvistaa kirjallisuudesta poimitut havainnot tuntikirjauksen hankaluuksista: koettu ahdistus sisäisen työn oikeutuksesta tai etukäteen arvioidun aikaraamin ylittämisestä asiakastyössä, sekä päivän aikana tehtyjen työtehtävien ja niiden keston muisteleminen jälkikäteen. Aftifakti ei pystynyt ohjeistamaan työntekijöitä näiden huolten osalta. Päälöydös on, että tuntiraportointi koettiin työn ärsyttävimmäksi osaksi. Tämä havainto paljastaa käytännön ongelmia, jotka vaativat selvitäkseen jatkotutkimuksia. Software maintenance takes a major part of the development life cycle for a system in both time and money. Developers in maintenance teams are working with multiple tasks parallel and interleaved. They report effort in timesheets which are then used for customer invoicing and estimating future work - both which are important to get right. However, the accuracy of time reports may vary. Literature identifies several reasons for inaccurate reports but it is not researched how these reasons are solved in practice. Literature suggests a way for setting up a time tracking system and use cases for gathered data, but doesn't examine the actual use of a time tracking system, nor how companies can instruct developers to report their time accurately. This study proposes instructions aiding in task categorisation for time reporting in software maintenance context. Design science research method was applied in a consultancy company and its software maintenance team to make the time tracking process easier. The team took part in defining activities and mapping them to current categorisation. The defined activities were used to construct an artifact of instructions in the form of a decision tree. The tree provided sixty examples for task categorisation and it was evaluated in practical use by interviewing team members. This study concludes that the artifact was helpful for learning task categorisation rules initially. The study also confirmed claims from literature regarding obstacles in the time tracking process, namely, perceived stress in justifying time spent on internal work or when exceeding an estimated time frame for customer work items, and recalling daily activities and time spent on each activity afterwards. However, the artifact designed in this study could not answer these concerns. The main finding is that time tracking was perceived as the most annoying part of the job. This observation reveals practical problems which need attention in further research.
first_indexed 2022-12-01T21:00:47Z
format Pro gradu
free_online_boolean 1
fullrecord [{"key": "dc.contributor.advisor", "value": "Lakanen, Antti-Jussi", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.advisor", "value": "Sepp\u00e4nen, Ville", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Kaihlavirta, Johanna", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2022-12-01T06:28:34Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2022-12-01T06:28:34Z", "language": null, "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2022", "language": "", "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/84170", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Ohjelmistojen yll\u00e4pitovaihe vie suuren osan ohjelmiston koko elinkaaren ajasta ja rahoituksesta. Yll\u00e4pidossa kehitt\u00e4j\u00e4t ty\u00f6st\u00e4v\u00e4t yht\u00e4 aikaa monta rinnakkaista teht\u00e4v\u00e4\u00e4. K\u00e4ytt\u00e4m\u00e4ns\u00e4 ajan he raportoivat tuntiraportille, jota k\u00e4ytet\u00e4\u00e4n asiakkaan laskutukseen ja tulevan ty\u00f6n ty\u00f6m\u00e4\u00e4r\u00e4arviointiin - molemmat hyvin t\u00e4rkeit\u00e4 asioita tehd\u00e4 oikein. Tuntiraporttien tarkkuus voi kuitenkin vaihdella. Kirjallisuudessa tunnistetaan vaihtelulle useita syit\u00e4, mutta syiden ratkaisemista ei ole tutkittu. Tuntiraportointij\u00e4rjestelm\u00e4n luomiseen ja tuntiraporteilta saatavan tiedon k\u00e4ytt\u00e4miseen on kirjallisuudessa ehdotuksia, mutta itse tuntiraportointij\u00e4rjestelm\u00e4n k\u00e4ytt\u00f6\u00e4 tarkan tiedon saamiseksi ei ole tarkasteltu.\n \nT\u00e4m\u00e4 tutkimus ehdottaa ohjeistusta ty\u00f6teht\u00e4vien luokitteluun tuntiraportointia varten ohjelmistoyll\u00e4pitoty\u00f6ss\u00e4. Tutkimus toteutettiin suunnittelutiedemenetelm\u00e4ll\u00e4 konsultointiyrityksen ohjelmistoyll\u00e4pitotiimiss\u00e4. Tavoitteena oli helpottaa tuntiraportointiprosessia. Tiimi osallistui teht\u00e4viens\u00e4 kirjaamiseen. Kirjatut teht\u00e4v\u00e4t muokattiin ohjeeksi p\u00e4\u00e4t\u00f6spuun muotoon. Ohje on t\u00e4m\u00e4n tutkimuksen ohessa tuotettu artefakti. Ohje auttoi teht\u00e4vien luokittelussa kuudenkymmenen esimerkin kautta, ja sen k\u00e4ytt\u00f6\u00e4 arvioitiin tiimil\u00e4isten haastattelujen avulla.\n \nTutkimuksen lopputulokseksi saatiin vahvistettua artefaktin hy\u00f6dyllisyys teht\u00e4vien luokittelun opettelussa. Lis\u00e4ksi tutkimus vahvistaa kirjallisuudesta poimitut havainnot tuntikirjauksen hankaluuksista: koettu ahdistus sis\u00e4isen ty\u00f6n oikeutuksesta tai etuk\u00e4teen arvioidun aikaraamin ylitt\u00e4misest\u00e4 asiakasty\u00f6ss\u00e4, sek\u00e4 p\u00e4iv\u00e4n aikana tehtyjen ty\u00f6teht\u00e4vien ja niiden keston muisteleminen j\u00e4lkik\u00e4teen. Aftifakti ei pystynyt ohjeistamaan ty\u00f6ntekij\u00f6it\u00e4 n\u00e4iden huolten osalta. P\u00e4\u00e4l\u00f6yd\u00f6s on, ett\u00e4 tuntiraportointi koettiin ty\u00f6n \u00e4rsytt\u00e4vimm\u00e4ksi osaksi. T\u00e4m\u00e4 havainto paljastaa k\u00e4yt\u00e4nn\u00f6n ongelmia, jotka vaativat selvit\u00e4kseen jatkotutkimuksia.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Software maintenance takes a major part of the development life cycle for a system in both time and money. Developers in maintenance teams are working with multiple tasks parallel and interleaved. They report effort in timesheets which are then used for customer invoicing and estimating future work - both which are important to get right. However, the accuracy of time reports may vary. Literature identifies several reasons for inaccurate reports but it is not researched how these reasons are solved in practice. Literature suggests a way for setting up a time tracking system and use cases for gathered data, but doesn't examine the actual use of a time tracking system, nor how companies can instruct developers to report their time accurately.\n \n This study proposes instructions aiding in task categorisation for time reporting in software maintenance context. Design science research method was applied in a consultancy company and its software maintenance team to make the time tracking process easier. The team took part in defining activities and mapping them to current categorisation. The defined activities were used to construct an artifact of instructions in the form of a decision tree. The tree provided sixty examples for task categorisation and it was evaluated in practical use by interviewing team members.\n \nThis study concludes that the artifact was helpful for learning task categorisation rules initially. The study also confirmed claims from literature regarding obstacles in the time tracking process, namely, perceived stress in justifying time spent on internal work or when exceeding an estimated time frame for customer work items, and recalling daily activities and time spent on each activity afterwards. However, the artifact designed in this study could not answer these concerns. The main finding is that time tracking was perceived as the most annoying part of the job. This observation reveals practical problems which need attention in further research.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Paivi Vuorio (paelvuor@jyu.fi) on 2022-12-01T06:28:34Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2022-12-01T06:28:34Z (GMT). No. of bitstreams: 0\n Previous issue date: 2022", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "62", "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": "eng", "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": "time tracking", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "time reporting", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "software maintenance", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "timesheet", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "billables", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "tuntikirjaus", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "tuntiraportointi", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "ohjelmistoyll\u00e4pito", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "Time tracking in software maintenance service", "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-202212015437", "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": "Tietotekniikka", "language": "fi", "element": "subject", "qualifier": "discipline", "schema": "dc"}, {"key": "dc.subject.discipline", "value": "Mathematical Information Technology", "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": "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": "602", "language": "", "element": "subject", "qualifier": "oppiainekoodi", "schema": "dc"}, {"key": "dc.subject.yso", "value": "ajank\u00e4ytt\u00f6", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "seuranta", "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": "time use", "language": null, "element": "subject", "qualifier": "yso", "schema": "dc"}, {"key": "dc.subject.yso", "value": "tracking", "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.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"}]
id jyx.123456789_84170
language eng
last_indexed 2025-02-18T10:54:16Z
main_date 2022-01-01T00:00:00Z
main_date_str 2022
online_boolean 1
online_urls_str_mv {"url":"https:\/\/jyx.jyu.fi\/bitstreams\/5bcd66ff-2b89-43b6-8117-398748930426\/download","text":"URN:NBN:fi:jyu-202212015437.pdf","source":"jyx","mediaType":"application\/pdf"}
publishDate 2022
record_format qdc
source_str_mv jyx
spellingShingle Kaihlavirta, Johanna Time tracking in software maintenance service time tracking time reporting software maintenance timesheet billables tuntikirjaus tuntiraportointi ohjelmistoylläpito Tietotekniikka Mathematical Information Technology 602 ajankäyttö seuranta ohjelmistokehitys time use tracking software development
title Time tracking in software maintenance service
title_full Time tracking in software maintenance service
title_fullStr Time tracking in software maintenance service Time tracking in software maintenance service
title_full_unstemmed Time tracking in software maintenance service Time tracking in software maintenance service
title_short Time tracking in software maintenance service
title_sort time tracking in software maintenance service
title_txtP Time tracking in software maintenance service
topic time tracking time reporting software maintenance timesheet billables tuntikirjaus tuntiraportointi ohjelmistoylläpito Tietotekniikka Mathematical Information Technology 602 ajankäyttö seuranta ohjelmistokehitys time use tracking software development
topic_facet 602 Mathematical Information Technology Tietotekniikka ajankäyttö billables ohjelmistokehitys ohjelmistoylläpito seuranta software development software maintenance time reporting time tracking time use timesheet tracking tuntikirjaus tuntiraportointi
url https://jyx.jyu.fi/handle/123456789/84170 http://www.urn.fi/URN:NBN:fi:jyu-202212015437
work_keys_str_mv AT kaihlavirtajohanna timetrackinginsoftwaremaintenanceservice