The Project Management Information System as Enabler for ICT4D Achievement at Capability Maturity Level 2 and Above

  • Mark Jonathan CorriganEmail author
  • John Andrew van der Poll
  • Emmanuel Samuel Mtsweni
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 933)


Current trends in project management promote Agile as a solution for challenges around project delivery, focusing more on individuals and interactions than on processes and tools. This paper postulates that any project method, especially agile, if undertaken with limited process focus below Capability Maturity (CM) Level 2, may well result in project delivery failures, despite best intentions from the project team. With dynamic Internet growth in developing countries, and advancements in virtual collaboration, projects ought to involve tailoring jointly-agreed project management processes at Capability Maturity level 2 and above. In addition, the utilisation of a Project Management Information System (PMIS) emplacement is essential for project management success. The use of a PMIS is in line with a process-driven approach to ICT4D, and will facilitate the ICT value proposition for a developing economy. Following a comprehensive literature review, the paper asserts that Capability Maturity Level 2 will remain relatively unattainable, unless the PMIS emplacement becomes a strategic driver for success. To this end, we propose a PMIS CM Improvement Framework to the PMBOK Process Group and Knowledge Area matrix, and establish the value proposition for ICT4D.


ICT4D Agile Capability maturity levels Chaos Productivity Theory of Constraints Project management Process management Project Management Information System Software engineering Earned value management Value proposition 


  1. 1.
    Project Management Institute: A Guide to the Management Body of Knowledge. Project Management Institute, Inc., Atlanta (2017)Google Scholar
  2. 2.
    The Standish Group: The Standish group: the chaos report. Project Smart 16 (2014)Google Scholar
  3. 3.
    Sutherland, J., et al.: Manifesto for Agile Software Development.
  4. 4.
    Deming, W.E.: Out of the crisis. Massachusetts Institute of Technology, Center for Advanced Engineering Study, Cambridge (1986)Google Scholar
  5. 5.
    Eveleens, L.J., Verhoef, C.: The rise and fall of the chaos report figures. IEEE Softw. 27(1), 30–36 (2010)., ISSN 0740-7459CrossRefGoogle Scholar
  6. 6.
    Schach, S.R.: Object-Oriented and Classical Software Engineering. McGraw-Hill, New York (2011)Google Scholar
  7. 7.
    Guess, V.C.: CMII for Business Process Infrastructure. CMII Research Instutite (2006)Google Scholar
  8. 8.
    Hirsch, B.J.a.: PMI’s Pulse of the Profession. 2012 PMI Pulse Prof., 1–9 March 2012Google Scholar
  9. 9.
    Vargas, R.: Elaboration of the PMBOK 6 process flow.
  10. 10.
    Richards, K., Cooper, L.: PRINCE2 Agile. The Stationery Office, Norwich (2015)Google Scholar
  11. 11.
    Office of Government Commerce: Managing Successful Projects with PRINCE2. TSO, London (2009)Google Scholar
  12. 12.
    DSDM Consortium: Agile PM. Agile Project Management Handbook Version 2. DSDM Consortium (2014)Google Scholar
  13. 13.
    Setpathy, T.: Scrum Body of Knowledge. SCRUMstudy (2016)Google Scholar
  14. 14.
    Extreme Programming Web Site.
  15. 15.
    Boehm, B.: Get ready for agile methods, with care. Comput. (Long. Beach. Calif.) 35, 64–69 (2002)Google Scholar
  16. 16.
    Rakitin, S.: Manifesto elicits cynicism. IEEE Comput. 34, 4–7 (2001)Google Scholar
  17. 17.
    Schach, S.: Object Orientated and Classical Software Engineering, 8th edn. (2007)Google Scholar
  18. 18.
    Clinning, G., Marnewick, C.: Incorporating sustainability into IT project management. S. Afr. Comput. J. 29, 1–26 (2017)Google Scholar
  19. 19.
    Wysocki, R.K.: Effective Complext Project Management (2014)Google Scholar
  20. 20. Parallels in Delivering Organisational Change as a Bowl Of Soup.
  21. 21.
    Chrissis, M.B., Konrad, M., Shrum, S.: CMMI for Development. Addison-Wesley, Upper Saddle River (2011)Google Scholar
  22. 22.
    Brooks, F.P.J.: No silver bullet-essence and accidents of software engineering. In: Proceedings of the IFIP Tenth World Computing Conference, pp. 1069–1076 (1986)Google Scholar
  23. 23.
    Kruger, J., Dunning, D.: Unskilled and unaware of it: how difficulties in recognizing one’s own incompetence lead to inflated self-assessments. J. Pers. Soc. Psychol. 77, 1121–1134 (1999)CrossRefGoogle Scholar
  24. 24.
    Dudley, M.: Ladies and gentlemen, here comes the Dunning-Kruger Effect.
  25. 25.
    Scaled Agile: SAFe ® 4.5 Introduction Overview of the Scaled Agile Framework ® for Lean Enterprises. A Scaled Agil. Inc. White Pap. (2017)Google Scholar
  26. 26.
    Brooks, F.P.: No silver bullet: essence and accidences of software engineering. Comput. (Long. Beach. Calif.) 20, 10–19 (1987)Google Scholar
  27. 27.
    Brooks, F.P.: The Mythical Man - Month. Essays on Software Engineering, Anniversary Edition (1995)Google Scholar
  28. 28.
    Bočková, K.H., Sláviková, G., Gabrhel, J.: Game theory as a tool of project management. Procedia Soc. Behav. Sci. 213, 709–715 (2015)CrossRefGoogle Scholar
  29. 29.
    Braglia, M., Frosolini, M.: An integrated approach to implement Project Management Information Systems within the extended enterprise. Int. J. Proj. Manag. 32, 18–29 (2014)CrossRefGoogle Scholar
  30. 30.
    Meredith, J.R., Mantel, S.J.J.: Project Management: A Managerial Approach (2009)Google Scholar
  31. 31.
    Raymond, L., Bergeron, F.: Project management information systems: an empirical study of their impact on project managers and project success. Int. J. Proj. Manag. 26, 213–220 (2008)CrossRefGoogle Scholar
  32. 32.
    Engwall, M., Jerbrant, A.: The resource allocation syndrome: The prime challenge of multi-project management? Int. J. Proj. Manag. JPMA 21, 403–409 (2003)Google Scholar
  33. 33.
    Tromp, J.W., Homan, T.: How unplanned changes emerge while implementing a Project Management Information System (PMIS) in a complex multi project R&D environment. Procedia Soc. Behav. Sci. 194, 211–220 (2015)CrossRefGoogle Scholar
  34. 34.
    Goldratt, E.M.: Critical Chain. North River Press, Great Barrington (1997)Google Scholar
  35. 35.
    Walton, M., Heeks, R.: Development Informatics Improve ICT4D Project Success? Development Informatics Group (2011)Google Scholar
  36. 36.
    People Capability Maturity Model (P-CMM) (2009)Google Scholar

Copyright information

© Springer Nature Switzerland AG 2019

Authors and Affiliations

  1. 1.School of ComputingUniversity of South AfricaJohannesburgSouth Africa
  2. 2.Graduate School of Business LeadershipUniversity of South AfricaMidrandSouth Africa
  3. 3.School of ComputingUniversity of South AfricaJohannesburgSouth Africa

Personalised recommendations