Identifying and Addressing Risks in the Early Design of a Sociotechnical System through Premortem

Abstract

Anticipating risks in software development is always challenging, but particularly so when the software application is part of a novel sociotechnical system with various human and physical components. Our interdisciplinary team of software engineering and human factors researchers is designing such a system. In order to identify and mitigate the risks latent in this previously unexplored space, we have used the premortem method at an early stage in system design. In the premortem, the team ideated failure scenarios across the range of system use, then collaborated on ways to eliminate, mitigate, or monitor the risks of these failures. We have found the premortem method valuable in recognizing and mitigating previously unanticipated risks and in enriching team communication.

Get full access to this article

View all access options for this article.

References

Boehm

B.W.

(1988). A spiral model of software development and enhancement. Computer 21(5), 61-72.

Boehm

B.W.

(1991). Software risk management: principles and practices. IEEE Software 8(1), 32-41.

Boehm

B.W.

Ross

(1989). Theory-W software project management principles and examples. IEEE Transactions on Software Engineering. 15(7), 902-916.

Dong

Kleinsmann

M. S.

Deken

(2013). Investigating design cognition in the construction and enactment of team mental models. Design Studies, 34(1), 1-33. https://doi.org/10.1016/i.destiid.2012.05.003

Dougherty

(1992). Interpretive barriers to successful product innovation in large firms. Organization Science, 3(2), 179-202. https://doi.org/10.1287/orsc.3.2.179

Haigh

F.D.

(2021) SW failure modes and effects analysis. NASA Software Engineering Handbook, 8.5.

https://swehb.nasa.Gov

Higuera

R.P.

Haimes

Y.Y.

(1996). Software risk management. Tech Report CMU/SEI-96-TR-012, Software Engineering Institute.

Keil

Cule

P.E.

Lyytinen

Schmidt

R.C.

(1998). A framework for identifying software project risks. Communications of the ACM 41(11), 76-83.

10.

Klein

(2007). Performing a project premortem. Harvard Business Review, 85(9), 18-19.

11.

Klein

(2021). The Pre-Mortem Method. https://www.psychologytoday.com/us/blog/seeing-what-others-dont/202101/the-pre-mortem-method

12.

Kleinsmann

M. S.

(2006). Understanding Collaborative Design. PhD Thesis. Netherlands, Delft University.

13.

Kleinsmann

Buijs

Valkenburg

(2010). Understanding the complexity of Knowledge Integration in collaborative new product development teams: A case study. Journal of Engineering and Technology Management, 27(1-2), 20-32. https://doi.org/10.1016/jjengtecman2010.03.003

14.

Kleinsmann

Valkenburg

(2008). Barriers and enablers for creating shared understanding in co-design projects. Design Studies, 29(4), 369-386. https://doi.org/10.1016/j.destud.2008.03.003

15.

Mitchell

D. J.

Russo

J. E.

Pennington

(1989). Back to the Future: Temporal Perspective in the Explanation of Events. Journal of Behavioral Decision Making, 2,25-38

16.

Ovstedal

E.O.

(1991). Using fault tree analysis in developing reliable software. IFAC Proceedings, Volume 24(13), 77-82.

17.

Peabody

Veinott

(2017). Focus shift: Differences in reasons generated using Premortem and Worst Case Scenario plan evaluation methods. Naturalistic Decision Making, 259-261.

18.

Pirinen

(2016). The Barriers and Enablers of Co-design for Services. International Journal of Design, 10(3), 27-42.

19.

Reifer

D. J.

(1979). Software failure modes and effects analysis. IEEE Transactions on reliability, 28(3), 247-249.

20.

Roth

Kleiner

(2000). Car Launch: The Human Side of Managing Change. Oxford University Press.

21.

Veinott

E. S.

Klein

Wiggins

(2010). Evaluating the effectiveness of the PreMortem technique on plan confidence. Proceedings of ISCRAM, Seattle, WA.