2007
DOI: 10.1016/j.infsof.2007.02.004
|View full text |Cite
|
Sign up to set email alerts
|

Self-organization of teams for free/libre open source software development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
91
0
4

Year Published

2008
2008
2022
2022

Publication Types

Select...
5
3

Relationship

1
7

Authors

Journals

citations
Cited by 164 publications
(98 citation statements)
references
References 43 publications
0
91
0
4
Order By: Relevance
“…Free/libre Open Source Software (FLOSS) is software developed and maintained by individuals working closely together in globally-distributed environments [5]. The FLOSS development communities can include dozens, hundreds or even thousands of volunteers who, for the most part, are not employed by and do not receive profits from the projects [20].…”
Section: Introductionmentioning
confidence: 99%
“…Free/libre Open Source Software (FLOSS) is software developed and maintained by individuals working closely together in globally-distributed environments [5]. The FLOSS development communities can include dozens, hundreds or even thousands of volunteers who, for the most part, are not employed by and do not receive profits from the projects [20].…”
Section: Introductionmentioning
confidence: 99%
“…A self-organizing network is characterized by the absence of an explicit coordinating leadership (Wagner & Leydesdorff, 2005), the ability to develop without significant direct external interference (Rycroft & Kash, 2004), the intense inter-relationship and communication between network participants (Anderson, 1999), the coevolution of the participants and the network (Kash & Rycoft, 2000), the learning capacity and use of this learning (Vany, 1996), the knowledge of the capabilities of all participants and access to these capabilities (Kash & Rycroft, 2002), the existence of mutual trust and aid (Kash & Rycroft, 2002), the ability to meet quickly a team to solve a problem and then dissolve it right after (Quinn et al, 1996) and the use of information systems to systematize the knowledge developed and accumulated by the network (Crowston et al, 2007).…”
Section: Self-organizing Networkmentioning
confidence: 99%
“…Among the various works already carried out, we can find examples related to academic and scientific research networks (Bennett & Kidwell, 2001;Wagner & Leydesdorff, 2005), development networks of free software (Crowston et al, 2007), research and development networks in the automotive industry (Rycroft & Kash, 2004), networks of companies to improve sustainability (Espinosa & Porter, 2011), local public administration networks for economic policy development (Lee et al, 2012), networks of farmers (Dutta et al, 2005), networks of fashion industries (Schuh et al, 2008;Scherrer-Rathje et al, 2009), team management (Parker et al, 2015), among others. In all the literature reviewed, self-organizing networks were not addressed in the scope of Six Sigma programs, although there are common characteristics.…”
Section: Self-organizing Networkmentioning
confidence: 99%
See 1 more Smart Citation
“…Consequently, how to mitigate the productivity impact of distributed work has become a key concern in methods literature FLOSSD differs from traditional software engineering in its transparency (Scacchi et al 2006), lack of formal SDMs, PMFs, budgets, schedules or rule structures (Scacchi 2007;Scacchi et al 2006), developer self-assignment of tasks (Crowston et al 2007) and success measures (Crowston et al 2004;Crowston et al 2006). For example, Crowston et al (2006) FLOSSD projects are organized into layers -a small group of core developers, a larger group of ad hoc developers who make minor changes and bug fixes and an even larger group who report problems (Mockus et al 2002).…”
Section: The Scope Of the Design Agentmentioning
confidence: 99%