Skip to main content

Identifying Organizational Issue for Digital Transformation by an Analysis Based on Kaizen

  • Chapter
  • First Online:
Research on Project, Programme and Portfolio Management

Abstract

Digital transformation requires utilizing information technology (IT) system as well as collaboration between IT vendor and IT user. However, we have been observing disputes between the users and the vendors to compensate for individual loss due to failures of IT projects (IT disputes), which waste tremendous resources and opportunities. Nevertheless, not only root causes of IT disputes, but also why they failed to avoid the disputes, are not clear in most cases. The business risk caused by such IT disputes has been difficult to be visualized sufficiently enough to avoid the same dispute in the future. This paper tries to make it possible for them to manage the business risk of the IT disputes by visualizing the risk. By applying a new method based on Kaizen to analyze IT dispute cases of actual IT projects, where recent technologies of package software and agile are introduced for quick response to individual new challenge, we specify individual root cause and visualize a business risk, whose threat has not been understood by organizations. Furthermore, we also discuss development of improved management to cope with the threat of the visualized business risk, from the aspect of organization.

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 139.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 179.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 179.99
Price excludes VAT (USA)
  • Durable hardcover 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

References

  1. Brooks FP (1987) No silver bullet—essence and accidents of software engineering. IEEE Comput 20(4):10–19

    Article  Google Scholar 

  2. Furuyama T et al (2007) Analysis of the factor that affect the performance of software projects. Information Processing 48(8):2608–2619

    Google Scholar 

  3. IPA (2006) A white paper of software data. Nikkei BP, Japan

    Google Scholar 

  4. IPA (2006) MIERUKA of IT project (lower development phase). Nikkei BP, Japan

    Google Scholar 

  5. IPA (2006) Principle 17 articles, pp 87–110 in Ensuring quality of requirement by involving the management 2nd ed. Ohmusha, Japan

    Google Scholar 

  6. IPA (2007) MIERUKA (visualization) of IT project (upper development phase). Nikkei BP, Japan

    Google Scholar 

  7. IPA (2008) MIERUKA of IT project (middle development phase). Nikkei BP, Japan

    Google Scholar 

  8. IPA (2008) MIERUKA of IT project (summary). Nikkei BP, Japan

    Google Scholar 

  9. JISA (2011) Requirements engineering body of knowledge (REBOK), 1st edn. Kindai Kagakusya, Japan

    Google Scholar 

  10. METI (2007) Model transaction/contract, 1st edn. https://www.meti.go.jp/policy/it_policy/keiyaku/index.html. Accessed 11 Sept 2020

  11. Nikkei Computer (2008) 2nd investigation of actual situation of projects. Nikkei BP, Japan

    Google Scholar 

  12. Ohtaka H, Fukazawa Y (2010) Managing risk symptom: a method to identify major risks of serious problem projects in si environment using cyclic causal model. Project Manage J 41(1):51–60

    Article  Google Scholar 

  13. Ohtaka H, Fukazawa Y (2011) Analysis of causes of serious problem projects focusing on stakeholders. J Soc Project Manag 13(3):19–25

    Google Scholar 

  14. PMI (2008) The standard for portfolio management, 2nd edn. PMI, USA

    Google Scholar 

  15. PMI (2008) The standard for program management, 2nd edn. PMI, USA

    Google Scholar 

  16. PMI (2013) Organizational project management maturity model, 3rd edn. PMI, USA

    Google Scholar 

  17. PMI (2016) A guide to the project management of knowledge (PMBOK), 6th edn. PMI, USA

    Google Scholar 

  18. Serrador P, Pinto KJ (2015) Does agile work?—a quantitative analysis of agile project success. Int J Project Manage 33(5):1040–1051

    Article  Google Scholar 

  19. Smith J (2001) Troubled IT projects—prevention and turnaround. IEE, London, UK

    Book  Google Scholar 

  20. Smith J (2002) The 40 root causes of troubled IT projects. Comput Control Eng J 109–112

    Google Scholar 

  21. Standish Group (2020) CHAOS report. Standish Group, USA

    Google Scholar 

  22. Sutterfield S et al (2006) a case study of project and stakeholder management failures: lessons learned. Project Manage J 37(5):26–35

    Article  Google Scholar 

  23. Yeo K (2002) Critical failure factors in information system projects. Int J Project Manage 20(1):241–246

    Article  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Hiroshi Ohtaka .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2022 The Author(s), under exclusive license to Springer Nature Switzerland AG

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Ohtaka, H., Koumura, M., Isokawa, M. (2022). Identifying Organizational Issue for Digital Transformation by an Analysis Based on Kaizen. In: Ding, R., Wagner, R., Bodea, CN. (eds) Research on Project, Programme and Portfolio Management. Lecture Notes in Management and Industrial Engineering. Springer, Cham. https://doi.org/10.1007/978-3-030-86248-0_9

Download citation

Publish with us

Policies and ethics