Using grounded theory to study the experience of software development

Adolph, Steve; Hall, Wendy A.; Kruchten, Philippe

doi:10.1007/s10664-010-9152-6

Cited by 186 publications

(141 citation statements)

References 35 publications

(24 reference statements)

Supporting

Mentioning

141

Contrasting

Order By: Relevance

“…We used constant comparison for data analysis, which is a systematic way to identify concepts in the data by comparing identified concepts to previous observations [16]. All interviews and the collected documentation were intensively studied and coded.…”

Section: Discussionmentioning

confidence: 99%

See 1 more Smart Citation

Industrial Implementation of a Documentation Framework for Architectural Decisions

Manteuffel

Tofan

Koziolek³

et al. 2014

2014 IEEE/IFIP Conference on Software Architecture

View full text Add to dashboard Cite

Abstract-Architecture decisions are often not explicitly documented in practice but reside in the architect's mind as tacit knowledge, even though explicit capturing and documentation of architecture decisions has been associated with a multitude of benefits. As part of a research collaboration with ABB, we developed a tool to document architecture decisions. This tool is an add-in for Enterprise Architect and is an implementation of a viewpoint-based decision documentation framework. To validate the add-in, we conducted an exploratory case study with ABB architects. In the study, we assessed the status quo of architecture decision documentation, identified architects' expectations of the ideal decision documentation tool, and evaluated the new add-in. We found that although awareness of decision documentation is increasing at ABB, several barriers exist that limit the use of decisions in practice. Regarding their ideal tool, architects want a descriptive and efficient approach. Supplemental features like reporting or decision sharing are requested. The new add-in, was well-perceived by the architects. As a result of the study, we propose a clearer separation of problem, outcomes, and alternatives for the decision documentation framework.

show abstract

Section: Discussionmentioning

confidence: 99%

“…Responses of the participant that were related to one of the research questions were labeled. During the coding and constant comparison the researcher gets a better understanding of the data he is looking at [16]. The identified codes were grouped into related higher level concepts.…”

Section: Discussionmentioning

confidence: 99%

Industrial Implementation of a Documentation Framework for Architectural Decisions

Manteuffel

Tofan

Koziolek³

et al. 2014

2014 IEEE/IFIP Conference on Software Architecture

View full text Add to dashboard Cite

show abstract

“…The first phase (Case Study A) comprised a multiple case study of 53 practitioners from two multinational companies; employing a Glaserian grounded theory analysis of documentary sources, practice observations and interview transcripts [2,16]. Requires objective measurement, and as such is independent of location -however making sure that rewards are given to each employee fairly across different locations may not be achievable, e.g.…”

Section: Methodsmentioning

confidence: 99%

Employee retention and turnover in global software development

Bass

Beecham²,

Razzak³

et al. 2018

Proceedings of the 13th International Conference on Global Software Engineering

View full text Add to dashboard Cite

Poor employee retention (high staff turnover) has a negative impact on software development productivity and product quality. Further, offshore outsourcing has a widely held reputation for particularly poor employee retention. Interestingly, in-house sites (regardless of location) do not suffer such high levels of staff turnover.We want to understand the factors affecting employee retention in-house and offshore outsourced settings, to better understand the potential impact of staff turnover on global software development.The research employed a mixed-method approach comprising two empirical case studies in industry involving 62 practitioners at three international companies conducting in-house and offshore outsourced software development. We collected practitioner perceptions of causal factors for employee retention and performed a cross-case analysis to triangulate our findings.Practitioners cited employment policies, work-life balance, workplace innovation, product quality, alignment of offshore work hours with onshore, long working hours and adverse impact on health as factors affecting staff retention. In-house offshore have more family friendly employment policies. In the outsourcing sector, the focus on customer satisfaction sometimes leads to less attractive work patterns.Offshore outsourcing service providers could improve development team member retention by improving work-life balance and adopting more family friendly employment policies.Permission to make digital or hard copies of part or all of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for third-party components of this work must be honored. For all other uses, contact the owner/author(s CCS CONCEPTS• Software and its engineering → Software creation and management; Software development process management; Collaboration in software development;

show abstract

“…Grounded Theory is able to generate theories that are relevant to practitioners [15] and that are 'grounded in data' [12].…”

Section: Grounded Theorymentioning

confidence: 99%

An exploratory study on ontology engineering for software architecture documentation

Graaf¹,

Liang

Tang

et al. 2014

Computers in Industry

View full text Add to dashboard Cite

Architectural Knowledge (AK) can be retrieved by the stakeholders in a software project.Recent findings show that the use of ontology-based SA documentation is promising. However, different roles in software development have different needs for AK, and building an ontology to suit these needs is challenging. In this paper we describe an approach to build an ontology for SA documentation. This approach involves the use of typical questions for eliciting and constructing an ontology. We outline eight contextual factors, which influence the successful construction of an ontology, especially in complex software projects with diverse AK users. We tested our 'typical question' approach in a case study and report how it can be used for acquiring and modeling AK needs.

show abstract

Using grounded theory to study the experience of software development

Cited by 186 publications

References 35 publications

Industrial Implementation of a Documentation Framework for Architectural Decisions

Industrial Implementation of a Documentation Framework for Architectural Decisions

Employee retention and turnover in global software development

An exploratory study on ontology engineering for software architecture documentation

Contact Info

Product

Resources

About