SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "WFRF:(Gren Lucas 1984) srt2:(2020)"

Sökning: WFRF:(Gren Lucas 1984) > (2020)

  • Resultat 1-7 av 7
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  • Gren, Lucas, 1984 (författare)
  • A Flipped Classroom Approach to Teaching Empirical Software Engineering
  • 2020
  • Ingår i: IEEE Transactions on Education. - 0018-9359 .- 1557-9638. ; 63:3
  • Tidskriftsartikel (refereegranskat)abstract
    • Contribution: A flipped classroom approach to teaching empirical software engineering increases student learning by providing more time for active learning in class. Background: There is a need for longitudinal studies of the flipped classroom approach in general. Although a few cross-sectional studies show that a flipped classroom approach can increase student learning by providing more time for other in-class activities, such as active learning, such studies are also rare in the context of teaching software engineering. Intended Outcomes: To assess the usefulness of a flipped classroom approach in teaching software engineering. Application Design: The study was conducted at an international master's program in Sweden, given in English, and partially replicated at a university in Africa. Findings: The results suggest that students' academic success, as measured by their exam grades, can be improved by introducing a flipped classroom to teach software engineering topics, but this may not extend to their subjective liking of the material, as measured by student evaluations. Furthermore, the effect of the change in the teaching methodology was not replicated when changing the teaching team. IEEE
  •  
2.
  • Gren, Lucas, 1984, et al. (författare)
  • Agile ways of working: A team maturity perspective
  • 2020
  • Ingår i: Journal of Software: Evolution and Process. - : Wiley. - 2047-7481 .- 2047-7473 .- 1532-060X. ; 32:6
  • Tidskriftsartikel (refereegranskat)abstract
    • With the agile approach to managing software development projects comes an increased dependability on well-functioning teams, since many of the practices are built on teamwork. The objective of this study was to investigate if, and how, team development from a group psychological perspective is related to some work practices of agile teams. Data were collected from 34 agile teams (200 individuals) from six software development organizations and one university in both Brazil and Sweden using the Group Development Questionnaire (Scale IV) and the Perceptive Agile Measurement (PAM). The result indicates a strong correlation between levels of group maturity and the two agile practices iterative development and retrospectives. We, therefore, conclude that agile teams at different group development stages adopt parts of team agility differently, thus confirming previous studies but with more data and by investigating concrete and applied agile practices. We thereby add evidence to the hypothesis that an agile implementation and management of agile projects need to be adapted to the group maturity levels of the agile teams.
  •  
3.
  • Gren, Lucas, 1984, et al. (författare)
  • Agility is responsiveness to change: An essential definition
  • 2020
  • Ingår i: 24th Conference on Evaluation and Assessment in Software Engineering (EASE2020). - New York, NY, USA : Association for Computing Machinery. - 2153-1633.
  • Konferensbidrag (refereegranskat)abstract
    • There is some ambiguity of what agile means in both research and practice. Authors have suggested a diversity of different definitions, through which it is difficult to interpret what agile really is. The concept, however, exists in its implementation through agile practices. In this vision paper, we argue that adopting an agile approach boils down to being more responsive to change. To support this claim, we relate agile principles, practices, the agile manifesto, and our own experiences to this core definition. We envision that agile transformations would be, and are, much easier using this definition and contextualizing its implications.
  •  
4.
  • Gren, Lucas, 1984, et al. (författare)
  • Group-Development Psychology Training: The Perceived Effects on Agile Software-Development Teams
  • 2020
  • Ingår i: IEEE Software. - 1937-4194 .- 0740-7459. ; 37:3, s. 63-69
  • Tidskriftsartikel (refereegranskat)abstract
    • Research has shown that the maturity of small workgroups, from a psychological perspective, is intimately connected to team agility. This study showed a perceived positive effect of training agile teams in group developmental psychology. We therefore see huge potential in training agile teams in this topic since the positive effects might span over the entire software development organization.
  •  
5.
  • Gren, Lucas, 1984 (författare)
  • Understanding work practices of autonomous agile teams: A social-psychological review
  • 2020
  • Ingår i: Agile Processes in Software Engineering and Extreme Programming – Workshops. XP 2020. Lecture Notes in Business Information Processing. - Cham : Springer, Cham. - 1865-1348 .- 1865-1356. - 9783030588571
  • Konferensbidrag (refereegranskat)abstract
    • The purpose of this paper is to suggest additional aspects of social psychology that could help when making sense of autonomous agile teams. To make use of well-tested theories in social psychology and instead see how they replicated and differ in the autonomous agile team context would avoid reinventing the wheel. This was done, as an initial step, through looking at some very common agile practices and relate them to existing findings in social-psychological research. The two theories found that I argue could be more applied to the software engineering context are social identity theory and group socialization theory. The results show that literature provides social-psychological reasons for the popularity of some agile practices, but that scientific studies are needed to gather empirical evidence on these under-researched topics. Understanding deeper psychological theories could provide a better understanding of the psychological processes when building autonomous agile team, which could then lead to better predictability and intervention in relation to human factors.
  •  
6.
  • Gren, Lucas, 1984, et al. (författare)
  • What an Agile Leader Does: The Group Dynamics Perspective
  • 2020
  • Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer International Publishing. - 1865-1356 .- 1865-1348. - 9783030493912 ; 383 LNBIP, s. 178-194
  • Konferensbidrag (refereegranskat)abstract
    • When large industrial organizations change to (or start with) an agile approach to operations, managers and some employees are supposed to be “agile leaders” often without being given a clear definition of what that comprises when building agile teams. An inductive thematic analysis was used to investigate what 15 appointed leaders actually do and perceive as challenges regarding group dynamics working with an agile approach. Team maturity, Team design, and Culture and mindset were all categories of challenges related to group dynamics that the practitioners face and manage in their work-life that are not explicitly mentioned in the more process-focused agile transformation frameworks. The results suggest that leader mitigation of these three aspects of group dynamics is essential to the success of an agile transformation.
  •  
7.
  • Lenberg, Per, 1976, et al. (författare)
  • Behavioral Aspects of Safety-Critical Software Development
  • 2020
  • Ingår i: Proceedings - 2020 IEEE/ACM 42nd International Conference on Software Engineering Workshops, ICSEW 2020. - New York, NY, USA : ACM. ; , s. 173-176
  • Konferensbidrag (refereegranskat)abstract
    • We are becoming increasingly dependent on software systems also for highly critical tasks in society. To minimize the risk of failures, regulatory institutions define standards that software organizations must meet. However, the quality of the safety-critical software is, ultimately, determined by the software engineers' behavior. Even though previous studies have recognized the significance of such behavioral aspects, research that studies them is limited. The aim of this initial study was, therefore, to identify how and in what way, behavioral aspects affect the quality of safety-critical software. Thematic analysis of interviews with six software engineers identified four themes linking developer behavior to safety. Our analysis suggests that developing safety-critical systems imposes stress on software engineers and that to reduce such pressure it is critical to enhance organizational trust. It also indicates that the agile way-of-working has the potential to improve safety by facilitating the sharing of domain knowledge. Our findings provide directions for future studies into these important aspects and can be of wider relevance, in particular for the development of secure software, but potentially also for general software engineering.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-7 av 7

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Stäng

Kopiera och spara länken för att återkomma till aktuell vy