Kropp, Martin
Lade...
E-Mail-Adresse
Geburtsdatum
Projekt
Organisationseinheiten
Berufsbeschreibung
Nachname
Kropp
Vorname
Martin
Name
Kropp, Martin
35 Ergebnisse
Suchergebnisse
Gerade angezeigt 1 - 10 von 35
- PublikationMaintenance and evolution of large scale software systems – Business, dev & ops challenges(10.02.2023) Rüegger, Janick; Kropp, MartinEven in the time of agile software development and devOps, maintenance and evolution of large-scale software systems remain challenging. This is not only caused by technical debt, but is heavily caused by lost knowledge, high complexity of micro-service architectures, difficult requirements management, not available documentation, and the complexity of communication among and coordination of the many stakeholders. In our session we will talk about the challenges we identified in our study and present new approaches to address these challenges.06 - Präsentation
- 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
- PublikationBenefits of card walls in agile software development. A systematic literature review(Springer, 2022) Sallin, Marc; Kropp, Martin; Stray, Viktoria; Stol, Klaas-Jan; Paasivaara, Maria; Kruchten, Philippe [in: Agile processes in software engineering and extreme programming]Card walls are often used to visualize various aspects of the software development process. They are an essential and widespread agile practice. Despite the drawback of physical card walls, its digital version is often not considered a sufficient alternative. This paper aims to find the reason for this and suggests how to evolve digital card walls into a viable alternative. We conducted a systematic literature review and analyzed twenty-two studies. We identified which desirable effects agile teams get from card wall usage and derived a set of properties a card wall needs to achieve those effects. Furthermore, we suggested a typology of card walls to compare the benefits and challenges among them.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
- PublikationThe Effects on social support and work engagement with scrum events(IEEE, 2021) Müller, Debora; Kropp, Martin; Anslow, Craig; Meier, Andreas [in: 2021 IEEE/ACM 13th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)]One of the core values of the Agile Manifesto is “individuals and interactions over processes and tools.” Scrum implements interaction through key events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Retrospective). There is limited work done on how these events influence perceived social support and work engagement. This paper examines perceived social support as a strengthening factor on work engagement in an agile work environment. Drawing upon the Job Demands-Resource Model, the research question is how do Scrum events relate to social support and what effect do they have on work engagement? We conducted an online survey with 132 Scrum professionals and analyzed the data using structural equation modelling. Results show that the Scrum event Retrospective strengthened social support. Moreover, social support is positively related to work engagement. The research contributes to the limited empirical understanding on perceived social support as well as work engagement in an agile work environment. It provides companies with an understanding of the importance of Retrospectives as a Scrum event.04B - Beitrag Konferenzschrift
- PublikationMeasuring 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
- 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
- PublikationVisualizing progress tracking for software teams on large collaborative touch displays(IEEE, 2020) Scott-Hill, Brandon; Anslow, Craig; Ferreira, Jennifer; Kropp, Martin; Mateescu, Magdalena; Meier, Andreas [in: 2020 IEEE Symposium on Visual Languages and Human-Centric Computing (VL/HCC)]04B - Beitrag Konferenzschrift
- 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