Are Daily Stand-up Meetings Valuable? A Survey of Developers in Software Teams

The daily stand-up meeting is a widely used practice. However, what is more uncertain is how valuable the practice is to team members. We invited professional developers of a programming forum to a survey and obtained 221 responses. Results show that the daily stand-up meeting was used by 87% of those who employ agile methods. We found that even though the respondents on average were neutral towards the practice, the majority were either positive or negative. Junior developers were most positive and senior developers and members of large teams most negative. We argue that the value of the practice should be evaluated according to the team needs. Further, more work is needed to understand why senior developers do not perceive the meetings as valuable and how to apply the practice successfully in large teams

Report from The International Society for Nomenclature of Paediatric and Congenital Heart Disease: cardiovascular catheterisation for congenital and paediatric cardiac disease (Part 1-Procedural nomenclature)

Interventional cardiology for paediatric and congenital cardiac disease is a relatively young and rapidly evolving field. As the profession begins to establish multi-institutional databases, a universal system of nomenclature is necessary for the field of interventional cardiology for paediatric and congenital cardiac disease. The purpose of this paper is to present the results of the efforts of The International Society for Nomenclature of Paediatric and Congenital Heart Disease to establish a system of nomenclature for cardiovascular catheterisation for congenital and paediatric cardiac disease, focusing both on procedural nomenclature and on the nomenclature of complications associated with interventional cardiology. This system of nomenclature for cardiovascular catheterisation for congenital and paediatric cardiac disease is a component of The International Paediatric and Congenital Cardiac Code. This manuscript is the first part of a two-part series. Part 1 will cover the procedural nomenclature associated with interventional cardiology as treatment for paediatric and congenital cardiac disease. This procedural nomenclature of The International Paediatric and Congenital Cardiac Code will be used in the IMPACT Registry\u2122 (IMproving Pediatric and Adult Congenital Treatment) of the National Cardiovascular Data Registry\uae of The American College of Cardiology. Part 2 will cover the nomenclature of complications associated with interventional cardiology as treatment for paediatric and congenital cardiac disease

Results from a Replicated Experiment on the Affective Reactions of Novice Developers When Applying Test-Driven Development

Test-Driven Development (TDD) is an incremental approach to software development. Despite it is claimed to improve both quality of software and developers’ productivity, the research on the claimed effects of TDD has so far shown inconclusive results. Some researchers have ascribed these inconclusive results to the negative affective states that TDD would provoke. A previous (baseline) experiment has, therefore, studied the affective reactions of (novice) developers—i.e., 29 third-year undergraduates in Computer Science (CS)—when practicing TDD to implement software. To validate the results of the baseline experiment, we conducted a replicated experiment that studies the affective reactions of novice developers when applying TDD to develop software. Developers in the treatment group carried out a development task using TDD, while those in the control group used a non-TDD approach. To measure the affective reactions of developers, we used the Self-Assessment Manikin instrument complemented with a liking dimension. The most important differences between the baseline and replicated experiments are: (i) the kind of novice developers involved in the experiments—third-year vs. second-year undergraduates in CS from two different universities; and (ii) their number—29 vs. 59. The results of the replicated experiment do not show any difference in the affective reactions of novice developers. Instead, the results of the baseline experiment suggest that developers seem to like TDD less as compared to a non-TDD approach and that developers following TDD seem to like implementing code less than the other developers, while testing code seems to make them less happy

An Empirical Assessment on Affective Reactions of Novice Developers When Applying Test-Driven Development

We study whether and in which phase Test-Driven Development (TDD) influences affective states of novice developers in terms of pleasure, arousal, dominance, and liking. We performed a controlled experiment with 29 novice developers. Developers in the treatment group performed a development task using TDD, whereas those in the control group used a non-TDD development approach. We compared the affective reactions to the development approaches, as well as to the implementation and testing phases, exploiting a lightweight, powerful, and widely used tool, i.e., Self-Assessment Manikin. We observed that there is a difference between the two development approaches in terms of affective reactions. Therefore, it seems that affective reactions play an important role when applying TDD and their investigation could help researchers to better understand such a development approach