Sampling for qualitative research

Marshall, Martin

doi:10.1093/fampra/13.6.522

Cited by 2,775 publications

(1,956 citation statements)

References 4 publications

Supporting

Mentioning

1,840

Contrasting

Unclassified

Order By: Relevance

“…We discussed the codes collaboratively and repeatedly. We concluded the study after reaching the point of theoretical saturation, when categories, themes, and explanations repeated from the data (Marshall, 1996). A second researcher independently coded four sample interviews transcripts.…”

Section: Data Analysis Proceduresmentioning

confidence: 99%

The appropriation of GitHub for curation

Wang

Kropczynski

et al. 2017

PeerJ Computer Science

View full text Add to dashboard Cite

GitHub is a widely used online collaborative software development environment. In this paper, we describe curation projects as a new category of GitHub project that collects, evaluates, and preserves resources for software developers. We investigate:(1) what motivates software developers to curate resources; (2) why curation has occurred on GitHub; (3) how curated resources are used by software developers; and (4) how the GitHub platform could better support these practices. We conduct indepth interviews with 16 software developers, each of whom hosts curation projects on GitHub. Our results suggest that the motivators that inspire software developers to curate resources on GitHub are similar to those that motivate them to participate in the development of open source projects. Convenient tools (e.g., Markdown syntax and Git version control system) and the opportunity to address professional needs of a large number of peers attract developers to engage in curation projects on GitHub. Benefits of curating on GitHub include learning opportunities, support for development work, and professional interaction. However, curation is limited by GitHub's document structure, format, and a lack of key features, such as search. In light of this, we propose design possibilities to encourage and improve appropriations of GitHub for curation.Subjects Human-Computer Interaction, Software Engineering

show abstract

Section: Data Analysis Proceduresmentioning

confidence: 99%

The appropriation of GitHub for curation

Wang

Kropczynski

et al. 2017

PeerJ Computer Science

View full text Add to dashboard Cite

show abstract

“…The study employed purposeful sampling, whereby the case was selected on the knowledge, experience and information that could be provided (Marshall, 1996). It was important to select an organisation that was involved in GSD and thus employed a GSD team setup, and also used Kanban as a methodology for their software projects.…”

Section: Samplingmentioning

confidence: 99%

“…It was important to select an organisation that was involved in GSD and thus employed a GSD team setup, and also used Kanban as a methodology for their software projects. Convenience sampling was also applied because the study was dependent on the willingness and availability of the participants (Marshall, 1996). Forums, meetups, search engines, as well as virtual communities that shared information about software development and project management were reviewed.…”

Section: Samplingmentioning

confidence: 99%

The Use of Kanban to Alleviate Collaboration and Communication Challenges of Global Software Development

Tanner¹,

Dauane²

2017

InSITE Conference

View full text Add to dashboard Cite

[This Proceedings paper was revised and published in the journal Issues in Informing Science and Information Technology] Aim/Purpose : This paper aims to describe how various Kanban elements can help alleviate two prominent types of challenges, communication and collaboration in Global Software Development (GSD). Background: Iterative and Lean development methodologies like Kanban have gained significance in the software development industry, both in the co-located and globally distributed contexts. However, little is known on how such methodologies can help mitigate various challenges in that occur in a globally distributed software development context. Methodology: The study was conducted using a single-case study based on a general inductive approach to analysis and theory development. Through the literature review, collaboration and communication challenges that GSD teams face were identified. Data collected through semi-structured interviews was then inductively analyzed to describe how the case-study teams employed various Kanban elements to mitigate communication and collaboration challenges they face during GSD. Findings: The study found that some Kanban elements, when properly employed, can help alleviate collaboration and communication challenges that occur within GSD teams. These relate to Inclusion Criteria, Reverse Items, Kanban Board, Policies, Avatars, and Backlog. Contribution: The paper contributes to knowledge by proposing two simple concept maps that detail the specific types of communication and collaboration challenges which can be alleviated by the aforementioned Kanban elements in GSD. Recommendations for Practitioners: This paper is relevant to GSD teams who are seeking ways to enhance their team collaboration and communication as these are the most important elements that contribute to GSD project success. It is recommended that relevant Kanban elements be used to that effect, depending on the challenges that they aim to alleviate. Future Research: Future research can investigate the same research questions (or similar ones) using a quantitative approach.

show abstract

“…Opportunity sampling is a form of non-probability sampling, which involves the sample being drawn from a population that is convenient to the investigator (Marshall, 1996). Although very suited to obtaining a homogeneous sample, which is suitable for IPA, it does have the drawback that the findings from such a sample may be less transferable to the wider population.…”

Section: Sampling and Recruitmentmentioning

confidence: 99%