How Scrum adds value to achieving software quality?

Abstract

Scrum remains the most popular agile software development method implementation for a variety of reasons; one important motive is to improve software quality. Yet many organizations fail to achieve quality improvements through the use of Scrum, and existing research sheds little light on the value-add of Scrum for software quality. More specifically, (1) how notions of software quality among Scrum practitioners relate to established quality perspectives, (2) how Scrum helps teams to achieve higher software quality and (3) why some teams fail to meet the objective of higher quality. We addressed these gaps through a two-phased qualitative study based on 39 interviews and two in-depth case studies. We find that Scrum practitioners emphasize established notions of external quality comprising of conformity to business needs and absence of defects, while they also value internal quality, especially sustainable software design. Our results show that Scrum helps teams achieve both dimensions of quality by promoting some social antecedents (collaboration, psychological safety, accountability, transparency) and process-induced advantages (iterative development, formal inspection, and adaptation). Our findings unveil how these factors contribute to achieving software quality and under what conditions their effects can fail to materialize. These conditions include inconsistent Scrum implementations, cultural constraints, team tensions, and inaccessibility of end-users. In addition, the complexity of the project aggravates the impact of these conditions. Taken together, these findings show that Scrum can complement established quality assurance and software engineering practices by promoting a social environment that is conducive to creating high-quality software. Based on our findings, we provide specific recommendations for how practitioners can create such an environment.

Development of Agile Scrum Perception Tool to Evaluate Students’ Opinions on Agile Methodology in Nursing Education

“…Items were generated on the basis of a literature search of existing tools,[ 24 25 26 27 28 29 ] and information were obtained from focus group discussions (FGD) with seven software architects practicing agile and scrum techniques in their projects. In the first FGD, the following open-ended questions[ 30 31 32 33 34 ] with probing were discussed:…”

Critical incidence reporting about medical teaching

“…We set up a CIRS which was made available to students and lecturers after only 2 months of development and roll out of the associated IT project. To this end, we used an agile project management methodology based on the Scrum framework because of its simplicity, its potential of adaption and its ability to enhance team productivity 1 . Development started with definition of needs regarding the CIRS, the so‐called ‘product backlog’ by the ‘product owner’ represented by the Dean for medical education.…”

FARUL3S: a New Framework for Agile Regulated Ultra-Large-Scale Software Systems

“…In the field of software engineering, the agile software development methodologies [2][3][4][5][6][7] have gained a lot of attention. There are many agile methodologies introduced in the literature such as SCRUM [8], Lean UX [9],…”