| 1. |
- Al Sabbagh, Khaled, 1987, et al.
(författare)
-
The connections between group maturity, software development velocity, and planning effectiveness
- 2018
-
Ingår i: Journal of Software-Evolution and Process. - : Wiley. - 2047-7473 .- 2047-7481. ; 30:1
-
Tidskriftsartikel (refereegranskat)abstract
- Empirical evidence regarding the connection between group development (maturity) and the success of software development teams is lacking. The purpose of this research is to gain a qualitative and quantitative understanding of how velocity and planning effectiveness of software teams connect to a group development model. The Group Development Questionnaire was given to 19 software developers from 4 work groups to assess their group development maturity. The work groups' responses to the survey were checked for correlation with development velocity and planning effectiveness. Semistructured interviews were conducted with 16 individuals from the same 4 work groups to explore issues about their group maturity and to validate the responses of the interviewees in the Group Development Questionnaire. The measurement of the fourth stage of group development had a strong association with the planning effectiveness measurement, which means that a team with less issues in the fourth phase of group development is more effective in adhering to its plans. On the other hand, group development and velocity showed no significant convergent validity. We conclude that the dynamics within software development teams might correlate to their ability to deliver the expected outcome as planned but not to their ability to develop tasks faster.
|
|
| 2. |
- Berntsson Svensson, Richard, 1978, et al.
(författare)
-
Creativity Techniques for More Creative Requirements: Theory vs. Practice
- 2015
-
Ingår i: EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA 2015), August 26-28. - : IEEE. - 9781467375856
-
Konferensbidrag (refereegranskat)abstract
- Requirements engineering was initially regarded as a front-end activity to form a basis for the coming activities of software development, which can be achieved by gathering and producing unambiguous and consistent requirements. However, in recent years, requirements engineering has been recognized as a creative process. A systematic literature review followed by an online questionnaire with practitioners were employed to identify a comprehensive overview of existing empirical evidence using creativity techniques in the requirements engineering process. The results show a limited range of applied creativity techniques with insufficient empirical evidence to adequately evaluate if the techniques create more creative requirements. The contribution of this study is threefold: First, it compares which creativity techniques have been empirically evaluated in literature. Second, it compares the identified creativity techniques. Third, it includes an examination of which creativity techniques are used in industry.
|
|
| 3. |
- Bäckevik, Andreas, et al.
(författare)
-
Social Identity in Software Development
- 2019
-
Ingår i: 2019 IEEE/ACM 12th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE). - : IEEE/ACM. - 2574-1780 .- 2574-1837. - 9781728122403
-
Konferensbidrag (refereegranskat)abstract
- An agile approach has become very popular over the last decade, which requires good communication and teamwork within teams as well as with outside stakeholders. Therefore, social interaction is central for a software development team to be successful. Such social interactions form social identities and social structures in both teams and organizations. This study investigates possible effects that the social identity of individuals may have on the effectiveness of software development through seven in-dept interviews. The qualitative data from interviews were analyzed and summarized using summative content analysis, and the seven individuals also answered a questionnaire on social identity taken from social psychology research. The qualitative result shows that aspects of social identity affect software developers' behavior, and that we need to build cross-functional stable teams over time also from a pure social identity perspective in addition to the product related aspects to avoid a decreased effectiveness. However, we did not see clear connections to our operationalization of effectiveness in this study, and the quantitative analysis was also inconclusive, but we see value in our suggested method when investigating social identity in software development.
|
|
| 4. |
- Chronis, Konstantinos, et al.
(författare)
-
Agility Measurements Mismatch: A Validation Study on Three Agile Team Assessments in Software Engineering
- 2016
-
Ingår i: Proceedings of the 17th International Conference on Agile Software Development (XP2016). - Cham : Springer International Publishing. - 1865-1348 .- 1865-1356. - 9783319335148
-
Konferensbidrag (refereegranskat)abstract
- Many tools have been created for measuring the agility of software teams, thus creating a saturation in the field. Three agile measurement tools were selected in order to validate whether they yield similar results. The surveys of the tools were given to teams in Company A (N=30). The questions were grouped into agile practices which were checked for correlation in order to establish convergent validity. In addition, we checked whether the questions identified to be the same among the tools would be given the same replies by the respondents. We could not establish convergent validity since the correlations of the data gathered were very few and low. In addition, the questions which were identified to have the same meaning among the tools did not have the same answers from the respondents. We conclude that the area of measuring agility is still immature and more work needs to be done. Not all tools are applicable to every team but they should be selected on the basis of how a team has transitioned to agile.
|
|
| 5. |
- Gomes, Francisco, 1987, et al.
(författare)
-
Evolution of statistical analysis in empirical software engineering research : Current state and steps forward
- 2019
-
Ingår i: Journal of Systems and Software. - : Elsevier Inc.. - 0164-1212 .- 1873-1228. ; 156, s. 246-267
-
Tidskriftsartikel (refereegranskat)abstract
- Software engineering research is evolving and papers are increasingly based on empirical data from a multitude of sources, using statistical tests to determine if and to what degree empirical evidence supports their hypotheses. To investigate the practices and trends of statistical analysis in empirical software engineering (ESE), this paper presents a review of a large pool of papers from top-ranked software engineering journals. First, we manually reviewed 161 papers and in the second phase of our method, we conducted a more extensive semi-automatic classification of papers spanning the years 2001–2015 and 5196 papers. Results from both review steps was used to: i) identify and analyse the predominant practices in ESE (e.g., using t-test or ANOVA), as well as relevant trends in usage of specific statistical methods (e.g., nonparametric tests and effect size measures) and, ii) develop a conceptual model for a statistical analysis workflow with suggestions on how to apply different statistical methods as well as guidelines to avoid pitfalls. Lastly, we confirm existing claims that current ESE practices lack a standard to report practical significance of results. We illustrate how practical significance can be discussed in terms of both the statistical analysis and in the practitioner's context. © 2019 Elsevier Inc.
|
|
| 6. |
- 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
|
|
| 7. |
- Gren, Lucas, 1984
(författare)
-
A fourth explanation to Brooks' Law - The aspect of group developmental psychology
- 2017
-
Ingår i: 2017 Ieee/Acm 10th International Workshop on Cooperative and Human Aspects of Software Engineering (Chase 2017). - : IEEE. - 9781538640395
-
Konferensbidrag (refereegranskat)abstract
- Brooks' Law is often referred to in practice and states that adding manpower to a late software project makes it even later. Brooks' himself gave three explanation only related to concrete task-related issues, like introducing new members to the work being done, communication overheads, or difficulty dividing some programming tasks. Through a description of group developmental psychology we argue for a fourth explanation to the law by suggesting that the group will fall back in its group development when new members are added, resulting in rework setting group norms, group goals, defining roles etc. that will also change over time. We show that this fourth explanation is important when trying to understanding Brooks' Law, and that adding the group developmental perspective might help software development organizations in managing projects.
|
|
| 8. |
- Gren, Lucas, 1984
(författare)
-
Agile Process Consultation — An Applied Psychology Approach to Agility
- 2018
-
Ingår i: 24th Americas Conference on Information Systems (AMCIS). - : Association for Information Systems (AIS). - 9780996683166
-
Konferensbidrag (refereegranskat)abstract
- An agile change effort in an organization needs to be understood in relation to human processes. Such theory and accompanying tools already existed almost 50 years ago in applied psychology. The core ideas of Agile Process Consultation are that a client initiating a change toward more agility often does not know what is wrong and the consultant needs to diagnose the problem jointly with the client. It is also assumed that the agile consultant cannot know the organizational culture of the client’s organization, which means that the client needs to be making the decisions based on the suggestions provided by the consultant. Since agile project management is spreading across the enterprise and outside of software development, we need situational approaches instead of prescribing low-level practices.
|
|
| 9. |
- 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.
|
|
| 10. |
- 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.
|
|
