An official website of the United States government
Traditionally, safety-critical projects have been de- veloped using the waterfall process. However, this makes it costly and challenging to incrementally introduce new features and to certify the modified product for use. As a result, there has been increasing interest in adopting agile development paradigms within the safety-critical domain. This in turn intro- duces numerous challenges. In this paper we address the specific problems of discovering, analyzing, specifying, and managing safety requirements within the agile Scrum process. We propose SafetyScrum, a methodology that augments the Scrum lifecycle with incrementally applied safety-related activities and introduces the notion of “safety debt” for incrementally tracking the current safety status of a project. We demonstrate the viability of SafetyScrum for managing safety stories in an agile development environment by applying it to a project in which our existing Unmanned Aerial Vehicle system is enhanced to support a River- Rescue scenario.
more »
« less
Discovering, Analyzing, and Managing Safety Stories in Agile Projects
Traditionally, safety-critical projects have been developed using the waterfall process. However, this makes it costly and challenging to incrementally introduce new features and to certify the modified product for use. As a result, there has been increasing interest in adopting agile development paradigms within the safety-critical domain. This in turn introduces numerous challenges. In this paper we address the specific problems of discovering, analyzing, specifying, and managing safety requirements within the agile Scrum process. We propose SafetyScrum, a methodology that augments the Scrum life-cycle with incrementally applied safety-related activities and introduces the notion of ``safety debt'' for incrementally tracking the current safety status of a project. We demonstrate the viability of SafetyScrum for managing safety stories in an agile development environment by applying it to a project in which our existing Unmanned Aerial Vehicle system is enhanced to support a River-Rescue scenario.
more »
« less
- Award ID(s):
- 1741781
- PAR ID:
- 10096064
- Date Published:
- Journal Name:
- IEEE Conference on Requirements Engineering
- Volume:
- 2018
- Page Range / eLocation ID:
- 262 to 273
- Format(s):
- Medium: X
- Sponsoring Org:
- National Science Foundation
More Like this
-
-
Abstract Developing sustainable software for the scientific community requires expertise in software engineering and domain science. This can be challenging due to the unique needs of scientific software, the insufficient resources for software engineering practices in the scientific community, and the complexity of developing for evolving scientific contexts. While open‐source software can partially address these concerns, it can introduce complicating dependencies and delay development. These issues can be reduced if scientists and software developers collaborate. We present a case study wherein scientists from the SuperNova Early Warning System collaborated with software developers from the Scalable Cyberinfrastructure for Multi‐Messenger Astrophysics project. The collaboration addressed the difficulties of open‐source software development, but presented additional risks to each team. For the scientists, there was a concern of relying on external systems and lacking control in the development process. For the developers, there was a risk in supporting a user‐group while maintaining core development. These issues were mitigated by creating a second Agile Scrum framework in parallel with the developers' ongoing Agile Scrum process. This Agile collaboration promoted communication, ensured that the scientists had an active role in development, and allowed the developers to evaluate and implement the scientists' software requirements. The collaboration provided benefits for each group: the scientists actuated their development by using an existing platform, and the developers utilized the scientists' use‐case to improve their systems. This case study suggests that scientists and software developers can avoid scientific computing issues by collaborating and that Agile Scrum methods can address emergent concerns.more » « less
-
In this paper, we propose an innovative practice based on agile software development methods. This research approach introduces agility into learning of research in an academic environment, resulting in an Agile Research Team. Such a research team follows an agile approach, based on modifications to the Scrum approach, to collaboratively learn about research, and to manage research projects and the researchers involved. Success in research requires self-motivation, collaboration, and knowledge exchange. Traditional research occurs in top-down research groups that are led by a leading researcher, who oversees postdoctoral researchers and Ph.D. students, who in turn manage graduate and undergraduate level students. It is up to individual researchers to stay motivated, to acquire the necessary skills to conduct research, and, oftentimes, to decide what the following steps are. Much like effective research groups, agile software development approaches rely on individuals to form self-organizing and motivated teams to deliver technical excellence. Agile software development teams also require an environment of sharing knowledge between senior and junior developers. Agile approaches can facilitate the efficient exchange of knowledge due to a strong dependency on face-to-face communication and teamwork. With the emerging adoption of agile methods for software development in industry and its ability to expedite projects’ delivery, we argue that such approaches can potentially provide similar benefits for researchers and students in academia. The advantages that agile methods provide are twofold: the ability to respond faster to change, and a shorter feedback loop, which facilitates the learning of how to conduct research. This paper explores the impactful benefits of using an agile approach to manage research team projects to keep researchers motivated, enhance the learning of knowledge and research skills, increase scalability, and foster inclusivity. This paper will also present the roles, responsibilities, and processes defined for managing an Agile Research Team to support adoption of the approach with other research teams. In addition, results and lessons learned are presented following our experience with using the approach as described in this work.more » « less
-
null (Ed.)Study explores Scrum, a comprehensive team performance process based on Agile engineering principles, through an I/O lens. Study focuses on impact of Scrum implementation on team performance, organizational culture, and change management. Role of I/O in implementing engineering process improvement programs is discussed, as well as need for greater I/O involvement in engineering process management.more » « less
-
Teamwork has been identified as one of the essential professional skills for the 21st century. Business, industries, and corporates require their employees to work in teams on various projects. Therefore, it is crucial to introduce and train undergraduate students on teamwork skills. Working in teams is not easy as one needs to collaborate with people from diverse backgrounds, skillsets, and opinions. The disagreement among the team members may lead to conflict and chaos that jeopardizes the team's harmony. Therefore, just creating teams and assigning a group project is insufficient to help undergraduate students develop teamwork skills. Instructors need to help students become cognizant of their teamwork skills, such as conflict resolution, scrum values, and cultural self-awareness. In this research paper, we intend to understand the perception of students enrolled in a sophomore-level system's course regarding conflict resolution skills, scrum values, and cultural self-awareness. We also want to understand how the perception of these values is related to one another. In the light of this study, we want to answer the following research questions (1) How do students' reported conflict management skills relate to their reported scrum values? (2) How do students' cultural self-awareness relate to their conflict management skills? (3) How do students' cultural self-awareness relate to their reported scrum values? A course on system analysis and design followed a project-based cooperative learning approach. The students were required to work in teams and complete the course deliverables, including the final course project. The team projects followed a scrum approach that helped students identify the project requirements, perform modeling and develop a prototype. Since students worked on scrum- driven projects in a cooperative learning environment, the students were required to participate in a survey study that allowed the instructional team to develop an understanding of the students' perception of conflict management, scrum values, and cultural self-awareness. The responses of the students were analyzed using descriptive and inferential statistics. The results suggest that students found themselves competent in managing conflict, adhering to scrum values, and demonstrating a high-level cultural self-awareness.more » « less
- Free Publicly Accessible Full Text
-
Accepted Manuscript1.0
- Conference Paper:
- https://doi.org/10.1109/RE.2018.00034
