2017/01/01 by Yang Wang, Jasmin Ramadani, Stefan Wagner · 1 citation
Computer Science · Engineering · Health Professions · #Agile Unified Process #Agile software development #Context (archaeology) #Exploratory research #Occupational Health and Safety Research #Process (computing) #Safety Systems Engineering in Autonomy #Safety assurance #Scrum #Software Engineering Techniques and Practices #cs.SE
paper · pdf · doi:10.1007/978-3-319-69926-4_23
published as PROFES 2017. Lecture Notes in Computer Science, vol 10611. Springer, Cham · 16 pages, 4 figures
crossref issued 2017/01/01 · crossref published 2017/01/01 · crossref published-print 2017/01/01 · openalex publication_date 2017/01/01 · openalex created_date 2017/04/07 · crossref created 2017/10/27 · crossref published-online 2017/10/28 · arxiv created 2018/04/05 · arxiv updated 2018/04/06 · crossref deposited 2019/10/05 · crossref indexed 2026/04/11 · openalex updated_date 2026/08/05
Agile techniques recently have received attention in developing safety-critical systems. However, a lack of empirical knowledge of performing safety assurance techniques in practice, especially safety analysis into agile development processes prevents further steps. In this article, we aim at investigating the feasibility and the effects of our S-Scrum development process, and stepwise improving and proposing an Optimized S-Scrum development process for safety-critical systems in a real environment. We conducted an exploratory case study in a one-year student project "Smart Home" at the University of Stuttgart, Germany. We participated in the project and collected quantitative and qualitative data from questionnaire, interviews, participant observation, physical artifacts, and documentation review. Furthermore, we evaluated the Optimized S-Scrum in industry by conducting interviews. The first-stage results showed that by integrating STPA (System-Theoretic Process Analysis) can ensure the safety during each sprint and enhance the safety of delivered products, while the agility of S-Scrum is slightly worse than the original Scrum. Six challenges have been explored: Management changes the team's priorities during an iteration; Disturbed safety-related communication; Non-functional requirements are determined too late; Insufficient upfront planning; Insufficient well-defined completion criteria; Excessive time to perform upfront planning. We investigated further the causalities and optimizations. The second-stage results revealed that the safety and agility have been improved after the optimizations. We have gained a positive assessment and suggestions from industry. The optimized S-Scrum is feasible for developing safety-critical systems concerning the capability to ensure safety and the acceptable agility in a student project. Further attempt is still needed in industrial projects.