Kropp, Martin

Profilbild
E-Mail-Adresse
Geburtsdatum
Projekt
Organisationseinheiten
Berufsbeschreibung
Nachname
Kropp
Vorname
Martin
Name
Kropp, Martin

Filter

2014 - 201922020 - 20212
Filter zurücksetzen

Einstellungen

Autor:in: Meier, Andreas × Anfangsdatum: 2010 × Dateien dazu vorhanden?: Ja × Institut: Institut für Mobile und Verteilte Systeme × Thema: 005 - Computer Programmierung, Programme und Daten ×

Suchergebnisse

Gerade angezeigt 1 - 4 von 4
  • Vorschaubild
    Publikation
    Measuring Software Delivery Performance Using the Four Key Metrics of DevOps
    (Springer, 2021) Sallin, Marc; Kropp, Martin; Anslow, Craig; Quilty, James W.; Meier, Andreas; Gregory, Peggy; Lassenius, Casper; Wang, Xiaofeng; Kruchten, Philippe [in: Agile Processes in Software Engineering and Extreme Programming]
    The Four Key Metrics of DevOps have become very popular for measuring IT-performance and DevOps adoption. However, the measurement of the four metrics deployment frequency, lead time for change, time to restore service and change failure rate is often done manually and through surveys - with only few data points. In this work we evaluated how the Four Key Metrics can be measured automatically and developed a prototype for the automatic measurement of the Four Key Metrics. We then evaluated if the measurement is valuable for practitioners in a company. The analysis shows that the chosen measurement approach is both suitable and the results valuable for the team with respect to measuring and improving the software delivery performance.
    04B - Beitrag Konferenzschrift
  • Vorschaubild
    Publikation
    Satisfaction and its correlates in agile software development
    (Elsevier, 06/2020) Kropp, Martin; Meier, Andreas; Anslow, Craig; Biddle, Robert [in: Journal of Systems and Software]
    In this paper we address the topic of software development team members satisfaction with their development process. We present an in-depth analysis of the results of a nationwide survey about software development in Switzerland. We wanted to find out if satisfaction relates to the applied development method, and to the use of various practices, and impacts on business, team and software issues. We found that higher satisfaction is reported more by those using Agile development than with plan-driven processes. We explored the different perspectives of developers and those with a management role and found a high consistency of satisfaction between Agile developers and Agile management, and differences with those using working plan-driven methods. We found that certain practices and impacts have high correlations to satisfaction, and that collaborative processes are closely related to satisfaction. We then explored the relationship between satisfaction and various other perspectives. Our results in this analysis are principally descriptive, but we think they can be a relevant contribution to understand the challenges for everyone involved in Agile development.
    01A - Beitrag in wissenschaftlicher Zeitschrift
  • Vorschaubild
    Publikation
    Stress in Agile Software Development: Practices and Outcomes
    (Springer, 2018) Meier, Andreas; Kropp, Martin; Anslow, Craig; Biddle, Robert; Garbajosa, Juan; Wang, Xiaofeng; Aguiar, Ademar [in: Agile Processes in Software Engineering and Extreme Programming]
    04B - Beitrag Konferenzschrift
  • Vorschaubild
    Publikation
    Qualitative Study of Successful Agile Software Development Projects
    (12/2014) Kropp, Martin; Meier, Andreas [in: IMVS Fokus Report]
    Various studies show that the agile method has become a mainstream methodology for software development. When agile pioneers introduced this approach, they executed very successful projects which lead to the enormous popularity of agile development. With becoming mainstream, less experienced teams started to apply the agile approaches and news about failed agile projects appeared. This raises the question, what it needs to conduct successful agile projects. In a qualitative study we asked IT companies about the essential success factors in their successful agile projects. We found that there was a strong focus on engineering and management best practices. We found that when these practices did not work, mature teams sensed that following a recipe is not sufficient, and they started adapting the agile process to their needs. Applying a sense-making methodology like the Cynefin framework, theoretically explains our observations in the study.
    01B - Beitrag in Magazin oder Zeitung