ScrumBut as an Indicator of Process Debt Lahti, Jacinto Ramirez; Tuovinen, Antti-Pekka; Mikkonen, Tommi ...
2022 48th Euromicro Conference on Software Engineering and Advanced Applications (SEAA),
2022-Aug.
Conference Proceeding
Odprti dostop
Technical debt analysis is used to detect problems in a codebase. Most technical debt indicators rely on measuring the quality of the code, as developers tend to induce recurring technical debt that ...emerges along with evolution cycles. This debt can emerge when project pressure leads to process deviations, for instance. In agile methods like Scrum, such deviations are commonly known as ScrumButs (like Scrum but ...), which can be considered as a form of process debt. In this paper, we investigate two recurring signs of process debt (i.e. code smells and anti-patterns) caused by Scrumbuts. Our contribution investigates typical ScrumBut practices found in agile projects in one company and we report the relationships found between problems in code and ScrumBut issues. Our findings identify three types of ScrumButs, their root causes, and how these relate to concrete code smells and anti-patterns.
Adopting agile practices is often a long process and one for which there is no existing formula for success. Some common patterns are beginning to emerge, but many of them focus on adoption within ...larger organizations. While we went through the process of adopting agile practices at IASTA, we experienced several challenges that seemed to be somewhat unique, or at least more common, in a small, organic growth organization. Finding advice and guidance on these challenges that could be implemented in our environment from the popular resources was challenging. This paper tells the story of our agile adoption process in hopes that other organizations in similar situations can learn from our experience.
In this paper we analyze the challenges we may encounter by tweaking core practices of Scrum framework (ScrumBut) or benefits we may get by blending some non-Scrum practices with Scrum framework ...(ScrumAnd). Detailed analysis is carried out on ScrumBut and ScrumAnd and their impact on project success or failure is studied. As it is not always easy to conclude if any Agile project is following ScrumBut or ScromAnd, we discuss two principles, derived from OOD, to distinguish between the two. Use of these principles is illustrated by application on real life scenarios. By application of these principles, a Scrum Practitioner can easily find out the methodology used in a particular project implementation.
