Abstract
Software is successfully applied in a wide variety of areas. However, software projects have suffered from poor reputation by repeatedly bursting deadlines, costs or failing to fully meet user requirements. Postmortem Analysis is an activity to analyze what happened in projects in search of understanding the failures occurred and the achieved successes. Despite bringing interesting data for improving future projects, Postmortem Analysis is often neglected in organizations. This article seeks to identify and analyze the technical and managerial difficulties that exist in its accomplishment through bibliographical research. As a result, it is possible to conclude that the main difficulties for realizing postmortem activities are the shortage of time, lack of management support, conflicts between stakeholders, difficulty in extracting and collecting data, lack of agreement regarding evaluation criteria, lack of standards for achievement, and lack of useful or efficient historical data.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Ahonen, J.-J., Savolainen, P.: Software engineering projects may fail before they are started: post-mortem analysis of five cancelled projects. J. Syst. Softw. 83(11), 2175–2187 (2010)
Birk, A., Dingsoyr, T., Stalhane, T.: Postmortem: never leave a project without it. IEEE Softw. 19(3), 43–45 (2002)
Bjarnason, E., Hess, A., Svensson, R.-B., Regnell, B., Doerr, J.: Reflecting on evidence-based timelines. IEEE Softw. 31(4), 37–43 (2014)
Bjørnson, F.-O., Dingsøyr, T.: Knowledge management in software engineering: a systematic review of studied concepts, findings and research methods used. Inf. Softw. Technol. 50(11), 1055–1068 (2008)
Bjørnson, F.-O., Wang, A.-I., Arisholm, E.: Improving the effectiveness of root cause analysis in post mortem analysis: a controlled experiment. Inf. Softw. Technol. 51(1), 150–161 (2009)
Cerpa, N., Verner, J.-M.: Why did your project fail? Commun. ACM 52(12), 130–134 (2009)
Charette, R.-N.: Why software fails [software failure]. IEEE Spectr. 42(9), 42–49 (2005)
Charette, R.-N.: IT’s fatal amnesia. Computer 50(2), 86–91 (2017)
Collier, B., DeMarco, T., Fearey, P.: A defined process for project post mortem review. IEEE Softw. 13(4), 65–72 (1996)
Dingsøyr, T.: Postmortem reviews: purpose and approaches in software engineering. Inf. Softw. Technol. 47(5), 293–303 (2005)
Duffield, S., Whitty, S.-J.: How to apply the systemic lessons learned knowledge model to wire an organisation for the capability of storytelling. Int. J. Proj. Manag. 34(3), 429–443 (2016)
Glass, R.-L.: Project retrospectives, and why they never happen. IEEE Softw. 19(5), 111–112 (2002)
Jørgensen, M.: A survey on the characteristics of projects with success in delivering client benefits. Inf. Softw. Technol. 78(Supplement C), 83–94 (2016)
Lehtinen, T.-O., Mäntylä, M.-V., Itkonen, J., Vanhanen, J.: Diagrams or structural lists in software project retrospectives an experimental comparison. J. Syst. Softw. 103(Supplement C), 17–35 (2015)
Lehtinen, T.-O., Virtanen, R., Viljanen, J.-O., Mäntylä, M.-V., Lassenius, C.: A tool supporting root cause analysis for synchronous retrospectives in distributed software teams. Inf. Softw. Technol. 56(4), 408–437 (2014)
Lehtinen, T.-O., Itkonen, J., Lassenius, C.: Recurring opinions or productive improvements—what agile teams actually discuss in retrospectives. Empirical Softw. Eng. 22(5), 2409–2452 (2017)
Linberg, K.-R.: Software developer perceptions about software project failure: a case study. J. Syst. Softw. 49(2–3), 177–192 (1999)
Menke, M.-M.: Managing R&D for competitive advantage. Res.-Technol. Manag. 40(6), 40–42 (1997)
Mitchell, S.-M., Seaman, C.-B.: Could removal of project-level knowledge flow obstacles contribute to software process improvement? A study of software engineer perceptions. Inf. Softw. Technol. 72(Suppl. C), 151–170 (2016)
Nonaka, I., Takeuchi, H.: The Knowledge Creating Company: How Japanese Companies Create the Dynamics of Innovation. Oxford University Press, New York (1995)
Politowski, C., Fontoura, L.-M., Petrillo, F., Guéhéneuc, Y.-G.: Learning from the past: a process recommendation system for video game projects using postmortems experiences. Inf. Softw. Technol. 100, 103–118 (2018)
Savolainen, P., Ahonen, J.-J., Richardson, I.: Software development project success and failure from the supplier’s perspective: a systematic literature review. Int. J. Proj. Manag. 30(4), 458–469 (2012)
Sharon, I., Soares, M.S., Barjis, J., van den Berg, J., Vrancken, J.L.M.: A decision framework for selecting a suitable software development process. In: International Conference on Enterprise Information Systems, pp. 34–43 (2010)
Sommerville, I.: Software Engineering. Pearson, Boston (2011)
Stålhane, T., Dingsøyr, T., Hanssen, G.K., Moe, N.B.: Post mortem – an assessment of two approaches. In: Conradi, R., Wang, A.I. (eds.) Empirical Methods and Studies in Software Engineering. LNCS, vol. 2765, pp. 129–141. Springer, Heidelberg (2003). https://doi.org/10.1007/978-3-540-45143-3_8
Williams, T.: Identifying the hard lessons from projects - easily. Int. J. Proj. Manag. 22(4), 273–279 (2004)
Zhivich, M., Cunningham, R.-K.: The real cost of software errors. IEEE Secur. Privacy 7(2), 87–90 (2009)
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2019 Springer Nature Switzerland AG
About this paper
Cite this paper
Vieira, F.J.R., Oliveira, M.R., do Nascimento, R.P.C., Soares, M.S. (2019). Technical and Managerial Difficulties in Postmortem Analysis in Software Projects. In: Misra, S., et al. Computational Science and Its Applications – ICCSA 2019. ICCSA 2019. Lecture Notes in Computer Science(), vol 11623. Springer, Cham. https://doi.org/10.1007/978-3-030-24308-1_5
Download citation
DOI: https://doi.org/10.1007/978-3-030-24308-1_5
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-030-24307-4
Online ISBN: 978-3-030-24308-1
eBook Packages: Computer ScienceComputer Science (R0)