Peopleware: productive projects and teams
Peopleware: productive projects and teams
On building software process models under the lamppost
ICSE '87 Proceedings of the 9th international conference on Software Engineering
The Unified Modeling Language user guide
The Unified Modeling Language user guide
An empirical investigation into the adoption of systems development methodologies
Information and Management
Qualitative Methods in Empirical Studies of Software Engineering
IEEE Transactions on Software Engineering
Software assessments, benchmarks, and best practices
Software assessments, benchmarks, and best practices
An encounter with grounded theory: tackling the practical and philosophical issues
Qualitative research in IS
Software Engineering Economics
Software Engineering Economics
How Software Process Improvement Helped Motorola
IEEE Software
Ethical Issues in Empirical Studies of Software Engineering
IEEE Transactions on Software Engineering
Writing good software engineering research papers: minitutorial
Proceedings of the 25th International Conference on Software Engineering
An Empirical Analysis of Productivity and Quality in Software Products
Management Science
Software development: processes and performance
IBM Systems Journal
A Survey of Controlled Experiments in Software Engineering
IEEE Transactions on Software Engineering
On the success of empirical studies in the international conference on software engineering
Proceedings of the 28th international conference on Software engineering
Editorial: For the Special issue on Qualitative Software Engineering Research
Information and Software Technology
Information and Software Technology
The Social Nature of Agile Teams
AGILE '07 Proceedings of the AGILE 2007
Investigating the use of "Grounded Theory" in information systems research
Proceedings of the 2008 annual research conference of the South African Institute of Computer Scientists and Information Technologists on IT research in developing countries: riding the wave of technology
CASCON '08 Proceedings of the 2008 conference of the center for advanced studies on collaborative research: meeting of minds
RESRES: The story behind the paper "Research in software engineering: An analysis of the literature"
Information and Software Technology
XP Customer Practices: A Grounded Theory
AGILE '09 Proceedings of the 2009 Agile Conference
Organizing self-organizing teams
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Test confessions: a study of testing practices for plug-in systems
Proceedings of the 34th International Conference on Software Engineering
An exploratory study of forces and frictions affecting large-scale model-driven development
MODELS'12 Proceedings of the 15th international conference on Model Driven Engineering Languages and Systems
Lessons learned from evaluating MDE abstractions in an industry field study
Proceedings of the Second Edition of the International Workshop on Experiences and Empirical Studies in Software Modelling
Journal of Systems and Software
Expectations, outcomes, and challenges of modern code review
Proceedings of the 2013 International Conference on Software Engineering
Evaluating usefulness of software metrics: an industrial experience report
Proceedings of the 2013 International Conference on Software Engineering
Classification of design decisions: an expert survey in practice
ECSA'13 Proceedings of the 7th European conference on Software Architecture
When agile meets the enterprise
Information and Software Technology
Hi-index | 0.00 |
Grounded Theory is a research method that generates theory from data and is useful for understanding how people resolve problems that are of concern to them. Although the method looks deceptively simple in concept, implementing Grounded Theory research can often be confusing in practice. Furthermore, despite many papers in the social science disciplines and nursing describing the use of Grounded Theory, there are very few examples and relevant guides for the software engineering researcher. This paper describes our experience using classical (i.e., Glaserian) Grounded Theory in a software engineering context and attempts to interpret the canons of classical Grounded Theory in a manner that is relevant to software engineers. We provide model to help the software engineering researchers interpret the often fuzzy definitions found in Grounded Theory texts and share our experience and lessons learned during our research. We summarize these lessons learned in a set of fifteen guidelines.