Kropp, Martin
Lade...
E-Mail-Adresse
Geburtsdatum
Projekt
Organisationseinheiten
Berufsbeschreibung
Nachname
Kropp
Vorname
Martin
Name
Kropp, Martin
14 Ergebnisse
Suchergebnisse
Gerade angezeigt 1 - 10 von 14
- PublikationWaste self-reporting for software development productivity improvement(Springer, 2023) Sallin, Marc; Kropp, Martin; Anslow, Craig; Biddle, Robert; Stettina, Christoph J.; Garbajosa, Juan; Kruchten, Philippe [in: Agile processes in software engineering and extreme programming]Little research has been done on enabling software development teams to self-report waste to assist in productivity improvement. This study created a waste categorization and survey for teams to identify and quantify wasteful activities. Developers from a Swiss company used the survey for three weeks. Participants found the survey helpful for identifying waste but there was little evidence that self-reported waste correlated with improved performance.04B - Beitrag Konferenzschrift
- PublikationUnderstanding Leadership in Agile Software Development Teams: Who and How?(Springer, 09.06.2022) Weichbrodt, Johann; Kropp, Martin; Biddle, Robert; Gregory, Peggy; Anslow, Craig; Bühler, Ursina Maria; Mateescu, Magdalena; Meier, Andreas; Stray, Viktoria; Stol, Klaas-Jan; Paasivaara, Maria; Kruchten, Philippe [in: Agile Processes in Software Engineering and Extreme Programming. XP 2022]In this paper we report on a study of the nature of different aspects of leadership in agile teams. We used an established model of leadership, distinguishing transactional and transformational styles, and asked IT professionals a set of questions about the leadership they experience, both from direct supervisors (hierarchical leadership) and from the team itself (shared leadership). Our results show that agility is indeed related to the transformational style, but that the transactional style also plays a part, especially as shared leadership. Furthermore, even in highly agile software development, leadership by direct supervisors still plays an important role. We propose that, as software development becomes more agile, the transactional aspects of leadership may shift away from the leadership dyad between supervisor and employee into the agile team, while transformational leadership is important for both the team and supervisors.04B - Beitrag Konferenzschrift
- PublikationAgile Software Development: Practices, Self-Organization, and Satisfaction(Springer, 2021) Biddle, Robert; Kropp, Martin; Meier, Andreas; Anslow, Craig; Pfeiffer, Sabine; Nicklich, Manuel; Sauer, Stefan [in: The Agile Imperative]04A - Beitrag Sammelband
- PublikationSatisfaction 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
- PublikationSatisfaction and its correlates in agile software development(Elsevier, 2020) Kropp, Martin; Meier, Andreas; Anslow, Craig; Biddle, Robert [in: Journal of Systems and Software]01A - Beitrag in wissenschaftlicher Zeitschrift
- PublikationSources of satisfaction in agile software development(ACM, 2018) Kropp, Martin; Biddle, Robert; Meier, Andreas; Anslow, Craig [in: ACM/IEEE 40th International Conference on Software Engineering: Companion Proceedings (ICSE 2018)]In this paper we address the topic of satisfaction by analysis of the results of a national survey of software development in Switzerland. We found that satisfaction is reported more by those using Agile development than with plan-driven processes. We explored how satisfaction relates to oth-er elements in the development process, including the use of various practices, and the in!uences on business, team and software issues. We found that certain practices and in!uences have high correlations to satisfaction, and that collaborative processes are closely related to sat-isfaction, especially when combined with technical practices. Our intention in this analysis is principally descriptive, but we think the results are important to understand the challenges for everyone involved in Agile development, and can help in the transformation to Agile.04B - Beitrag Konferenzschrift
- PublikationStress 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
- PublikationStress in Agile Software Development: Practices and Outcomes(Springer, 2018) Kropp, Martin; Meier, Andreas; Anslow, Craig; Biddle, Robert; Garbajosa, Juan; Wang, Xiaofeng; Aguiar, Ademar [in: Agile Processes in Software Engineering and Extreme Programming: 19th International Conference, XP 2018]Stress is an important workplace issue, affecting both the health of individuals, and the health of organizations. Early advocacy for Agile Software Development suggested it might help avoid stress, with practices that emphasize a sustainable pace, and self-organizing teams. Our analysis of a 2014 survey, however, suggested that stress might still be commonplace in Agile teams, especially for those with less experience. We also noticed that newcomers to Agile emphasized technical, rather than collaborative, practices, and speculated this might explain the stress. We explored this in our analysis of a follow-up survey conducted in 2016, and report our findings in this paper. We show that there are a variety of factors involved, and that avoiding stress is associated with both collaborative and technical practices, and a range of outcomes.04B - Beitrag Konferenzschrift
- PublikationMyagile: sociological and cultural effects of agile on teams and their members(ACM, 2018) Biddle, Robert; Meier, Andreas; Kropp, Martin; Anslow, Craig [in: ACM/IEEE 11th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE 2018)]04B - Beitrag Konferenzschrift
- PublikationSatisfaction, Practices, and Influences in Agile Software Development(ACM, 2018) Kropp, Martin; Meier, Andreas; Anslow, Craig; Biddle, Robert [in: EASE 2018 - 22nd International Conference on Evaluation and Assessment in Software Engineering]The principles behind the Agile Manifesto begin with "Our highest priority is to satisfy the customer...". It also states that Agile projects should be build around motivated and self-organized teams, which might also lead to more satisfied developers. Several studies indeed report an increased job satisfaction by anecdotal evidence. In this paper we address the topic of satisfaction by in-depth analysis of the results of a nationwide survey about software development in Switzerland. We wanted to find out if satisfaction depends on the applied development method, and, more concrete, how satisfaction relates to other elements in the development process, including the use of various practices, and the influences on business, team and software issues.04B - Beitrag Konferenzschrift