XP Customer Practices: A Grounded Theory

Martín, Àngela; Biddle, Robert; Noble, James

doi:10.1109/agile.2009.68

Cited by 30 publications

(35 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Such testing and evaluation activities can be internal and include developers that built the product, as well as external including beta users that agree to try the product for a limited period of time. Martin et al [14] support the idea of having internal evaluation with developers being the first "customers", and suggest a second step in which developers coach the customers for a couple of iterations. This way, the product use is observed by its' creators while in use by the customer.…”

Section: Customer Feedback Techniquesmentioning

confidence: 99%

“…Therefore, customers are not able to test the full product, and they might misinterpret the intention with the early version of the product. This might lead the customer to believe that the product is not developed as agreed [9], [14].…”

Section: Challenges and Limitationsmentioning

confidence: 99%

“…Additionally, and when having a prototype or an early version of a product, in-product surveys and web polls are important techniques for collecting feedback that helps in understanding the customer appreciation of a current and future products. Martin et al [14] also recommend customer pairing and customer 'boot camps' as one technique to not only collect feedback from one customer, but to have customers share this feedback with other customers with similar experiences.…”

Section: Customer Feedback Techniquesmentioning

confidence: 99%

See 2 more Smart Citations

Customer Feedback and Data Collection Techniques in Software R&D: A Literature Review

Fabijan

Olsson

Bosch

2015

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. In many companies, product management struggles in getting accurate customer feedback. Often, validation and confirmation of functionality with customers takes place only after the product has been deployed, and there are no mechanisms that help product managers to continuously learn from customers. Although there are techniques available for collecting customer feedback, these are typically not applied as part of a continuous feedback loop. As a result, the selection and prioritization of features becomes far from optimal, and product deviates from what the customers need. In this paper, we present a literature review of currently recognized techniques for collecting customer feedback. We develop a model in which we categorize the techniques according to their characteristics. The purpose of this literature review is to provide an overview of current software engineering research in this area and to better understand the different techniques that are used for collecting customer feedback.

show abstract

Section: Customer Feedback Techniquesmentioning

confidence: 99%

Section: Challenges and Limitationsmentioning

confidence: 99%

Section: Customer Feedback Techniquesmentioning

confidence: 99%

See 1 more Smart Citation

Customer Feedback and Data Collection Techniques in Software R&D: A Literature Review

Fabijan

Olsson

Bosch

2015

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

show abstract

“…Part of the problem is there are few good sources of information to help software engineers learn how to apply the Grounded Theory Method. Many of the leading text books on the topic, and especially those by Grounded Theory co-inventor Barney Glaser, can describe Grounded Theory in near mystical terms and there are only a few practical examples for a novice engineering Grounded Theory researcher to follow (Martin et al 2009;Seaman 1999;Whitworth and Biddle 2007;Hoda et al 2010). With few exceptions (Coleman and Conner 2007;Hughes and Jones 2004;Seaman 1999;Urqhart 2001), most scholarly treatments of Grounded Theory are from the disciplines of Nursing and Sociology (Annells 1996;Benoliel 1996;Dey 1999;Schreiber and Stern 2001).…”

mentioning

confidence: 98%

Using grounded theory to study the experience of software development

2011

View full text Add to dashboard Cite

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.

show abstract

“…One person, or in some instances a pair of people [13], were the identified contact point. It emerged that, like in DeMarco's analogy, the Negotiator 2 picked up the task of gaining agreement within the larger stakeholder community on the vision for the software.…”

Section: Negotiatormentioning

confidence: 99%