Kropp, Martin
E-Mail-Adresse
Geburtsdatum
Suchergebnisse
Enhancing Agile Team Collaboration Through the Use of Large Digital Multi-touch Cardwalls
Sources of satisfaction in agile software development
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.
Stress in Agile Software Development: Practices and Outcomes
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.
Satisfaction, Practices, and Influences in Agile Software Development
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.
Use of Gamification to Teach Agile Values and Collaboration: A multi-week Scrum simulation project in an undergraduate software engineering course
Collaboration and communication are key to successful agile software development. Respect, openness, transparency and trust are core Agile values. However studies show, that there is a shortage of software developers with these skills. How can we teach these skills to software engineering students' This paper presents the approach of using a multi-week Scrum Paper City simulation game. The course execution was accompanied by a thorough evaluation to find out how effective this approach is compared to traditional ex-cathedra teaching. While the evaluation shows some aspects to be improved, it clearly shows that students like to experience the Agile approach directly in a project, that they enjoy more fun, and the collaboration in the team.