Listen
12 Ergebnisse
Bereich: Suchergebnisse
Publikation Benefits 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, PhilippeCard 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 KonferenzschriftPublikation Waste self-reporting for software development productivity improvement(Springer, 2023) Sallin, Marc; Kropp, Martin; Anslow, Craig; Biddle, Robert; Stettina, Christoph J.; Garbajosa, Juan; Kruchten, PhilippeLittle 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 KonferenzschriftPublikation Enhancing 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, Matthias04B - Beitrag KonferenzschriftPublikation Stress in Agile Software Development: Practices and Outcomes(Springer, 2018) Meier, Andreas; Kropp, Martin; Anslow, Craig; Biddle, Robert; Garbajosa, Juan; Wang, Xiaofeng; Aguiar, Ademar04B - Beitrag KonferenzschriftPublikation 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, PhilippeThe 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 KonferenzschriftPublikation Understanding 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, PhilippeIn 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 KonferenzschriftPublikation Satisfaction and its correlates in agile software development(Elsevier, 06/2020) Kropp, Martin; Meier, Andreas; Anslow, Craig; Biddle, RobertIn 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 ZeitschriftPublikation Satisfaction, Practices, and Influences in Agile Software Development(ACM, 2018) Kropp, Martin; Meier, Andreas; Anslow, Craig; Biddle, RobertThe 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 KonferenzschriftPublikation aWall: Agile Collaboration using Large Digital Multi-Touch Cardwalls(12/2016) Anslow, Craig; Burkhard, Roger; Kropp, Martin; Mateescu, Magdalena; Vischi, Dario; Zahn, CarmenDespite 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 ZeitungPublikation Automatisierung von Systemtests im industriellen Umfeld(12/2011) Kellner, Anja; Kropp, MartinContinuous Integration Umgebungen werden in der Regel im Software-Entwicklungszyklus für die kontinuierliche Integration der Software eingesetzt. In diesem Artikel zeigen wir, dass sich solche Systeme auch hervorragend für die Realisierung von automatisierten Testinfrastrukturen im industriellen Umfeld eignen. Im vorliegenden Anwendungsfall wird damit eine fast vollständig automatisierte System- und Akzeptanztestumgebung von Softwareprodukten zur Überwachung und Steuerung von Messtechnik-Sensoren erreicht.01B - Beitrag in Magazin oder Zeitung