The Dos and Don’ts of Crowdsourcing Software Development

B. Fitzgerald and K. Stol (2015) The Dos and Don’ts of Crowdsourcing Software Development, Proceedings SOFSEM 2015, LNCS 8939, pp. 58-64

In 1957, the eminent computer scientist, Edsger W. Dijkstra, sought to record his profession as “Computer Programmer” on his marriage certificate. The Dutch authorities, although probably more progressive than most, refused on the grounds that there was no such profession. Ironically, just a decade later, the term “software crisis” had been coined, as delegates at a NATO Conference in Garmisch [1] reported a common set of problems, namely that software took too long to develop, cost too much to develop, and the software which was eventually delivered did not meet user expectations. Despite the advances in technology over the past 50 years, this remains problematic, as evidenced by the following quote from the US President’s Council of Advisors on Science & Technology (PCAST) in 2012.

“The problem of predictable development of software with the intended functionality that is reliable, secure and efficient remains one of the most important problems in [ICT]”

A number of initiatives have emerged over the years to address the software crisis. Outsourcing of the software development activity has been on the increase in recent years according to US and European reports. However, in many cases outsourcing of software development has not been successful [2,3]. The success of the open source movement which has proven surprisingly successful at developing high quality software in a cost effective manner [4] has been an inspiration for a number of specific forms of software outsourcing, including opensourcing [5], innersourcing [6] and crowdsourcing [7].

References

  1. Naur,P., Randell, B. (eds.):ReportonaconferencesponsoredbytheNATOSCIENCECOM- MITTEE (1968)
  2. Nakatsu, R., Iacovou, C.: A comparative study of important risk factors involved in offshore and domestic outsourcing of software development projects: A two-panel delphi study. Infor- mation & Management 46, 57–68 (2009)
  3. Tiwana, A., Keil, M.: Control in internal and outsourced software projects. Journal of Man- agement Information Systems 26, 9–44 (2009)
  4. Feller, J., Fitzgerald, B., Hissam, S., Lakhani, K.: Perspectives on Free and Open Source Software. MIT Press (2005)
  5. Agerfalk, P.J., Fitzgerald, B.: Outsourcing to an unknown workforce: Exploring opensourc- ing as a global sourcing strategy. MIS Quarterly 32 (2008)
  6. Stol, K., Avgeriou, P., Babar, M., Lucas, Y., Fitzgerald, B.: Key factors for adopting inner source. ACM Trans. Softw. Eng. Methodol., 23 (2014)
  7. Stol, K., Fitzgerald, B.: Two’s company, three’s a crowd: A case study of crowdsourcing software development. In: Proc. 36th Int’l Conf. Software Engineering, pp. 187–198 (2014)

 

UA-57933830-1