Assessing SCRUM Agile Principles in Concurrent Engineering

Abstract

Traditionally, space projects have followed a sequential methodology, often depicted as a V-model diagram (Fig.1). This model starts with identifying a possible system solution and assessing its feasibility. It then moves on to conceptual design and evaluating various options, requiring multiple iterations, constant stakeholder input, and thorough verification plans [1]. Concurrent Engineering (CE) is the state-of-the-art approach in space systems design, aiming to achieve the upper left part of the V diagram with shorter development times, higher consistency, and lower costs compared to sequential design processes [2,3]. The traditional linear approach can be problematic for complex space systems due to the high degree of interdependence between subsystems. A change in one component can trigger a chain reaction, affecting the entire system and leading to potential design conflicts. As space projects evolve, engineering methods need to adapt to new constraints and environments, driven by the need for tighter budgets, shorter development times, and more collaborative design processes. Concurrent Engineering (CE) enhances information flow within a dedicated environment, addressing these challenges effectively [4]. CE has gained popularity for the early design stages of spacecraft and other space systems because it addresses the limitations of the traditional step-by-step approach. By working on different subsystems simultaneously, CE shortens the overall project timeline and boosts design efficiency. In CE, teams from various disciplines start working together from day one, sharing information and refining designs in parallel. This helps to identify and resolve design conflicts early, improves communication among team members, and allows for quicker and more flexible responses to changes [5,6]. Despite its advantages, traditional CE can lead to inefficient use of resources. To improve this, integrating Agile methodologies like Scrum has been suggested [6], where Scrum is a term from the sports field meaning "tight crowd" initially applied in software development. Agile focuses on prioritizing tasks, iterative development, and flexibility. By combining Agile principles with CE, the design process can become more adaptive and efficient, leading to better resource management and improved outcomes.