@article {2017, title = {Work~features to support stigmergic coordination in distributed teams}, year = {2017}, type = {Interactive paper}, abstract = {
When work products are shared via a computer system, members of distributed teams can see the work products produced by remote colleagues as easily as those from local colleagues. Drawing on coordination theory and work in computer-supported cooperative work (CSCW), we theorize that these work products can provide information to support team coordination, that is, that work can be coordinated through the outcome of the work itself, a mode of coordination analogous to the biological process of stigmergy. Based on studies of documents and work, we postulate three features of work products that enable them to support team coordination, namely having a clear genre, being visible and mobile, and being combinable. These claims are illustrated with examples drawn from free/libre open source software development teams. We conclude by discussing how the proposed theory might be empirically tested.
}, keywords = {Coordination, Stigmergy}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Stigmergy\%20theory\%20paper\%20to\%20share.pdf}, author = {Kevin Crowston and James Howison and Bolici, Francesco and Carsten {\O}sterlund} } @article {2016, title = {Manifesto on Engineering Academic Software (Dagstuhl Perspectives Workshop 16252)}, volume = {6}, year = {2016}, month = {12/2106}, institution = {Schloss Dagstuhl {\textendash} Leibniz Center for Informatics}, address = {Wadern, Germany}, abstract = {Software is often a critical component of scientific research. It can be a component of the academic research methods used to produce research results, or it may itself be an academic research result. Software, however, has rarely been considered to be a citable artifact in its own right. With the advent of open-source software, artifact evaluation committees of conferences, and journals that include source code and running systems as part of the published artifacts, we foresee that software will increasingly be recognized as part of the academic process. The quality and sustainability of this software must be accounted for, both a priori and a posteriori. The Dagstuhl Perspectives Workshop on {\textquotedblleft}Engineering Academic Software{\textquotedblright} has examined the strengths, weaknesses, risks, and opportunities of academic software engineering. A key outcome of the workshop is this Dagstuhl Manifesto, serving as a roadmap towards future professional software engineering for software-based research instruments and other software produced and used in an academic context. The manifesto is expressed in terms of a series of actionable {\textquotedblleft}pledges{\textquotedblright} that users and developers of academic research software can take as concrete steps towards improving the environment in which that software is produced.}, author = {Alice Allen and Cecilia Aragon and Christoph Becker and Jeffrey Carver and Andrei Chi{\c s} and Benoit Combemale and Mike Croucher and Kevin Crowston and Daniel Garijo and Ashish Gehani and Carole Goble and Robert Haines and Robert Hirschfeld and James Howison and Kathryn Huff and Caroline Jay and Daniel S. Katz and Claude Kirchner and Katie Kuksenok and Ralf L{\"a}mmel and Oscar Nierstrasz and Matt Turk and van Nieuwpoort, Rob and Matthew Vaughn and Jurgen Vinju} } @article {9998, title = {Stigmergic coordination in FLOSS development teams: Integrating explicit and implicit mechanisms}, journal = {Cognitive Systems Research}, volume = {38}, year = {2016}, pages = {14{\textendash}22}, keywords = {Coordination, Stigmergy}, doi = {10.1016/j.cogsys.2015.12.003}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/COGSYS-RS-\%28HHS\%29-\%282015\%29-\%283\%29.pdf}, author = {Bolici, Francesco and James Howison and Kevin Crowston} } @article {9999, title = {Collaboration through superposition: How the IT artifact as an object of collaboration affords technical interdependence without organizational interdependence}, journal = {MIS Quarterly}, volume = {38}, year = {2014}, month = {3/2104}, pages = {29-50}, abstract = {This paper develops a theory of collaboration through superposition: the process of depositing separate layers on top of each other over time. The theory is developed in a study of development of community-based Free and Open Source Software (FLOSS), through a research arc of discovery (participant observation), replication (two archival case studies) and formalization (a model of developer choices). The theory explains two key findings: 1) the overwhelming majority of work is accomplished with only a single programmer working on a task and 2) when tasks appear too large for an individual they are more likely to be deferred until they are easier, rather than being undertaken through structured teamwork. It is theorized that this way of organizing is key to successful open collaboration where the IT artifact is the object of collaboration, because it allows the co-production of technically interdependent artifacts through motivationally interdependent work. The affordances of software as an object of collaboration are used as a framework to analyze efforts to learn from FLOSS in other domains of work and in the IS function of for-profit organizations.}, doi = {10.25300/MISQ/2014/38.1.02}, url = {http://misq.org/collaboration-through-open-superposition.html}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/CollaborationThroughSuperposition-WorkingPaper.pdf}, author = {James Howison and Kevin Crowston} } @article {Crowston:2009, title = {Free/Libre Open Source Software Development: What we know and what we do not know}, journal = {ACM Computing Surveys}, volume = {44}, year = {2012}, month = {02/2012}, edition = {2}, abstract = {We review the empirical research on Free/Libre and Open Source Software (FLOSS) development and assess the state of the literature. We develop a framework for organizing the literature based on the input-mediator-output- input (IMOI) model from the small groups literature. We present a quantitative summary of articles selected for the review and then discuss findings of this literature categorized into issues pertaining to inputs (e.g., member characteristics, technology use and project characteristics), processes (software development and social processes), emergent states (e.g., trust and task related states) and outputs (e.g. team performance, FLOSS implementation and project evolution). Based on this review, we suggest topics for future research, as well as identifying methodological and theoretical issues for future inquiry in this area, including issues relating to sampling and the need for more longitudinal studies.}, doi = {10.1145/2089125.2089127}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/CrowstonFLOSSReviewPaperPreprint.pdf , https://crowston.syr.edu/sites/crowston.syr.edu/files/Appendix\%201\%20Journal\%20and\%20Conference\%20Names.pdf , https://crowston.syr.edu/sites/crowston.syr.edu/files/Appendix\%202\%20Coding\%20Scheme.pdf , https://crowston.syr.edu/sites/crowston.syr.edu/files/Appendix\%203\%20Studies\%20included\%20in\%20the\%20review.pdf}, author = {Kevin Crowston and Kangning Wei and James Howison and Wiggins, Andrea} } @article {9999, title = {Validity issues in the use of social network analysis with digital trace data}, journal = {Journal of the Association for Information Systems}, volume = {12}, year = {2011}, month = {12/2011}, chapter = {Article 2}, abstract = {There is an exciting natural match between social network analysis methods and the growth of data sources produced by social interactions via information technologies, from online communities to corporate information systems. Information Systems researchers have not been slow to embrace this combination of method and data. Such systems increasingly provide "digital trace data" that provide new research opportunities. Yet digital trace data are substantively different from the survey and interview data for which network analysis measures and interpretations were originally developed. This paper examines ten validity issues associated with the combination of data digital trace data and social network analysis methods, with examples from the IS literature, to provide recommendations for improving the validity of research using this combination.
}, doi = {10.17705/1jais.00282 }, url = {http://aisel.aisnet.org/jais/vol12/iss12/2/}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/JAIS.RA-JAIS-08-0130-ReferencesFixed.pdf}, author = {James Howison and Kevin Crowston and Wiggins, Andrea} } @conference {2011, title = {Work as coordination and coordination as work: A process perspective on FLOSS development projects}, booktitle = {Third International Symposium on Process Organization Studies}, year = {2011}, month = {6/2011}, address = {Corfu, Greece}, url = {http://www.process-symposium.com/}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/PROS-134.pdf}, author = {Kevin Crowston and Carsten {\O}sterlund and James Howison and Bolici, Francesco} } @proceedings {2010, title = {Analyzing Leadership Dynamics in Distributed Group Communication}, year = {2010}, address = {Kauai, HI, 5{\textendash}8 January}, abstract = {We apply social network analysis (SNA) to examine the dynamics of leadership in distributed groups, specifically Free/Libre Open Source Software development projects, and its relation to group performance. Based on prior work on leadership in distributed groups, we identify leaders with those who make the highest level of contribution to the group and assess the degree of leadership by measuring centralization of communications. We compare the dynamics of leadership in two FLOSS projects, one more and one less effective. We find that in both projects, centralization was higher in developer-oriented communications venues than in user-oriented venues, suggesting higher degrees of leadership in developer venues. However, we do not find a consistent relation between centralization and effectiveness. We suggest that SNA can instead be useful for identifying interesting periods in the history of the project, e.g., periods where the leadership of the project is in transition.}, keywords = {FLOSS, Leadership}, issn = {0361-1434 }, doi = {10.1109/HICSS.2010.62}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/07-06-02.pdf}, author = {Kevin Crowston and Wiggins, Andrea and James Howison} } @article {2010, title = {The under-appreciated role of stigmergic coordination in software development}, year = {2010}, abstract = {Coordination in software development teams has been a topic of perennial interest in empirical software engineering research. The vast majority of this literature has drawn on a conceptual separation between work and coordination mechanisms, separate from the work itself, which enable groups to achieve coordination. Traditional recommendations and software methods focused on planning: using analysis to predict and manage dependencies. Empirical research has demonstrated the limits of this approach, showing that many important dependencies are emergent and pointing to the persistent importance of explicit discussion to managing these dependencies as they arise. Drawing on work in Computer-Supported Collaborative Work and building from an analogy to collaboration amongst insects (stigmergy), we argue that the work product itself plays an under-appreciated role in helping software developers manage dependencies as they arise. This short paper presents the conceptual argument with empirical illustrations and explains why this mechanism would have significant implications for Software Engineering coordination research. We discuss issues in marshaling clear positive evidence, arguing that these issues are responsible, in part, for the under-consideration of this mechanism in software engineering and outlining research strategies which may overcome these issues.
}, keywords = {Coordination, FLOSS, Stigmergy}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/stigmergy-short.pdf}, author = {Bolici, Francesco and James Howison and Kevin Crowston} } @conference {Bolici:2009, title = {Coordination without discussion? Socio-technical congruence and Stigmergy in Free and Open Source Software projects}, booktitle = {2nd International Workshop on Socio-Technical Congruence, ICSE}, year = {2009}, month = {19 May}, address = {Vancouver, Canada}, keywords = {Coordination, FLOSS}, url = {http://docs.google.com/View?id=dhncd3jd_405fzt842gv}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Coordination\%20without\%20discussion\%3F\%20Socio-technical\%20congruence.pdf}, author = {Bolici, Francesco and James Howison and Kevin Crowston} } @proceedings {Wiggins:2009, title = {Heartbeat: Measuring Active User Base and Potential User Interest in FLOSS Projects}, volume = {299}, year = {2009}, pages = {94-104}, publisher = {Springer Boston}, address = {Skövde, Sweden, 3-6 June}, abstract = {This paper presents a novel method and algorithm to measure the size of an open source project{\textquoteright}s user base and the level of potential user interest that it generates. Previously unavailable download data at a daily resolution confirms hypothesized patterns related to release cycles. In short, regular users rapidly download the software after a new release giving a way to measure the active user base. In contrast, potential new users download the application independently of the release cycle, and the daily download figures tend to plateau at this rate when a release has not been made for some time. An algorithm for estimating these measures from download time series is demonstrated and the measures are examined over time in two open source projects.}, isbn = {978-3-642-02031-5}, issn = {978-3-642-02031-5}, doi = {10.1007/978-3-642-02032-2\%5f10}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/heartbeat.pdf}, author = {Wiggins, Andrea and James Howison and Kevin Crowston}, editor = {Boldyreff, Cornelia and Kevin Crowston and Lundell, Bj{\"o}rn and Wasserman, Tony} } @article {Li:2008a, title = {Asynchronous Decision-Making in Distributed Teams (Poster)}, year = {2008}, month = {8{\textendash}12 November}, address = {San Diego, CA}, keywords = {Decision-Making, FLOSS}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/CSCW2008Poster11x17Draft.pdf}, author = {Li, Qing and Heckman, Robert and Allen, Eileen E. and Kevin Crowston and Eseryel, U. Yeliz and James Howison and Wiggins, Andrea} } @proceedings {Li:2008, title = {Decision Making Paths in Self-Organizing Technology-Mediated Distributed Teams}, year = {2008}, address = {Paris, France, 14-17 December}, abstract = {This paper investigates decision making in self-organizing technology-mediated distributed teams. This context provides an opportunity to examine how the use of technological support to span temporal and organizational discontinuities affects decision-making processes. 258 software-modification decision episodes were collected from the public emailing lists of six Free/Libre Open Source Software (FLOSS) projects over a span of five years. Six decision-making paths were identified as 1) short-cut decision-making path; 2) implicit-development decision-making path; 3) implicit-evaluation decision-making path; 4) normative decision-making path; 5) dynamic decision-making path; and 6) interrupted/delayed decision-making path. We suggest that the nature of the tasks and the affordances of the technology used reduce the need for explicit coordination, resulting in a broader range of possible decision processes than are observed in face-to-face groups.}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Decision\%20Making\%20Paths\%20in\%20Self\%20Organizing\%20Technology\%20Mediated\%20Dist.pdf}, author = {Li, Qing and Heckman, Robert and Kevin Crowston and James Howison and Allen, Eileen E. and Eseryel, U. Yeliz} } @proceedings {Howison:2008, title = {e{R}esearch workflows for studying free and open source software development}, year = {2008}, note = {Slides from the presentation at the Oxford eResearch Conference of lessons learned in replicating research in eResearch workflows.}, address = {Milan, Italy, 7-10 September}, abstract = {This paper proposes a demonstration of eResearch workflow tools as a model for the research community studying free and open source software and its development. For purposes of background and justification, the paper first introduces eResearch as increasingly practiced in fields such as astrophysics and biology, then contrasts the practice of research on free and open source software. After outlining the suitable public data sources the paper introduces a class of tools known as scientific workflow frameworks, specifically focusing on one---Taverna---and introducing its features. To further explain the tool a complete workflow used for original research on FLOSS is described and the agenda for the live demonstration is outlined. }, keywords = {eResearch, FLOSS, Workflow}, doi = {10.1007/978-0-387-09684-1_39}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/eResearchWorkflows.pdf}, author = {James Howison and Wiggins, Andrea and Kevin Crowston} } @proceedings {, title = {eSocialScience for Free/Libre Open Source Software researchers}, year = {2008}, address = {Manchester, UK, 18-20 June}, abstract = {This abstract presents a case study of the potential application of eScience tools and practices for the social science research community studying Free/Libre Open Source Software (FLOSS) development practices. We first describe the practice of research on FLOSS to motivate the need for eScience. After outlining suitable public data sources, we describe our initial efforts to introduce eScience tools for FLOSS research, potential obstacles and how the use of such tools might affect the practice of research in this field.}, keywords = {eScience, FLOSS}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/NCeSS2008CrowstonHowisonWiggins.pdf}, author = {Kevin Crowston and James Howison and Wiggins, Andrea} } @proceedings {Scialdone:2008, title = {Group Maintenance in Technology-Supported Distributed Teams}, year = {2008}, address = {Anaheim, CA, 9-13 August}, abstract = {Are geographically-distributed teams which exhibit high levels of group maintenance between members successful? We answer this through content analysis of emails from two Free/Libre Open Source Software (FLOSS) teams. Our results illustrate that the groups utilize low levels of organizational citizenship behaviors and high levels of positive politeness actions.}, keywords = {FLOSS, Group Maintenance}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/GroupMaintenance.pdf}, author = {Scialdone, Michael J. and Li, Na and James Howison and Heckman, Robert and Kevin Crowston} } @proceedings {Crowston:2008a, title = {Opportunities for eScience research on Free/Libre Open Source Software}, year = {2008}, address = {Oxford, England, 11-13 September}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Opportunities\%20for\%20eScience\%20research\%20on\%20Free.pdf}, author = {Kevin Crowston and James Howison and Wiggins, Andrea} } @proceedings {Wiggins:2008, title = {Replication of FLOSS Research as eResearch}, year = {2008}, address = {Oxford, England, 11-13 September}, abstract = {We are working to introduce the ideas of eResearch to a multi-disciplinary research domain: those researchers examining Free/Libre and Open Source Software (FLOSS) and its development (Howison, Wiggins, \& Crowston, 2008). The first phase of this work focused on building a repository for data on FLOSS teams, FLOSSmole (Howison, Conklin, \& Crowston, 2006), and collaborating with other nascent data repositories in the field. Recently we have begun a second phase, which is to introduce another established principle of eResearch, that of broader collaboration through shared workflows accessing these data repositories. To provide an example of the potential value of this principle, we are replicating seminal FLOSS papers using eResearch approaches. This paper describes research outcomes and lessons learned from translating published literature into eResearch workflows.}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/ReplicationOfFLOSSResearch.pdf}, author = {Wiggins, Andrea and James Howison and Kevin Crowston} } @proceedings {Wiggins:2008a, title = {Social dynamics of FLOSS team communication across channels}, year = {2008}, pages = {131-142}, publisher = {Springer Boston}, address = {Milan, Italy, 7-10 September}, abstract = {This paper extends prior investigation into the social dynamics of free and open source (FLOSS) teams by examining the methodological questions arising from research using social network analysis on open source projects. We evaluate the validity of data sampling by examining dynamics of communication centralization, which vary across multiple communication channels. We also introduce a method for intensity-based smoothing in dynamic social network analysis.}, keywords = {FLOSS}, isbn = {978-0-387-09683-4}, issn = {1571-5736 (Print) 1861-2288 (Online)}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/DSNAWigginsIFIP.pdf}, author = {Wiggins, Andrea and James Howison and Kevin Crowston} } @article {Howison:2008a, title = {Towards a data and workflow collaboratory for research on Free and Open Source Software and its development (Poster)}, year = {2008}, address = {Los Angeles, CA}, keywords = {eScience, FLOSS, Workflow}, author = {James Howison and Squire, Megan and Kevin Crowston} } @article {Howison:2007, title = {Building a collaboratory for research on open source software development (Poster)}, year = {2007}, address = {Ann Arbor, MI}, keywords = {eScience, FLOSS}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Howison_eSocSciPoster-small.pdf}, author = {James Howison and Squire, Megan and Kevin Crowston} } @proceedings {Heckman:2007, title = {Emergent decision-making practices in Free/Libre Open Source Software FLOSS development teams}, year = {2007}, address = {Limerick, Ireland, 10-14 June}, abstract = {We seek to identify work practices that make Free/Libre Open Source Software (FLOSS) development teams effective. Particularly important to team effectiveness is decision making. In this paper, we report on an inductive qualitative analysis of 360 decision episodes of six FLOSS development teams. Our analysis revealed diversity in decision-making practices that seem to be related to differences in overall team characteristics and effectiveness. }, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/20070320\%20OSS\%20Conference_v15_final\%20submitted.pdf}, author = {Heckman, Robert and Kevin Crowston and Eseryel, U. Yeliz and James Howison and Allen, Eileen E. and Li, Qing} } @article {2007, title = {Investigating the Dynamics of FLOSS Development Teams (Poster)}, year = {2007}, note = {SD 2007 poster - Full Adobe PDF 2007 HSD PI{\textquoteright}s conference poster reporting on the grant project work to date in a full Adobe PDF file. HSD 2007 poster - Small PDF HSD 2007 conference grant progress reporting poster in a smaller PDF file. }, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/HSDposter_8.ai_.pdf , https://crowston.syr.edu/sites/crowston.syr.edu/files/HSDposter_8.pdf}, author = {Li, Na and Li, Qing and Kangning Wei and Heckman, Robert and Eseryel, U. Yeliz and Liddy, Elizabeth D. and James Howison and Kevin Crowston and Allen, Eileen E. and Scialdone, Michael J. and Inoue, Keisuke and Harwell, Sarah and Rowe, Steven and McCracken, Nancy and Wiggins, Andrea} } @article {2007, title = {A proposed data and analysis archive for research on Free and Open Source Software and its development (Poster)}, year = {2007}, address = {Ann Arbor, MI}, keywords = {FLOSS}, author = {James Howison and Squire, Megan and Kevin Crowston} } @article {2007, title = {A proposed data and analysis archive for research on Free and Open Source Software and its development (Poster)}, year = {2007}, keywords = {FLOSS}, author = {James Howison and Squire, Megan and Kevin Crowston} } @article {Crowston:2007, title = {The role of face-to-face meetings in technology-supported self-organizing distributed teams}, journal = {IEEE Transactions on Professional Communications}, volume = {50}, number = {3}, year = {2007}, pages = {185{\textendash}203}, abstract = {We examine the role of face-to-face meetings in the context of technology-supported self-organizing distributed or virtual teams, specifically Free/Libre Open Source Software (FLOSS) development teams. Based on a qualitative inductive analysis of data from interviews and observations at FLOSS conferences, we identify a variety of settings in which developers meet face-to-face, activities performed in these settings and benefits obtained. Contrary to the conventional wisdom, FLOSS developers generally do not meet face-to-face until the project is well under way. An additional benefit of face-to-face meetings is time away from a regular job and speed of interaction for certain kinds of tasks.}, keywords = {FLOSS}, doi = {10.1109/TPC.2007.902654}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/070122.pdf}, author = {Kevin Crowston and James Howison and Masango, Chengetai and Eseryel, U. Yeliz} } @article {Crowston:2007b, title = {Self-organization of teams in free/libre open source software development}, journal = {Information and Software Technology Journal: Special issue on Understanding the Social Side of Software Engineering, Qualitative Software Engineering Research}, volume = {49}, year = {2007}, pages = {564{\textendash}575}, abstract = {This paper provides empirical evidence about how free/libre open source software development teams self-organize their work, specifically, how tasks are assigned to project team members. Following a case study methodology, we examined developer interaction data from three active and successful FLOSS projects using qualitative research methods, specifically inductive content analysis, to identify the task-assignment mechanisms used by the participants. We found that {\textquoteleft}self-assignment{\textquoteright} was the most common mechanism across three FLOSS projects. This mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research.}, doi = {10.1016/j.infsof.2007.02.004}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/060918.pdf}, author = {Kevin Crowston and Kangning Wei and Li, Qing and Eseryel, U. Yeliz and James Howison} } @article {Crowston:2006d, title = {Assessing the health of open source communities}, journal = {IEEE Computer}, volume = {39}, number = {5}, year = {2006}, month = {May}, pages = {89-91}, abstract = {An invited column that discusses what a healthy FLOSS community looks like, and how one ought to go about assessing it (particularly in the context of software specification).}, doi = {10.1109/MC.2006.152}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/HealthOfAFlossCommunity.pdf}, author = {Kevin Crowston and James Howison} } @inbook {Crowston:2006c, title = {Coordination theory: A ten-year retrospective}, booktitle = {Human-Computer Interaction in Management Information Systems}, year = {2006}, pages = {120-138}, publisher = {M. E. Sharpe, Inc.}, organization = {M. E. Sharpe, Inc.}, abstract = {Since the initial publication in 1994, Coordination Theory has been referenced in nearly 300 journal articles, book chapters, conference papers and theses. Coordination Theory provides an approach to a core problem in HCI: analyzing group work to suggest alternative approaches involving computer support. Coordination Theory suggests identifying the dependencies between the tasks the different group members are carrying out and the coordination mechanisms the group use to coordinate their work and then considering alternative mechanisms. This chapter will analyze the contribution of this body of research to determine how Coordination Theory has been used for user task analysis and modelling for HCI. Issues that will be addressed include: 1)how the theory has been applied; 2) factors that led to the success of the theory; and 3)identification of areas needing further research. }, keywords = {Coordination}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/CT\%20Review\%20to\%20distribute.pdf}, author = {Kevin Crowston and Rubleske, Joe and James Howison}, editor = {Zhang, P. and Galletta, D.} } @proceedings {Crowston:2006b, title = {Core and periphery in Free/Libre and Open Source software team communications}, year = {2006}, address = {Kaua{\textquoteright}i, Hawai{\textquoteright}i, January}, abstract = {The concept of the core group of developers is important and often discussed in empirical studies of FLOSS projects. This paper examines the question, {\textquotedblleft}how does one empirically distinguish the core?{\textquotedblright} Being able to identify the core members of a FLOSS development project is important because many of the processes necessary for successful projects likely involve core members differently than peripheral members, so analyses that mix the two groups will likely yield invalid results. We compare 3 analysis approaches to identify the core: the named list of developers, a Bradford{\textquoteright}s law analysis that takes as the core the most frequent contributors and a social network analysis of the interaction pattern that identifies the core in a core-and-periphery structure. We apply these measures to the interactions around bug fixing for 116 SourceForge projects. The 3 techniques identify different individuals as core members; examination of which individuals are identified leads to suggestions for refining the measures. All 3 measures though suggest that the core of FLOSS projects is a small fraction of the total number of contributors.}, keywords = {FLOSS}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/CoreAndPeripheryInFreeLibre.pdf}, author = {Kevin Crowston and Kangning Wei and Li, Qing and James Howison} } @proceedings {Heckman:2006b, title = {Emergent decision-making practices in technology-supported self-organizing distributed teams}, year = {2006}, address = {Milwaukee, WI, 10{\textendash}13 Dec}, abstract = {We seek to identify work practices that make technology-supported self-organizing distributed (or virtual) teams (TSSODT for short) effective in producing outputs satisfactory to their sponsors, meeting the needs of their members and continuing to function. A particularly important practice for team effectiveness is decision making: are the right decisions made at the right time to get the work done in a way that satisfies team sponsors, keeps contributors happy and engaged, and enables continued team success? In this research-in-progress paper, we report on an inductive qualitative analysis of 120 decision episodes taken by 2 Free/libre Open Source Software development teams. Our analysis revealed differences in decision-making practices that seem to be related to differences in overall team effectiveness.}, keywords = {Decision-Making, FLOSS}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Emergent\%20Decision\%20Making\%20Practices\%20In\%20Technology\%20Supported\%20Self\%20O.pdf}, author = {Heckman, Robert and Kevin Crowston and Li, Qing and Allen, Eileen E. and Eseryel, U. Yeliz and James Howison and Kangning Wei} } @article {Howison:2006, title = {FLOSSmole: A collaborative repository for FLOSS research data and analyses}, journal = {International Journal of Information Technology and Web Engineering}, volume = {1}, number = {3}, year = {2006}, pages = {17{\textendash}26}, abstract = {This paper introduces and expands on previous work on a collaborative project, called FLOSSmole (formerly OSSmole), designed to gather, share and store comparable data and analyses of free and open source software development for academic research. The project draws on the ongoing collection and analysis efforts of many research groups, reducing duplication, and promoting compatibility both across sources of FLOSS data and across research groups and analyses. The paper outlines current difficulties with the current typical quantitative FLOSS research process and uses these to develop requirements and presents the design of the system.}, keywords = {FLOSSmole}, issn = {1554-1045 }, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/FLOSSmole.pdf}, author = {James Howison and Conklin, Megan S. and Kevin Crowston} } @article {Crowston:2006a, title = {Hierarchy and centralization in Free and Open Source Software team communications}, journal = {Knowledge, Technology \& Policy}, volume = {18}, number = {4}, year = {2006}, pages = {65{\textendash}85}, abstract = {Free/Libre Open Source Software (FLOSS) development teams provide an interesting and convenient setting for studying distributed work. We begin by answering perhaps the most basic question: what is the social structure of these teams? Based on a social network analysis of interactions represented in 62,110 bug reports from 122 large and active projects, we find that some OSS teams are highly centralized, but contrary to expectation, others are not. Projects are mostly quite hierarchical on four measures of hierarchy, consistent with past research but contrary to the popular image of these projects. Furthermore, we find that the level of centralization is negatively correlated with project size, suggesting that larger projects become more modular. The paper makes a further methodological contribution by identifying appropriate analysis approaches for interaction data. We conclude by sketching directions for future research.}, keywords = {FLOSS}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/HierarchyAndCentralization.pdf}, author = {Kevin Crowston and James Howison} } @article {Crowston:2006, title = {Information systems success in Free and Open Source Software development: Theory and measures}, journal = {Software Process{\textendash}Improvement and Practice}, volume = {11}, number = {2}, year = {2006}, pages = {123{\textendash}148}, abstract = {Information systems success is one of the most widely used dependent variables in information systems (IS) research, but research on Free/Libre and Open Source software (FLOSS) often fails to appropriately conceptualize this important concept. In this paper, we reconsider what success means within a FLOSS context. We first review existing models of IS success and success variables used in FLOSS research and assess them for their usefulness, practicality and fit to the FLOSS context. Then, drawing on a theoretical model of group effectiveness in the FLOSS development process, as well as an online discussion group with developers, we present additional concepts that are central to an appropriate understanding of success for FLOSS. In order to examine the practicality and validity of this conceptual scheme, the second half of our paper presents an empirical study that demonstrates its operationalization of the chosen measures and assesses their internal validity. We use data from SourceForge to measure the project{\textquoteright}s effectiveness in team building, the speed of the project at responding to bug reports and the project{\textquoteright}s popularity. We conclude by discussing the implications of this study for our proposed extension of IS success in the context of FLOSS development and highlight future directions for research.}, keywords = {FLOSS, Success}, doi = {10.1002/spip.259}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/InformationSystemsSuccessInFree.pdf}, author = {Kevin Crowston and James Howison and Annabi, Hala} } @article {2006, title = {Investigating the Dynamics of FLOSS Development Teams (Poster)}, year = {2006}, note = {Poster describing the current state of the project for the HSD Principal Investigators{\textquoteright} conference, 14-15 September 2006, Washington DC.}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/hsd2006poster.pdf}, author = {Li, Qing and Kangning Wei and Heckman, Robert and Eseryel, U. Yeliz and Liddy, Elizabeth D. and James Howison and Kevin Crowston and Allen, Eileen E. and Inoue, Keisuke and Harwell, Sarah and Rowe, Steven and McCracken, Nancy} } @conference {Li:2006, title = {Language and power in self-organizing distributed teams}, booktitle = {OCIS Division, Academy of Management Conference}, year = {2006}, address = {Atlanta, GA}, abstract = {In this paper, a comparative case study is conducted to explore the way power is expressed and exercised through language use in distributed or virtual teams. Our research questions are {\textquotedblleft}how is power expressed in online interactions in self-organizing distributed teams, in a context without formal authority or hierarchy?{\textquotedblright} and {\textquotedblleft}What effects do expressions of power have on team outcomes?{\textquotedblright} To fully understand the role of power in self-organizing teams, we apply an input-process-output model on two open source projects-one successful and the other less successful. Two set of codes (source of power and power mechanism) are drawn from the data, and different power patterns interestingly show up between them. The findings lead us to speculate that strong, centralized leadership, the assertive exercise of power, and direct language may contribute to effectiveness in FLOSS teams. And the relevant conclusions and suggestions are provided for further research.}, keywords = {FLOSS}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/LanguageAndPowerInSelf-organizing.pdf}, author = {Li, Qing and Kevin Crowston and Heckman, Robert and James Howison} } @proceedings {Howison:2006sd, title = {Social dynamics of free and open source team communications}, year = {2006}, pages = {319-330}, address = {Lake Como, Italy, 8-9 June}, abstract = {This paper furthers inquiry into the social structure of free and open source software (FLOSS) teams by undertaking social network analysis across time. Contrary to expectations, we confirmed earlier findings of a wide distribution of centralizations even when examining the networks over time. The paper also provides empirical evidence that while change at the center of FLOSS projects is relatively uncommon, participation across the project communities is highly skewed, with many participants appearing for only one period. Surprisingly, large project teams are not more likely to undergo change at their centers.}, keywords = {FLOSS}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/SocialDynamics.pdf}, author = {James Howison and Inoue, Keisuke and Kevin Crowston} } @conference {Conklin:2005, title = {Collaboration Using OSSmole: A repository of FLOSS data and analyses}, booktitle = {Symposium on Mining Software Repositories}, year = {2005}, month = {05/2005}, address = {St. Louis}, abstract = {This paper introduces a collaborative project OSSmole designed to collect, share, and store comparable data and analyses of free, libre and open source software (FLOSS) development for research purposes. The project is designed to be a clearinghouse for data from the ongoing collection and analysis efforts of many disparate research groups. A collaborative data repository will reduce duplication and promote compatibility both across sources of FLOSS data and across research groups and analyses. The primary objective of OSSmole is to mine FLOSS source code repositories and provide the resulting data and summary analyses as open source products. However, the OSSmole data model additionally supports donated raw and summary data from a variety of open source researchers and other software repositories. The paper first outlines current difficulties with the typical quantitative FLOSS research process and uses these to develop requirements for such a collaborative data repository. Finally, the design of the OSSmole system is presented, as well as examples of current research and analyses using OSSmole.}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/CollaborationUsingOSSmole.pdf}, author = {Conklin, Megan S. and James Howison and Kevin Crowston} } @proceedings {Crowston:2005, title = {Coordination of Free/Libre Open Source Software development}, year = {2005}, address = {Las Vegas, NV, USA, December}, abstract = {The apparent success of free/libre open source software (FLOSS) development projects such as Linux, Apache, and many others has raised the question, what lessons from FLOSS development can be transferred to mainstream software development? In this paper, we use coordination theory to analyze coordination mechanisms in FLOSS development and compare our analysis with existing literature on coordination in proprietary software development. We examined developer interaction data from three active and successful FLOSS projects and used content analysis to identify the coordination mechanisms used by the participants. We found that there were similarities between the FLOSS groups and the reported practices of the proprietary project in the coordination mechanisms used to manage task-task dependencies. However, we found clear differences in the coordination mechanisms used to manage task-actor dependencies. While published descriptions of proprietary software development involved an elaborate system to locate the developer who owned the relevant piece of code, we found that {\textquotedblleft}self-assignment{\textquotedblright} was the most common mechanism across three FLOSS projects. This coordination mechanism is consistent with expectations for distributed and largely volunteer teams. We conclude by discussing whether these emergent practices can be usefully transferred to mainstream practice and indicating directions for future research.}, keywords = {Coordination, FLOSS}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Coordination\%20of\%20Free\%20Libre\%20Open\%20Source\%20Software\%20Development.pdf , https://crowston.syr.edu/sites/crowston.syr.edu/files/CoordinationFreeLibreOSSDevSlides.pdf}, author = {Kevin Crowston and Kangning Wei and Li, Qing and Eseryel, U. Yeliz and James Howison} } @proceedings {Crowston:2005e, title = {Effective work practices for FLOSS development: A model and propositions}, year = {2005}, note = {"Effective work practices for Software Engineering: Free/Libre Open Source Software Development". Presentation at the Workshop on Interdisciplinary Software Engineering 2004, SIGSOFT 2004/FSE-12 Conference, Newport Beach, CA, 5 November. Powerpoint file.}, address = {Big Island, Hawai{\textquoteright}i, January}, abstract = {We review the literature on Free/Libre Open Source Software (FLOSS) development and on software development, distributed work and teams more generally to develop a theoretical model to explain the performance of FLOSS teams. The proposed model is based on Hackman{\textquoteright}s [1] model of effectiveness of work teams, with coordination theory [2] and collective mind [3] to extend Hackman{\textquoteright}s model by elaborating team practices relevant to effectiveness in software development. We propose a set of propositions to guide further research.}, doi = {10.1109/HICSS.2005.222}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/22680197a.pdf , https://crowston.syr.edu/sites/crowston.syr.edu/files/041101\%20Wiser\%20Presentation.pdf}, author = {Kevin Crowston and Annabi, Hala and James Howison and Masango, Chengetai} } @conference {Crowston:2005b, title = {Face-to-face interactions in self-organizing distributed teams}, booktitle = {Academy of Management Conference}, year = {2005}, address = {Honolulu, HI}, abstract = {We explore the role of face-to-face meetings in the life of distributed teams using data from Free/Libre Open Source Software (FLOSS) development teams. Such distributed teams are part of many organizations{\textquoteright} new vision of management in the 21st century. Practitioner research has suggested the need for face-to-face meetings when a team is formed, but few studies have considered the role of face-to-face meetings during a team{\textquoteright}s life. Based on a qualitative inductive analysis of data from interviews and observations at FLOSS conferences, we identify a variety of settings in which FLOSS developers meet face-to-face, activities performed in these settings and benefits obtained. Contrary to prior research, we find that FLOSS developers generally do not meet until the project is well under way. We also find that an additional benefit of face-to-face meetings is time away from a regular job. We conclude by noting limitations in our data collection due to a focus on core developers in large projects and with directions for further research.}, keywords = {FLOSS}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/FaceToFace\%20Interactions.pdf}, author = {Kevin Crowston and James Howison and Masango, Chengetai and Eseryel, U. Yeliz} } @article {Crowston:2005c, title = {The social structure of Free and Open Source Software development}, journal = {First Monday}, volume = {10}, number = {2}, year = {2005}, note = {First Monday, Special Issue $\#$2: Open Source {\textemdash} 3 October 2005 The social structure of free and open source software development (originally published in Volume 10, Number 2, February 2005)}, abstract = {Metaphors, such as the Cathedral and Bazaar, used to describe the organization of FLOSS projects typically place them in sharp contrast to proprietary development by emphasizing FLOSS{\textquoteright}s distinctive social and communications structures. But what do we really know about the communication patterns of FLOSS projects? How generalizable are the projects that have been studied? Is there consistency across FLOSS projects? Questioning the assumption of distinctiveness is important because practitioner{\textendash}advocates from within the FLOSS community rely on features of social structure to describe and account for some of the advantages of FLOSS production. To address this question, we examined 120 project teams from SourceForge, representing a wide range of FLOSS project types, for their communications centralization as revealed in the interactions in the bug tracking system. We found that FLOSS development teams vary widely in their communications centralization, from projects completely centered on one developer to projects that are highly decentralized and exhibit a distributed pattern of conversation between developers and active users. We suggest, therefore, that it is wrong to assume that FLOSS projects are distinguished by a particular social structure merely because they are FLOSS. Our findings suggest that FLOSS projects might have to work hard to achieve the expected development advantages which have been assumed to flow from "going open." In addition, the variation in communications structure across projects means that communications centralization is useful for comparisons between FLOSS teams. We found that larger FLOSS teams tend to have more decentralized communication patterns, a finding that suggests interesting avenues for further research examining, for example, the relationship between communications structure and code modularity.}, keywords = {FLOSS}, url = {http://firstmonday.org/htbin/cgiwrap/bin/ojs/index.php/fm/article/view/1207/1127}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Social\%20structure\%20of\%20Free\%20and\%20Open\%20Source\%20Software\%20development.pdf}, author = {Kevin Crowston and James Howison} } @conference {2004, title = {Effective work practices for software engineering}, booktitle = {Proceedings of the 2004 ACM workshop on Interdisciplinary software engineering research (WISER {\textquoteright}04)}, year = {2004}, pages = {18}, publisher = {ACM Press}, organization = {ACM Press}, address = {Newport Beach, CA, USA}, abstract = {We review the literature on Free/Libre Open Source Software (FLOSS) development and on software development, distributed work and teams more generally to develop a theoretical model to explain the performance of FLOSS teams. The proposed model is based on Hackman{\textquoteright}s [34] model of effectiveness of work teams, with coordination theory [52] and collective mind [79] to extend Hackman{\textquoteright}s model by elaborating team practices relevant to effectiveness in software development. We propose a set of propositions to guide further research.}, keywords = {FLOSS}, isbn = {1581139888}, doi = {10.1145/1029997.1030003}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/p18-crowston.pdf}, author = {Kevin Crowston and Annabi, Hala and James Howison and Masango, Chengetai} } @conference {Howison:2004, title = {The perils and pitfalls of mining SourceForge}, booktitle = {Workshop on Mining Software Repositories, 26th International Conference on Software Engineering}, year = {2004}, address = {Edinburgh, Scotland}, abstract = {SourceForge provides abundant accessible data from Open Source Software development projects, making it an attractive data source for software engineering research. However it is not without theoretical peril and practical pitfalls. In this paper, we outline practical lessons gained from our spidering, parsing and analysis of SourceForge data. SourceForge can be practically difficult: projects are defunct, data from earlier systems has been dumped in and crucial data is hosted outside SourceForge, dirtying the retrieved data. These practical issues play directly into analysis: decisions made in screening projects can reduce the range of variables, skewing data and biasing correlations. SourceForge is theoretically perilous: because it provides easily accessible data items for each project, tempting researchers to fit their theories to these limited data. Worse, few are plausible dependent variables. Studies are thus likely to test the same hypotheses even if they start from different theoretical bases. To avoid these problems, analyses of SourceForge projects should go beyond project level variables and carefully consider which variables are used for screening projects and which for testing hypotheses.}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/The\%20perils\%20and\%20pitfalls\%20of\%20mining\%20SourceForge.pdf}, author = {James Howison and Kevin Crowston} } @conference {Crowston:2004c, title = {Towards a portfolio of FLOSS project success measures}, booktitle = {Workshop on Open Source Software Engineering, 26th International Conference on Software Engineering}, year = {2004}, address = {Edinburgh}, abstract = {Project success is one of the most widely used dependent variables in information systems research. However, conventional measures of project success are difficult to apply to Free/Libre Open Source Software projects. In this paper, we present an analysis of four measures of success applied to SourceForge projects: number of members of the extended development community, project activity, bug fixing time and number of downloads. We argue that these four measures provide different insights into the collaboration and control mechanisms of the projects.}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/Towards_a_Portfolio_\%20of\%20_FLOSS_Project.pdf}, author = {Kevin Crowston and Annabi, Hala and James Howison and Masango, Chengetai} } @proceedings {Crowston:2003c, title = {Defining Open Source Software project success}, year = {2003}, address = {Seattle, WA, December}, abstract = {Information systems success is one of the most widely used dependent variables in information systems research. In this paper, we identify a range of measures that can be used to assess the success of Open Source Software (OSS) projects. We identify measures based on a review of the literature, a consideration of the OSS development process and an analysis of the opinions of OSS developers. For each measure, we provide examples of how they might be used in a study of OSS development.}, keywords = {FLOSS}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/icis2003success.pdf}, author = {Kevin Crowston and Annabi, Hala and James Howison} } @conference {Crowston:2003e, title = {The social structure of Open Source Software development teams}, booktitle = {The IFIP 8.2 Working Group on Information Systems in Organizations Organizations and Society in Information Systems (OASIS) Workshop}, year = {2003}, address = {Seattle, WA}, abstract = {Open Source Software development teams provide an interesting and convenient setting for studying distributed work. We begin by answering perhaps the most basic question: what is the social structure of these teams? Based on a social network analysis of interactions represented in 62,110 bug reports from 122 large and active projects, we find that some OSS teams are highly centralized, but contrary to expectation, others are not. Furthermore, we find that the level of centralization is negatively correlated with project size, suggesting that larger projects become more modular. The paper makes a further methodological contribution by identifying appropriate analysis approaches for interaction data. We conclude by sketching directions for future research.}, keywords = {FLOSS}, attachments = {https://crowston.syr.edu/sites/crowston.syr.edu/files/icis2003sna.pdf}, author = {Kevin Crowston and James Howison} }