Skip to main content

Crisis Management in Software Engineering: Behavioral Aspects

  • Conference paper
  • First Online:
Proceedings of 5th International Conference in Software Engineering for Defence Applications (SEDA 2016)

Part of the book series: Advances in Intelligent Systems and Computing ((AISC,volume 717))

  • 515 Accesses

Abstract

Software projects failure rate is still high. It means that many projects experience crises and the managers have to deal with it. We believe that the human behavior is one of the main reasons that the projects fall into the crisis and one of the main drivers in mitigation process. In this paper we are not going to emphasize importance of a process in prevention and handling crises. Instead, we show that decisions that people make are at least as much important as process methodologies and techniques and helping employees make better decisions will benefit a company.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 129.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 169.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    Projects with an initial budget more than $15 million.

  2. 2.

    Further referred as ISD.

  3. 3.

    Since all the interviewees belong to the one side of the crisis and during the interview they had to talk about sensitive context, the researches note that the result might be biased. However, they state that this possible bias does not invalidate the case.

References

  1. A Guide to the Project Management Body of Knowledge (PMBOK Guides) (Project Management Institute, 2004)

    Google Scholar 

  2. C.J. Alberts, A.J. Dorofee, Risk management framework. Technical report, DTIC Document (2010)

    Google Scholar 

  3. N.R. Augustine, Managing the crisis you tried to prevent. Harv. Bus. Rev. 73(6), 147 (1995)

    Google Scholar 

  4. M. Bloch, S. Blumberg, J. Laartz, Delivering large-scale it projects on time, on budget, and on value

    Google Scholar 

  5. E.W. Dijkstra, The Humble Programmer. ACM Turing Lecture (1972)

    Google Scholar 

  6. S. Fink, Crisis Management: Planning for the Inevitable (American Management Association, New York, 1986)

    Google Scholar 

  7. B. Flyvbjerg, A. Budzier, Why your it project may be riskier than you think. Harv. Bus. Rev. (2011)

    Google Scholar 

  8. D. Gambetta, G. Origgi, The ll game: the curious preference for low quality and its norms. Polit. Philos. Econ. 12(1), 3–23 (2013)

    Article  Google Scholar 

  9. R. Goatham, The Story Behind the High Failure Rates in the IT Sector

    Google Scholar 

  10. B. Hardy-Vallee, The cost of bad project management. Bus. J. (2012)

    Google Scholar 

  11. B. Hardy-Vallee, How to run a successful project. Bus. J. (2012)

    Google Scholar 

  12. C. Jones, Assessment and Control of Software Risks (Yourdon Press, 1994)

    Google Scholar 

  13. H.H. Jørgensen, L. Owen, A. Neus, Making change work. Technical report (IBM Global)

    Google Scholar 

  14. G. King III, Crisis management and team effectiveness: a closer examination. J. Bus. Ethics 41(3), 235–249 (2002)

    Article  Google Scholar 

  15. K.T. Madsen, N.B. Platz, Crisis Management in IT Projects (2006)

    Google Scholar 

  16. S. Maguire, Debugging the Development Process (Microsoft Press, 1994)

    Google Scholar 

  17. I.I. Mitroff, Crisis management-cutting through the confusion. Sloan Manag. Rev. 29(2), 15–20 (1988)

    Google Scholar 

  18. P.J. Mota, Scoreboard: a support for management information needs. MSE Reflection Paper (2009)

    Google Scholar 

  19. M. Murphy, Agile project failure kills 15 m surrey police system, June 2014

    Google Scholar 

  20. C.M. Pearson, J.A. Clair, Reframing crisis management. Acad. Manag. Rev. 23(1), 59–76 (1998)

    Google Scholar 

  21. S.P. Robbins, T.A. Judge, Organizational Behavior, 15th edn. (Prentice Hall, 2012)

    Google Scholar 

  22. J. Söderlund, On the broadening scope of the research on projects: a review and a model for analysis. Int. J. Proj. Manag. 22(8), 655–667 (2004)

    Article  Google Scholar 

  23. J.E. Tomayko, O. Hazzan, Human Aspects of Software Engineering (Firewall Media, 2004)

    Google Scholar 

Download references

Acknowledgements

Authors would like to thank David B. Root and Eduardo Miranda for teaching how to learn.

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Stanislav Litvinov .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2018 Springer International Publishing AG

About this paper

Check for updates. Verify currency and authenticity via CrossMark

Cite this paper

Litvinov, S., Ivanov, V. (2018). Crisis Management in Software Engineering: Behavioral Aspects. In: Ciancarini, P., Litvinov, S., Messina, A., Sillitti, A., Succi, G. (eds) Proceedings of 5th International Conference in Software Engineering for Defence Applications. SEDA 2016. Advances in Intelligent Systems and Computing, vol 717. Springer, Cham. https://doi.org/10.1007/978-3-319-70578-1_17

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-70578-1_17

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-70577-4

  • Online ISBN: 978-3-319-70578-1

  • eBook Packages: EngineeringEngineering (R0)

Publish with us

Policies and ethics