Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crowston, Howison, Annabi - 2006 #2

Open
GeorgLink opened this issue Jan 27, 2017 · 1 comment
Open

Crowston, Howison, Annabi - 2006 #2

GeorgLink opened this issue Jan 27, 2017 · 1 comment

Comments

@GeorgLink
Copy link
Contributor

GeorgLink commented Jan 27, 2017

image

image

Crowston, K., Howison, J., & Annabi, H. (2006). Information systems success in free and open source software development: theory and measures. Software Process: Improvement and Practice, 11(2), 123–148. https://doi.org/10.1002/spip.259

@GeorgLink
Copy link
Contributor Author

Great article, always worth going back to.

The authors reviewed IS success literature and determined that the success factors (measures) in are determined by the organizational context of IS, which is not applicable to FOSS. Whereas IS success measures are outcome-oriented (e.g. market share, user satisfaction, code quality), the FOSS success factors more up the process of software development (developers are uses, developers are interested in process, developers have to be satisfied). Then the authors asked open source developers what metrics they look at and out came seven broad categories of metrics: User, Product, Process, Developers, Use, Recognition, and Influence. When looking at FOSS research and how it viewed FOSS success, four types emerged: system creation (process), system quality (product), system use (use), and system consequences (users and developers). Table 5 is the summary of concepts for IS success in FLOSS organized by process phase.

The advantage of the model is grouping of metrics into the process phases, thus indicating when metrics are most appropriately used. This grouping can also be indicative of the types of actions that can be informed by metrics. For example, metrics in the 'system creation and maintenance' phase may inform actions that impact governance, processes, tools, and developer interactions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant