| fullrecord |
[{"key": "dc.contributor.advisor", "value": "Sepp\u00e4nen, Ville", "language": "", "element": "contributor", "qualifier": "advisor", "schema": "dc"}, {"key": "dc.contributor.author", "value": "Lehoj\u00e4rvi, Jaana", "language": "", "element": "contributor", "qualifier": "author", "schema": "dc"}, {"key": "dc.date.accessioned", "value": "2018-06-01T09:22:23Z", "language": null, "element": "date", "qualifier": "accessioned", "schema": "dc"}, {"key": "dc.date.available", "value": "2018-06-01T09:22:23Z", "language": null, "element": "date", "qualifier": "available", "schema": "dc"}, {"key": "dc.date.issued", "value": "2018", "language": "", "element": "date", "qualifier": "issued", "schema": "dc"}, {"key": "dc.identifier.uri", "value": "https://jyx.jyu.fi/handle/123456789/58273", "language": null, "element": "identifier", "qualifier": "uri", "schema": "dc"}, {"key": "dc.description.abstract", "value": "Teknisen velan (Technical Debt, TD) k\u00e4sitteiden ja konseptin k\u00e4ytt\u00f6 on lis\u00e4\u00e4ntynyt paljon viimeisin\u00e4 vuosina, mik\u00e4 kuvastaa my\u00f6s yritysmaailman her\u00e4nnytt\u00e4 kiinnostusta aiheeseen. Teknisen velan negatiivisten vaikutusten ulottuessa ohjelmistotuotantoyrityksist\u00e4 ohjelmistojen k\u00e4ytt\u00e4jiin ja koko ymp\u00e4r\u00f6iv\u00e4\u00e4n maailmaan, velan hallinnoinnin merkitys kasvaa. Ohjelmistojen jatkokehityksen hankaloituminen tai estyminen tarkoittaa ylim\u00e4\u00e4r\u00e4isi\u00e4 kuluja. Samalla kun k\u00e4yt\u00e4nn\u00f6n tekij\u00f6iden kiinnostus on her\u00e4nnyt, on my\u00f6s syntynyt tarve erilaisille malleille, viitekehyksille ja esimerkkiratkaisuille, ty\u00f6v\u00e4lineille, joiden avulla k\u00e4yt\u00e4nn\u00f6ss\u00e4 teknisen velan hallinnointia voitaisiin tehd\u00e4. Teknisen velan hallin-nointia (Technical Debt Management, TDM) on parhaan kompromissin l\u00f6yt\u00e4minen kullekin projektille tai tuotteelle. T\u00e4m\u00e4 tutkimus perustui oletetukseen, ettei kirjallisuudessa ole viel\u00e4 tiimitasolle soveltuvaa, kokonaisvaltaista teknisen velan hallinnoinnin viitekehyst\u00e4. Tutkimuksen tavoitteena olikin rakentaa kir-jallisuuskatsauksien ja empiiriseen osion perusteella alustavat teknisen velan hallinnoinnin yleinen ja tasoittainen (tiimi) viitekehys. Viitekehykset toimivat siten apuv\u00e4linein\u00e4 rakennettaessa k\u00e4yt\u00e4nn\u00f6n teknisen velan hallinnoinnin malleja tai prosesseja tiimitasolle. Tutkimusstrategiana k\u00e4ytettiin suunnittelutieteellist\u00e4 tutkimusta ja l\u00e4hestymistapana suunnittelutieteellist\u00e4 prosessia (DSRM), jossa tutkittavia artefakteja rakennetaan iteratiivisesti. T\u00e4m\u00e4n tutkimuksen artefakteja ovat yleinen ja tasoittainen (tiimi) viitekehys. Rakennetut viitekehykset sek\u00e4 esimerkkimalliratkaisu arvioitiin asiantuntijoille suunnatulla kyselytutkimuksella. Viitekehykset ja esimerkkimalliratkaisu arvioitiin varsin toimiviksi ja k\u00e4ytt\u00f6kelpoisiksi asiantuntijoiden kyselytutkimuksessa. Kyselytutkimuksen tuloksista esiin nousseet t\u00e4rkeimm\u00e4t havainnot muutettiin viitekehysten kehitystoimenpiteiksi, jotka seuraavalla iterointikierroksella toteutettiin. Kyselytutkimuksesta selvisi my\u00f6s teknisen velan hallinnoinnin olevan viel\u00e4 varsin puutteellista, eik\u00e4 termin tuntemuskaan tiimeiss\u00e4 ole kattavaa.", "language": "fi", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.abstract", "value": "The use of the concept of technical debt (TD) has increased remarkably in a few years, reflecting the growing and widespread interest of the business community towards the issue. Managing technical debt becomes more and more important, as its negative impacts hit globally, starting from software companies and ending up to single software users. The costs of software production raise as a result of complicated, or even blocked further development of software. Simultaneously with the awakened interest of the practitioners, there emerges a need for various models, frameworks and solution models \u2013 tools \u2013 that would enable proper management of technical debt in practice. Technical Debt Management (TDM) is about finding best available compromises for each project or product in question. This research was based on the assumption that in the literature there does not yet exist any comprehensive technical debt management framework applicable to team level. The aim of the study was to construct two frameworks, general and hierarchical (team) to manage technical debt, based on a literature review and an empirical study. The frameworks will thus serve as tools for further construction of practical technical debt management models and processes at team level. Design science research was used as research strategy, the approach being design science process (DSRM), according to which the artifacts are constructed iteratively. The artifacts produced by this research are the general and the hierarchical (team) frameworks. The constructed frame-works and the sample model solution were evaluated by an expert questionnaire, resulting as being functional and useful. Main findings emerging from the results of the questionnaire were further developed into development proposals and were accordingly implemented in the next iteration cycle of the process. The questionnaire also revealed that the existence of the management of technical debt is still quite deficient, and the knowledge of the definition itself is not yet sufficient in software development teams.", "language": "en", "element": "description", "qualifier": "abstract", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Submitted by Paivi Vuorio (paelvuor@jyu.fi) on 2018-06-01T09:22:23Z\nNo. of bitstreams: 0", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.description.provenance", "value": "Made available in DSpace on 2018-06-01T09:22:23Z (GMT). No. of bitstreams: 0\n Previous issue date: 2018", "language": "en", "element": "description", "qualifier": "provenance", "schema": "dc"}, {"key": "dc.format.extent", "value": "165", "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": "tekninen velka", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "teknisen velan hallinnointi", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "teknisen velan hallinnoinnin viitekehys", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.subject.other", "value": "suunnittelutieteellinen tutkimus", "language": "", "element": "subject", "qualifier": "other", "schema": "dc"}, {"key": "dc.title", "value": "Teknisen velan hallinnoinnin viitekehykset: tiimin n\u00e4k\u00f6kulma", "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-201806012977", "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.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"}]
|