@article {2020, title = {GitLab: Work where you want, when you want}, journal = {Journal of Organizational Design}, volume = {9}, year = {2020}, month = {2020/11/16}, pages = {23}, abstract = {

GitLab is a software company that works {\textquotedblleft}all remote{\textquotedblright} at the scale of more than 1000 employees located in more than 60 countries. GitLab has no physical office and its employees can work from anywhere they choose. Any step of the organizational life of a GitLab employee (e.g., hiring, onboarding and firing) is performed remotely, except for a yearly companywide gathering. GitLab strongly relies on asynchronous coordination, allowing employees to work anytime they want. After highlighting some of the main practices implemented by GitLab to effectively work all remotely and asynchronously, I asked renowned organizational scientists their thoughts on this interesting case and to question the generalizability of the all remote asynchronous model. Understanding whether and under what conditions this model can succeed can be of guidance for organizational designers that are now considering different remote models in response of the COVID-19 shock and its aftermath.

}, isbn = {2245-408X}, doi = {10.1186/s41469-020-00087-8}, attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/s41469-020-00087-8.pdf}, author = {Choudhury, Prithwiraj and Crowston, Kevin and Dahlander, Linus and Minervini, Marco S. and Raghuram, Sumita} } @article {9998, title = {Group maintenance in technology-supported distributed teams}, journal = {Information \& Management}, volume = {51}, year = {2014}, month = {4/2014}, pages = {297-309}, abstract = {In this paper we investigate group maintenance behavior in community-based Free/Libre Open Source Software (FLOSS) development teams. Adopting a sociolinguistic perspective, we conceptualize group maintenance behavior as interpersonal communication tactics{\textemdash}specifically, social presence and politeness tactics{\textemdash}that help maintain relationships among group members. Developer email messages were collected from two FLOSS projects with different development status and content-analyzed to identify frequently-used group maintenance tactics. We then compared the two projects on the group maintenance tactics used, finding differences that reflect changes in the project work practices. Our work contributes theoretically to FLOSS research and has practical implications for FLOSS practitioners. }, doi = {10.1016/j.im.2014.02.001}, attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/Group_maintenance\%20paper_part\%20I_20140122_final.pdf}, author = {Kangning Wei and Kevin Crowston and Li, Na and Heckman, Robert} } @proceedings {Scialdone:2009, title = {Group Maintenance Behaviours of Core and Peripheral Members of Free/Libre Open Source Software Teams}, year = {2009}, address = {Skövde, Sweden, 3-6 June}, abstract = {Group Maintenance is pro-social, discretionary, and relation-building behavior that occurs between members of groups in order to maintain reciprocal trust and cooperation. This paper considers how Free/libre Open Source Software (FLOSS) teams demonstrate such behaviors within the context of e-mail, as this is the primary medium through which such teams communicate. We compare group maintenance behaviors between both core and peripheral members of these groups, as well as behaviors between a group that remains producing software today and one which has since dissolved. Our findings indicate that negative politeness tactics (those which show respect for the autonomy of others) may be the most instrumental group maintenance behaviors that contribute to a FLOSS group{\textquoteleft}s ability to survive and continue software production. }, keywords = {FLOSS, Group Maintenance}, attachments = {https://floss.syr.edu/sites/crowston.syr.edu/files/34finalmjs.pdf}, author = {Scialdone, Michael J. and Heckman, Robert and Kevin Crowston}, editor = {Boldyreff, Cornelia and Kevin Crowston and Lundell, Bj{\"o}rn and Wasserman, Tony} } @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://floss.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} }