Table 6: Suggestions to requesting clients and crowdsourcing platforms.
Suggestions
Turbulence • State the rationale of crowdsourcing and ensure that it is aligned with its business strategies and objectives [29]. • Provide instructions and guidance for newly companies.
Decomposition • Decompose the complex task into several simple mini tasks [15].
• Divide and describe tasks due to high granularity [21].
• Provide guidance on task decomposition.
Communication • Foster an open and supportive communication channel [9].
• Foster efficient crowdsourcing mechanisms [24].
• Appoint employees familiar with the project as copilots to coordinate registrants and answer questions [33].
• Focus on continuous communication, timely reply, and coordination [33].
• Implement computer-assisted translation or auto-translation mechanisms [13,15].
• Improve the construction of task forums.
Schedule • Pay attention to the progress of crowdsourcing tasks, timely modify and repost the failed tasks. • Employ empirically machine learning techniques to identify risk tasks automatically.
Intellectual Property • Explicitly assign all intellectual property to clients and reject to accept submissions containing proprietary information belonging to a third party [9,30].
• Reinforce the examination of submissions and try to find out plagiarism code [30].
• Using crowdsourcing among the existing employees or through a hybrid crowd comprising of employees and the general public [19].
• Explicitly assign all intellectual property to the requesting company [9].
• Calling crowd workers to support originality, not copying others' results [11].
• Ban those plagiarized workers from registering tasks several days or punish them with points.
Requirement • Provide clear, complete and consistent requirements [13].
• Provide enough links, documents and diagrams to keep context completely.
• Remind requesters to upload links & diagrams.
Estimation • Determine the duration and award based on similar tasks. • Provide auto-estimation support.
Quality • Use mechanisms such as automated quality control or entry evaluation of participants [9].
• Attracting more and higher skillful developers to participate [25].
• Formulate coding guidelines and directions [10].
• Show code best practice.
• Provide task-worker recommendation mechanism.
Starvation • Provide enough incentive to attract workers [10].
• Send emails to registrants to remind and encourage them to finish tasks.
• Encourage newcomers and guide them to complete the first task.
• Impose penalties on spammers.
Worker Continuity • Send emails to the previous submitters to attract them to register new tasks in the same project. • Provide more incentives to continuous workers, e.g., faster upgrades.
Worker Engagement • Use a SC decision support /recommendation system to better identify appropriate resources and increase task submission rates. • Provide more effective services to monitor ongoing data.
• Provide more actionable analytic for managing different types of workers.
Worker Trustworthiness • Restrict access by login type and strengthen the construction of firewalls and monitoring mechanisms [9,11].
• Anonymizing the data so that it becomes more neutral when released to the crowd [9].
• Restrict access by login type and strengthen the construction of firewalls and monitoring mechanisms [9,11].
• Anonymizing the data so that it becomes more neutral when released to the crowd [9].