Difference between revisions of "Milestone 6 Mustang"

From crowdresearch
Jump to: navigation, search
(Created page with " == Title == Methodologies to improve current crowdsourcing systems by adding functionality for better collaboration and fair compensation. Authors: Achal Varma, Vignesh Vi...")
 
Line 33: Line 33:
  
 
[1] Feature Idea - The Kickstarter Model/Surge Pricing “http://crowdresearch.stanford.edu/w/index.php?title=Milestone_3_Mustang_DarkHorse:_The_Kickstarter_Model”
 
[1] Feature Idea - The Kickstarter Model/Surge Pricing “http://crowdresearch.stanford.edu/w/index.php?title=Milestone_3_Mustang_DarkHorse:_The_Kickstarter_Model”
 +
 
[2] Foundation Idea - Dynamic Pricing Model for co-ordinated sales and operations “http://papers.ssrn.com/sol3/papers.cfm?abstract_id=861419##”
 
[2] Foundation Idea - Dynamic Pricing Model for co-ordinated sales and operations “http://papers.ssrn.com/sol3/papers.cfm?abstract_id=861419##”
[3] Feature Idea - Github style issues system
+
 
“http://crowdresearch.stanford.edu/w/index.php?title=Milestone_3_Mustang_PowerIdea_1:_HIT_Support_Page”
+
[3] Feature Idea - Github style issues system “http://crowdresearch.stanford.edu/w/index.php?title=Milestone_3_Mustang_PowerIdea_1:_HIT_Support_Page”
[4] Foundation Idea - Social Networking meets Software Development
+
 
http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6401114
+
[4] Foundation Idea - Social Networking meets Software Development "http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6401114"
[5] Feature Idea - Got issues? Who cares about it? A large scale investigation of issue trackers from GitHub
+
 
http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6698918&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D6698918
+
[5] Feature Idea - Got issues? Who cares about it? A large scale investigation of issue trackers from GitHub "http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6698918&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D6698918"
[6] An analysis of requirements evolution in open source projects: recommendations for issue trackers
+
 
http://dl.acm.org/citation.cfm?id=2501550
+
[6] An analysis of requirements evolution in open source projects: recommendations for issue trackers "http://dl.acm.org/citation.cfm?id=2501550"

Revision as of 21:57, 8 April 2015

Title

Methodologies to improve current crowdsourcing systems by adding functionality for better collaboration and fair compensation.

Authors: Achal Varma, Vignesh Vishwanathan

Abstract

This paper looks into improving the current crowdsourcing systems by utilizing some of the features that were suggested during Milestone 2. The major criteria for our selection is the amount of impact the feature creates when added to the new crowdsourcing model that we are collectively in the process of creating. While there were a lot of ideas, we are primarily looking at fleshing out some of the ideas that we came up with and are envisioning how users (workers and requestors) will interact with the features. Two ideas that we think has a lot of promise are the Kickstarter model of pricing the work and a Github style “Issue” tracker. While these ideas while not novel, they are something that we feel would positively impact the crowdsourcing model. We aim to accurately predict the use cases of our users, however that is something that we will learn during the implementation stages. And ideally learning more about our users to fine tune the current ideas that we are pursuing.

Motivation

All current crowdsourcing systems all follow the same rough model - requesters post tasks and depending on past experience, workers are allowed to take on said tasks for monetary compensation. Most problems that arise in this system are due to lack of trust between both parties and an imbalance of power. We feel that better communication and a fair compensation model will allow the parties to overcome these shortcomings.

Related Work

Insight

This section should lay out this the foundational idea(s). These big ideas are the things that you'll be known for, and what other platforms would want to replicate. Explain: Why/how are they novel and better than anything that has been attempted in the past?

System

The insight above should explain the high level idea (e.g., "All workers are paid in chocolate"). Here, you explain how it works in specifics. (e.g., "We built a crowdsourcing platform called Chococrowd that mails dark chocolate candies to workers at the conclusion of each month. Requesters choose the quality of the dark chocolate based on the quality of the work.")

Evaluation

Once the platform you propose has been implemented, how will you determine whether your system actually solves the problem you wanted to solve? What are the results you hope you can realistically achieve? Why do these results show that you have solved the problem?

References

[1] Feature Idea - The Kickstarter Model/Surge Pricing “http://crowdresearch.stanford.edu/w/index.php?title=Milestone_3_Mustang_DarkHorse:_The_Kickstarter_Model”

[2] Foundation Idea - Dynamic Pricing Model for co-ordinated sales and operations “http://papers.ssrn.com/sol3/papers.cfm?abstract_id=861419##”

[3] Feature Idea - Github style issues system “http://crowdresearch.stanford.edu/w/index.php?title=Milestone_3_Mustang_PowerIdea_1:_HIT_Support_Page”

[4] Foundation Idea - Social Networking meets Software Development "http://ieeexplore.ieee.org/xpl/articleDetails.jsp?arnumber=6401114"

[5] Feature Idea - Got issues? Who cares about it? A large scale investigation of issue trackers from GitHub "http://ieeexplore.ieee.org/xpl/login.jsp?tp=&arnumber=6698918&url=http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D6698918"

[6] An analysis of requirements evolution in open source projects: recommendations for issue trackers "http://dl.acm.org/citation.cfm?id=2501550"