Logo des Repositoriums

Auflistung nach Schlagwort "grounded theory"

1 - 2 von 2
  • Konferenzbeitrag
    Observations on Knowledge Transfer of Professional Software Developers during Pair Programming
    (Software Engineering und Software Management 2018, 2018) Zieris, Franz; Prechelt, Lutz
    This work was presented at the 38th International Conference on Software Engineering (2016). Context: Software development is knowledge-intense work, and so is pair programming. However, the importance of knowledge transfer in pair programming is usually only stressed for expert-novice constellations and not for general software development situations. Goal: Understand how pair programmers deal with their knowledge deficits and eventually provide guidance for practitioners. Method: Detailed qualitative data analysis of full-length recordings of industrial pair programming sessions. Results: Expert software developers need to transfer knowledge, too, in order to conduct productive pair programming sessions. There is a diversity of beneficial and potentially problematic patterns, which even good pairs do not steadily apply or avoid, respectively. Conclusions: Pair programming is a versatile practice that even experts can profit from. Knowledge transfer skills do not automatically emerge from good software development skills, but can probably be learned.
  • Konferenzbeitrag
    Quality Experience
    (Software Engineering und Software Management 2018, 2018) Prechelt, Lutz; Schmeisky, Holger; Zieris, Franz
    This work was presented at the 38th International Conference on Software Engineering (2016). Context: While successful conventional software development regularly employs separate testing staff, there are successful agile teams with as well as without separate testers. Question: How does successful agile development work without separate testers? What are advantages and disadvantages? Method: A case study, based on Grounded Theory evaluation of interviews and direct observation of three agile teams; one having separate testers, two without. All teams perform long-term development of parts of e-business web portals. Results: Teams without testers use a "quality experience" work mode centered around a tight field-use feedback loop, driven by a feeling of responsibility, supported by test automation, resulting in frequent deployments. Conclusion: In the given domain, hand-overs to separate testers appear to hamper the feedback loop more than they contribute to quality, so working without testers is preferred. However, Quality Experience is achievable only with modular architectures and in suitable domains.