Please use this identifier to cite or link to this item: https://ruomo.lib.uom.gr/handle/7000/655
Full metadata record
DC FieldValueLanguage
dc.contributor.authorBibi, Stamatia-
dc.contributor.authorZozas, Ioannis-
dc.contributor.authorAmpatzoglou, Apostolos-
dc.contributor.authorSarigiannidis, Panagiotis-
dc.contributor.authorKalampokis, George-
dc.contributor.authorStamelos, Ioannis-
dc.date.accessioned2020-03-29T06:48:39Z-
dc.date.available2020-03-29T06:48:39Z-
dc.date.issued2020-
dc.identifier10.1109/ACCESS.2020.2982619en_US
dc.identifier.issn2169-3536en_US
dc.identifier.urihttps://doi.org/10.1109/ACCESS.2020.2982619en_US
dc.identifier.urihttps://ruomo.lib.uom.gr/handle/7000/655-
dc.description.abstractDespite the extensive adoption of crowdsourcing for the timely, cost-effective, and highquality completion of software development tasks, a large number of crowdsourced challenges are not able to acquire a winning solution, on time, and within the desired cost and quality thresholds. A possible reason for this is that we currently lack a systematic approach that would aid software managers during the process of designing software development tasks that will be crowdsourced. This paper attempts to extend the current knowledge on designing crowdsourced software development tasks, by empirically answering the following management questions: (a) what type of projects should be crowdsourced; (b) why should one crowdsource—in terms of acquired benefits; (c) where should one crowdsource—in terms of application domain; (d) when to crowdsource—referring to the time period of the year; (e) who will win or participate in the contest; and (f) how to crowdsource (define contest duration, prize, type of contest etc.) to acquire the maximum benefits—depending on the goal of crowdsourcing. To answer the aforementioned questions, we have performed a case study on 2,209 software development tasks crowdsourced through TopCoder platform. The results suggest that there are significant differences in the level to which crowdsourcing goals are reached, across different software development activities. Based on this observation we suggest that software managers should prioritize the goals of crowdsourcing, decide carefully upon the activity to be crowdsourced and then define the settings of the task.en_US
dc.language.isoenen_US
dc.sourceIEEE Accessen_US
dc.subjectFRASCATI::Natural sciences::Computer and information sciencesen_US
dc.subject.othercrowdsourcingen_US
dc.subject.othersoftware developmenten_US
dc.subject.othersuccess factorsen_US
dc.subject.othercrowd factorsen_US
dc.subject.othercosten_US
dc.subject.otherdurationen_US
dc.titleCrowdsourcing in Software Development: Empirical Support for Configuring Contestsen_US
dc.typeArticleen_US
dc.contributor.departmentΤμήμα Εφαρμοσμένης Πληροφορικήςen_US
local.identifier.firstpage1en_US
local.identifier.lastpage25en_US
Appears in Collections:Department of Applied Informatics

Files in This Item:
File Description SizeFormat 
IEEEAcess_Bibi_etal.pdf2,97 MBAdobe PDFView/Open


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.