Kropp, Martin
Lade...
E-Mail-Adresse
Geburtsdatum
Projekt
Organisationseinheiten
Berufsbeschreibung
Nachname
Kropp
Vorname
Martin
Name
Kropp, Martin
11 Ergebnisse
Suchergebnisse
Gerade angezeigt 1 - 10 von 11
- 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
- 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
- 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
- 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
- PublikationEnhancing agile team collaboration through the use of large digital multi-touch cardwalls(Springer, 2017) Kropp, Martin; Anslow, Craig; Mateescu, Magdalena; Burkhard, Roger; Vischi, Dario; Zahn, Carmen; Baumeister, Hubert; Lichter, Horst; Riebisch, Matthias [in: Agile Processes in Software Engineering and Extreme Programming]04B - Beitrag Konferenzschrift
- PublikationaWall: Agile Collaboration using Large Digital Multi-Touch Cardwalls(12/2016) Anslow, Craig; Burkhard, Roger; Kropp, Martin; Mateescu, Magdalena; Vischi, Dario; Zahn, Carmen [in: IMVS Fokus Report]Despite the availability of many digital agile board tools, most co-located agile software teams still use physical cardboards for their daily standup meetings. This is due to the fact that existing digital agile boards lacks supporting a collaborative workspace, direct interaction for the whole team in meetings, or making project information directly visible. In this paper we present aWall, a digital agile cardwall designed for the highly collaborative agile work style using large multi-touch wall displays. The effectiveness of aWall was evaluated in a user study with eleven software practitioners. Our findings indicate that aWall enables and encourages team work due to the large size of the wall, accessibility and visibility of large amounts of information, and possibility of customization of the interface. Based on this work, we suggest that augmenting digital cardwalls with large interactive touch technology and new interaction concepts is a useful way to support effective collaborative agile software development processes.01B - Beitrag in Magazin oder Zeitung
- PublikationQualitative 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
- PublikationTeaching Agile Software Development at University Level(12/2013) Kropp, Martin; Meier, Andreas [in: IMVS Fokus Report]Several recent surveys show that agile methodologies like Scrum, Extreme Programming and Kanban have been successfully adopted by many companies for software development. However, the same surveys show that only few of the agile practices are applied consequently and thoroughly. This is to a great extent due to the lack of skilled personnel. In this paper we propose a more holistic approach for teaching agile software development, in which the required agile practices and values are not only integrated theoretically into our courses but also practically applied. The proposed concept was realized in a new a course at Zurich University of Applied Sciences during 2012. The evaluation shows very encouraging results.01B - Beitrag in Magazin oder Zeitung