Read more
This book addresses the development of safety-critical software and to this end proposes the SafeScrum® methodology. SafeScrum® was inspired by the agile method Scrum, which is extensively used in many areas of the software industry. Scrum is, however, not intended or designed for use with safety-critical systems; hence the authors propose guidelines and additions to make it both practically useful and compliant with the additional requirements found in safety standards.
The book provides an overview of agile software development and how it can be linked to safety and relevant safety standards. SafeScrum® is described in detail as a useful approach for reaping the benefits of agile methods, and is intended as a set of ideas and a basis for adaptation in industry projects. The book covers roles, processes and practices, and documentation. It also includes tips on how standard software process tools can be employed. Lastly, some insights into relevant research in this new and emerging field are provided, and selected real-world examples are presented.
The ideas and descriptions in this book are based on collaboration with the industry, in the form of discussions with assessment organizations, general discussions within the research fields of safety and software, and last but not least, the authors' own experiences and ideas. It was mainly written for practitioners in industry who know a great deal about how to produce safety-critical software but less about agile development in general and Scrum in particular.
List of contents
Preface.- Acknowledgements.- Glossary.- 1 Why you should read this book.- 2 What is agile software development - a short intro.- 3 What is safety-critical software.- 4 Placing agile in a safety context.- 5 Standards and certification.- 6 The SafeScrum process.- 7 SafeScrum activities.- 8 SafeScrum additional elements.- 9 Documentation and proof-of-compliance.- Annexes A-B-C-D The SafeScrum handbook.
About the author
Geir Kjetil Hanssen is a senior research scientist at SINTEF Digital in Norway, where he has focused on the use and effects of agile methods for more than 15 years. He holds a PhD in software engineering and is currently developing new research initiatives on agile development of safety-critical software, including compliance management and DevOps models. He was the project leader of the research project leading to SafeScrum® and is one of its co-founders.
Tor Stålhane is professor emeritus at the Norwegian University of Science and Technology in Trondheim. He holds a PhD in statistics and is currently doing research in software engineering and system safety analysis. He is one of the founders of SafeScrum®.
Thor Myklebust is a senior safety assessor, business developer and researcher at SINTEF Digital in Norway, where he is involved in mainly international but also national development and research projects. He has participated in several international committees since 1988, been a member of safety IEC 65, the IEC 61508 international committee, railway CENELEC/TC 9 and NB-rail (notified bodies) since 2007. In addition he was vice chair of NB-Rail in 2014 and chairman of NB-Rail in 2015. He is also one of the founders of SafeScrum®.
Summary
This book addresses the development of safety-critical software and to this end proposes the SafeScrum® methodology. SafeScrum® was inspired by the agile method Scrum, which is extensively used in many areas of the software industry. Scrum is, however, not intended or designed for use with safety-critical systems; hence the authors propose guidelines and additions to make it both practically useful and compliant with the additional requirements found in safety standards.
The book provides an overview of agile software development and how it can be linked to safety and relevant safety standards. SafeScrum® is described in detail as a useful approach for reaping the benefits of agile methods, and is intended as a set of ideas and a basis for adaptation in industry projects. The book covers roles, processes and practices, and documentation. It also includes tips on how standard software process tools can be employed. Lastly, some insights into relevant research in this new and emerging field are provided, and selected real-world examples are presented.
The ideas and descriptions in this book are based on collaboration with the industry, in the form of discussions with assessment organizations, general discussions within the research fields of safety and software, and last but not least, the authors’ own experiences and ideas. It was mainly written for practitioners in industry who know a great deal about how to produce safety-critical software but less about agile development in general and Scrum in particular.
