SciELO - Scientific Electronic Library Online

 
vol.23 número3 índice de autoresíndice de assuntospesquisa de artigos
Home Pagelista alfabética de periódicos  

Serviços Personalizados

Artigo

Indicadores

Links relacionados

  • Em processo de indexaçãoCitado por Google
  • Em processo de indexaçãoSimilares em Google

Compartilhar


South African Journal of Industrial Engineering

versão On-line ISSN 2224-7890
versão impressa ISSN 1012-277X

S. Afr. J. Ind. Eng. vol.23 no.3 Pretoria Jan. 2012

 

FEATURE ARTICLES

 

Project management maturity and project management success in the engineering and construction industries in Southern Africa#

 

 

S. PretoriusI, 1; H. SteynII, *; J.C. JordaanIII

IDepartment of Engineering and Technology Management Graduate School of Technology Management University of Pretoria, South Africa. Suzaan.Pretorius@up.ac.za
IIDepartment of Engineering and Technology Management Graduate School of Technology Management University of Pretoria, South Africa. Herman.Steyn@up.ac.za
IIIStatomet University of Pretoria, South Africa. Joyce.Jordaan@up.ac.za

 

 


ABSTRACT

Previous studies have attempted to determine how the success of South African IT projects related to the project management maturity of the organisations that executed the projects. The study reported in this article was conducted during 2010 in the engineering and construction sectors. This paper reports on a structured questionnaire distributed to 1,625 individuals mainly in the South African engineering and construction industries, from which 255 responses were received. 'Project success' was self-defined by the respondents, who identified 'project success' within their unique environments and contexts. The bulk of the projects (46%) were considered successful. The average perceived project management maturity level was 2.88.


OPSOMMING

Vorige studies het bepaal hoe die sukses van Suid-Afrikaanse IT projekte vergelyk met die projekbestuursvolwassenheid van die organisasies wat die projekte uitgevoer het. Hierdie studie is uitgevoer gedurende 2010 in die ingenieurs- en konstruksiebedrywe. 'n Gestruktu-reerde vraelys is versprei aan 1,625 mense wat meestal werksaam was in die Suid-Afrikaanse ingenieurswese-en konstruksiebedrywe, en 255 antwoorde is ontvang. 'Projeksukses' is selfgedefinieer deur die respondente op grond van hulle unieke omgewings en kontekste. Die grootste hoeveelheid van die projekte (46%) is as suksesvol gereken. Die gemiddelde waargeneemde vlak van projekbestuursvolwassenheid was 2.88.


 

 

1. INTRODUCTION

Studies to determine how the project management maturity of organisations related to the success of projects in the South African IT industry were conducted in 2003 and 2008 [1, 2]. This paper reports on part of a further study, performed during 2010, where it was decided also to include industries such as engineering, construction, petrochemicals, and mining to determine how the maturity of these industries differed from the maturity of the South African IT environment. The literature indicates that elsewhere in the world 'industries of origin' (engineering-based industries) can be expected to be more mature in terms of project management than industries that adapted project management principles and practices later on [3]. This study aimed to investigate the situation in Southern Africa.

The objectives for the study were the following:

i. To investigate the relationship between project management maturity and project success in engineering and construction industries in Southern Africa.

ii. To compare the 2010 level of maturity and the degree of success of engineering and construction industries with those of the IT industry in 2008.

iii. To investigate the effect of project size on project success in engineering and construction industries in Southern Africa.

iv. To investigate the effect of maturity in the nine knowledge areas on project outcome in the industries studied.

v. To explore the role of competencies of project managers in project success.

While the main focus of the study is to correlate success with maturity, project size and the competency of the project manager (rather than organisational maturity) might provide alternative explanations for project success, and these two aspects are therefore included in this study.

 

2. LITERATURE REVIEW

2.1 Project management and maturity levels

The Oxford Advanced Learner's Dictionary [4] defines 'maturity' as "the state of being fully grown or developed". When this concept is applied to a project, it could imply a situation where an organisation has standards and procedures in place that would assist it in reaching its objectives. An organisation is mature when it is in a position to deal perfectly with its projects [5].

Since the mid-1990s a number of project management maturity models (PMMMs) have been developed. Currently more than 30 models are available. The majority of these PMMMs consist of five distinct levels: level 1 is the initial level where no established project management practices exist; and level 5 is the 'optimising' level where the company is fully mature. Figure 1 describes the five maturity levels. However, at present there is still no single PMMM that is accepted worldwide [6, 7].

 

Figure 1: Project management maturity model [2]

 

2.2 Project success

The Oxford Advanced Learner's Dictionary [4] defines 'success' as "to achieve what was intended". It can thus be said that a project is successful when its goal has been achieved. There are several criteria, but they almost always include meeting requirements on time and within budget, as well as meeting quality requirements [8].

Project success is difficult to measure and to define, as it is dependent on a person's perception and perspective. Ika [6] is of the opinion that there is probably no such a thing as 'absolute success' in project management; there is only 'perceived success of a project', and how success is evaluated could change over time. The concept of success is ambiguous, inclusive, and multidimensional, and its definition is related to a specific context. Jugdev & Müller [9] agree that success means different things to different people; the personal objectives of individuals lead them to judge the success of projects differently, and what one person perceives as a successful project can be a failure in another person's eyes.

According to Kendra & Taplin [10], project management success is dependent on the following four dimensions:

  • The skills and competencies of the project manager;
  • Organisational structure;
  • Measurement systems; and
  • Management practices that represent an organisation's culture.

It can be concluded that project success is subjective, perceived, and difficult to measure. It is influenced by a variety of factors, including, but not limited to, formal project management practices, skills and competencies of the project manager and other team members, organisational culture, good communication, and support from senior management.

In this study project success was self-defined by the respondents, who identified project success within their unique environments and contexts.

2.3 The influence of maturity on project outcome

Mullaly & Thomas [11] point out that there seems to be a relationship between maturity and performance, but that no statistically significant correlations exist to prove it. Nieto-Rodriguez & Evrard [12], from a consultancy firm, indicate that project failures are often the result of organisational aspects beyond the influence of the project manager; and they claim that a higher level of organisational maturity enhances project performance.

According to Nicholas et al. [8], a higher level of project management maturity does not necessarily guarantee project success. Labuschagne et al. [2] also found no significant correlation between project success and the maturity level of an ICT organisation in South Africa. This finding supports the notion that projects can be successful despite the maturity level of the organisation.

Based on the above reports, there seems to be no consensus on whether a higher maturity level leads to project success or not.

2.4 Maturity levels of organisations

The majority of organisations are at the second level of the PMMMs, with almost all of the remaining organisations at the first or third level [13, 14]. Labuschagne et al. [2] found in their study of ICT organisations in South Africa that the highest number of organisations perceived themselves to be at level 3, with the second most placing themselves at level 2. Most organisations were perceived to be at maturity levels 1 to 3, which supports the findings of Spundak et al. [13] and of Grant et al. [14].

Cooke-Davies and Arzymanow [3] researched the variation between different industries, and found that the petrochemical and defence industries were the most developed.

2.5 Project size and project success

Labuschagne et al. [2, 15] found that, in general, small projects in the IT environment in South Africa tended to fail more often than larger ones, due to the fact that formal project management processes are sometimes not followed on the smaller projects. Organisations tend to invest more effort in bigger projects, as their associated risks are higher. This is in line with the findings of Papke-Shields et al. [16], who found evidence that larger, more expensive projects had more at stake for the organisation, and therefore greater control was exercised in terms of time, cost, and integration, as well as formal quality and risk management practices.

2.6 Project management knowledge areas

The PMBOK® Guide [17] is probably the most popular of several available project management standards. It claims to be a summary of the collective knowledge within the profession of project management, and it is published and reviewed every four years by the Project Management Institute (PMI). It defines the following nine project management knowledge areas:

  • scope management
  • time management
  • cost management
  • quality management
  • human relations management
  • communications management
  • risk management
  • procurement management, and
  • integration management.

Project success is often measured by the 'iron triangle' criteria of cost, quality, and time. The application of the nine knowledge areas is believed to have a major influence on achieving these criteria.

 

3. HYPOTHESES

In order to achieve the abovementioned objectives, the following 14 hypotheses were tested (where project management maturity and project success are perceived by the respondents):

H11:Mature project management organisations produce more successful projects than less mature project management organisations.

H21:Large projects are more successful than small projects.

H31: Project management organisations with mature project integration management practices produce more successful projects than project management organisations with less mature project integration management practices.

H41: Project management organisations with mature scope management practices produce more successful projects than project management organisations with less mature scope management practices.

H51: Project management organisations with mature time management practices produce more successful projects than project management organisations with less mature time management practices.

H61: Project management organisations with mature cost management practices produce more successful projects than project management organisations with less mature cost management practices.

H71: Project management organisations with mature quality management practices produce more successful projects than project management organisations with less mature quality management practices.

H81: Project management organisations with mature human resource management practices produce more successful projects than project management organisations with less mature human resource management practices.

H91: Project management organisations with mature project communication management practices produce more successful projects than project management organisations with less mature project communication management practices.

H101: Project management organisations with mature risk management practices produce more successful projects than project management organisations with less mature risk management practices.

H111: Project management organisations with mature project procurement management practices produce more successful projects than project management organisations with less mature project procurement management practices.

H121: Project management organisations with project managers with adequate competencies produce more successful projects than project management organisations with project managers with inadequate competencies.

H131: The perceived level of maturity of the engineering and construction projects correlates positively with the perceived level of maturity of South African IT projects in 2008 as reported by Labuschagne et al. [2].

H141: The success rate of the engineering and construction projects correlates positively with the success rate of South African IT projects in 2008 as reported by Labuschagne et al. [2].

 

4. RESEARCH METHODOLOGY

In order to be able to compare results with previous studies [1, 2], a survey questionnaire developed by Sonnekus et al. [1] was used in this study. This questionnaire mapped the nine knowledge areas of the PMBOK® [17] on to a PMMM based on various maturity models. Respondents were asked to reflect on the outcomes of projects in their organisations, and to examine recent projects in terms of outcomes. The questionnaire consisted of 15 questions. It was hosted electronically, and invitations to participate were distributed via email.

The invitation to complete the electronic survey was distributed to 1,625 individuals who had studied at the University of Pretoria; 255 responses were received. Thus 15.69% of those approached responded to the invitation to participate.

The data gathered were analysed with the help of SPSS, a statistical software package. In order to analyse the data, the following statistical tests were performed:

  • Reliability analysis (Cronbach's Alpha).
  • Descriptive statistics to describe the group profile.
  • Hypothesis testing: Kruskal-Wallis tests, Mann-Whitney U tests, Chi-square, post-hoc tests, t-tests, and p-values.

 

5. RESULTS

5.1 Descriptive statistics

Respondents who had studied at the University of Pretoria, and who came from South Africa and from some other African countries, participated in the survey. A total of 255 responses were received, and 273 projects were reported on. According to the respondents, the majority of projects were executed in South Africa (236), with the second-highest number of projects in Botswana (12). It should be noted that not all the responses were completed in full, and that some respondents did not complete certain sections of the questionnaire.

Respondents came mainly from the engineering and construction environment, as can be seen in Figure 2.

 

Figure 2: Industries in which respondents have been involved in projects

 

For the purposes of this study the three categories of project outcome were described in the questionnaire as follows:

  • Failed: A project that is never completed or does not meet customer requirements. It delivers very little value or no value at all.
  • Challenged: A project that is completed, but is late, over budget, or does not meet all the requirements. It delivers moderate value; less than what was anticipated.
  • Successful: A project that is delivered on time, within budget, within scope, and complies with the quality requirements. It delivers strong value; the expected value.

The majority of projects (46%) were perceived as successful, 36% as challenged, and the minority (18%) as failures.

The majority of respondents (31.9%) perceived their organisation's project management maturity, on average, at level 3, with 27.6% at level 2. Most organisations (71.3%) are perceived to be at maturity levels 1 to 3. The average perceived maturity is 2.88. Labuschagne et al. [2] found that the average perceived maturity of South African IT organisations was 2.97.

5.2 Hypothesis testing

Because parts of the study consisted of small subgroups, it was decided to use non-parametric tests for hypotheses 1 to 12. As adequate data were available for hypotheses 13 and 14, they were tested by parametric statistics.

5.2.1 Testing of hypotheses 3 to 11

The scores of the sub-questions in the questionnaire pertaining to hypotheses 3 to 11 were added together for each respondent, after which the average score was calculated for each question. The averages of the respondents were then grouped into five categories for each question. 'Not applicable' was treated as 'missing'. The grouping was done as outlined in Table 1.

 

Table 1: Categories for questions

 

If the Kruskal-Wallis Test indicated that there were significant differences in the mean percentages of successful projects, the Mann-Whitney U Test was used to perform multiple comparisons (pare-wise comparisons). It was decided beforehand to test for differences across levels 1-4, 1-5, 2-4, 2-5 and 3-5; hence the level of α=0.05 was adjusted to α=0.01

5.2.2 Reliability testing

A Cronbach Alpha of 0.7 or higher indicates that respondents have answered the items in a consistent way, and it is thus an indicator of reliability. Table 2 indicates that all the questions in the questionnaire pertaining to the nine knowledge areas have a good reliability.

 

Table 2: Cronbach's Alpha test for the knowledge areas

 

Table 3 outlines the results and interpretations of the hypotheses testing, as well as the statistical measures that were used. The statistical measures and tests used in the study are described elsewhere.

 

Table 3: Results of statistical hypothesis testing

 

6. CONCLUSION AND RECOMMENDATION

6.1 Outcome of African engineering and construction projects and the perceived level of maturity of organisations

The majority of projects were perceived by the respondents as successful and the minority as failures.

Project management organisations had an average perceived level of maturity of 2.88, and the majority of organisations were at level 3. Most organisations were perceived to be at maturity levels one to three, which supports the findings in other environments, e.g. those of Spundak et al. [13], Pretorius et al. [18, 19], Labuschagne et al. [20], and Grant et al. [14].

6.2 The relationship between project management maturity and project outcome

The study failed to establish any correlation between the project management maturity of an organisation and the perceived outcome of the projects that it produces. This finding is in line with Nicholas et al. [8], Pretorius et al. [19], and Labuschagne et al. [2]. They all claim that higher project management maturity does not automatically lead to project success; projects can be successful despite the maturity level of the organisation.

This finding could be an indication that project success is dependent on factors other than standardised practices implemented by the project office. The factors that could influence project success might include:

  • Organisational culture [21]
  • The competence level of the least competent project team member [22]
  • The size of the project [16], and
  • The competence of the project manager [9].

Additional empirical testing is necessary to gain more knowledge about the connections between project success and the above factors.

6.3 The relationship between project size and project outcome

The hypothesis testing failed to find a correlation between the size of a project and its perceived outcome. This is contrary to the findings of Papke-Shields et al. [16], Pretorius et al. [19], and Labuschagne et al. [2]; they all found that bigger projects tend to be more successful.

It therefore seems that the situation pertaining to the engineering and built environment projects investigated in this study differs from project management in the USA as well as from the ITC industry in South Africa. A possible explanation for this phenomenon could be the fact that African engineering and construction organisations invest more appropriate efforts, funds, and external resources in both small and large projects. Another explanation could be that large construction projects in Africa experience unique challenges that make it difficult for smaller ones to achieve better results.

6.4 The impact of the application of the nine PMBOK® knowledge areas to project outcome

It was found that the following PMBOK® [17] knowledge areas correlate positively with project outcome:

  • Integration management (H31)
  • Scope management (H41)
  • Time management (H51)
  • Cost management (H61)
  • Human resource management (H81)

The hypothesis testing indicated no significant correlation between the following PMBOK® [17] knowledge areas and project outcome:

  • Quality management (H70)
  • Communication management (H90)
  • Risk management (H100)
  • Procurement management (H110)

Scope-, time-, cost- and quality management are 'core functions', while human relations, communications, and risk and procurement management are 'facilitating functions' according to PMBOK® [17]. In this study the majority of knowledge areas that were found to have a direct relationship with project outcome were 'core functions', and the bulk of areas that had no significant correlation with project outcome were 'facilitating functions'. The only exceptions are human resource management (a facilitating function where maturity correlates with project outcome) and quality management (a core function that was found not to correlate with project outcome). Respondents probably realise the important role of aspects such as leadership and teamwork, which are often mentioned in the literature as being essential for project success.

According to Watson & Korukonda [23], "as quality management becomes embedded in more and more organisations, it has come to mean different things to different people". In the industries that were studied in this report, it could be that, due to the nature of the projects, quality management principles and measures have been so entrenched in the company's work ethos and standard operating procedures, that project managers do not even realise that they are applying them in their projects. This might have led to bias regarding this knowledge area.

Not all projects require significant procurement work. This might also have led to bias in the responses regarding procurement management.

6.5 The influence of the competency of project managers on the outcome of projects

The study found no relationship between the competency of project managers and the outcome of projects. This supports the notion of Kendra et al. [10] that project management success is dependent on four dimensions, of which the skills and competencies of the project manager are only one.

6.6 Maturity in the engineering and construction sector versus maturity in the IT sector

No difference between the average perceived maturity levels of companies in the South African IT environment in 2008 and the engineering and construction sector were found in the study; the engineering and construction industry compared favourably with the IT industry in terms of overall maturity level.

Cooke-Davies et al. [3] found that 'industries of origin' are more mature in project management than industries that adopted the discipline more recently. Construction and engineering can be considered industries of origin, and therefore higher maturity could have been expected in these sectors than in the IT sector.

In this study no difference could be found in the maturity levels of the two industries. This could be due to the fact that Labuschagne et al. [2] did their research in South Africa, whereas this study on the engineering and construction sectors was conducted in South Africa and in other parts of Africa. Project management companies in the rest of Africa are generally less experienced than South African project management companies.

6.7 Success rate in the engineering and built environment sector compared to projects in the IT sector

The study found a significant difference between the average percentage of completed projects that were successful in the South African IT sector and the African engineering and construction industry. The IT industry had a higher percentage of successful projects in 2008.

A possible explanation for this could be that Labuschagne et al. [2] researched only South African IT companies, whereas this study had respondents from South Africa and from other parts of Africa. South African project companies tend to be more experienced and therefore more successful in their execution of projects. Failure is also more obvious in engineering and construction projects than in IT projects.

6.8 Recommendations

Further research is necessary in order to determine why risk management had no influence on the outcome of engineering and construction projects in this study. According to Royer [24], "unmanaged or unmitigated risks are one of the primary causes of project failure". Thompson and Perry [25] say that if risk management is not exercised, the result is poor performance with increased cost and time delays. This particular finding of the study thus seems to contradict conventional wisdom.

6.9 Shortcomings of the study

The questionnaire consisted of 15 questions, and the nature of some questions was very repetitive. Respondents normally do not have much time to spend on long questionnaires; and this might have led to some respondents completing only some of the questions.

The respondents identified project success from their unique environments and contexts. It could be argued that the customer's perspective of the outcome of the project should also be taken into account to provide a more objective picture of the real situation. Due to the fact that an existing questionnaire was used, this was not possible for this study. This should, however, be addressed in future studies.

 

REFERENCES

[1] Sonnekus, R. & Labuschagne, L. 2003. The Prosperus Report 2003: ICT project management maturity versus project success in South Africa. Johannesburg, Rand Afrikaans University.         [ Links ]

[2] Labuschagne, L. & Marnewick, C. 2009. The Prosperus Report 2008. IT Project Management Maturity vs. Project Success in South Africa. Project Management South Africa, South Africa.         [ Links ]

[3] Cooke-Davies, T.J. & Arzymanow, A. 2003. The maturity of project management in different industries: An investigation into variations between project management models. International Journal of Project Management, 21, pp 471-478.         [ Links ]

[4] Oxford Advanced Learner's Dictionary of Current English. 2001. 6th ed. Oxford: University Press.         [ Links ]

[5] Andersen, S.A. & Jessen, S.A. 2002. Project maturity in organisations. International Journal of Project Management, 21, pp 457-461.         [ Links ]

[6] Ika, L.A. 2009. Project success as a topic in project management journals. Project Management Journal, 40(4), pp 6-19.         [ Links ]

[7] Organizational Project Management Maturity Models, http://www.acis.org.co [accessed 10/12/10]         [ Links ].

[8] Nicholas, J.M. & Steyn, H. 2008. Project management for business engineering, and technology. Principles and practice. 3rd ed. Burlington: Butterworth-Heinemann.         [ Links ]

[9] Jugdev, K. & MUller, R. 2005. A retrospective look at our evolving understanding of project success. Project Management Journal, 36(4), pp 19-31.         [ Links ]

[10] Kendra, K. & Taplin, L.J. 2004. Project success: A cultural framework. Project Management Journal, 35(1), pp 30-45.         [ Links ]

[11] Mullaly, M.E.M. & Thomas, J. 2010. Re-thinking project management maturity. Perspectives gained for explorations of fit and value. Project Management Institute Inc.         [ Links ]

[12] Nieto-Rodriguez, A. & Evrard, D. 2004. Boosting business performance through programme and project management. A first goal survey on the current state of project management maturity in organisations across the world. PriceWaterhouseCoopers.         [ Links ]

[13] Spundak, M. & Striga, K. 2010. Project management maturity of Croatian companies: Is there any? Project Management Institute Inc.         [ Links ]

[14] Grant, K.P. & Pennypacker, J.S. 2006. Project management maturity: An assessment of project management capabilities among and between selected industries. IEEE Transactions on Engineering Management, 53(1), pp 59-68.         [ Links ]

[15] Labuschagne, L., Marnewick, C. & Jakovljevic, M. 2008. IT Project Management Maturity: A South African Perspective. Proceedings of the PMSA Conference 2008: From Strategy to Reality, Midrand, South Africa.         [ Links ]

[16] Papke-Shields., K.E., Beise, C. & Quan, J. 2010. Do project managers practice what they preach, and does it matter to project success? International Journal of Project Management, 28, pp 650-662.         [ Links ]

[17] Project Management Institute, Inc. 2008. A guide to the project management body of knowledge (PMBOK® Guide). Newtown Square, Pennsylvania, USA.         [ Links ]

[18] Pretorius, S. 2011. Project management maturity versus project management success in the engineering and built environment: An African perspective. Dissertation in partial fulfilment of the requirements for Masters in Project Management, University of Pretoria.         [ Links ]

[19] Pretorius, S., Steyn, H. & Jordaan, J.C. 2011. Project management maturity versus project management success in the engineering and built environment: An African perspective. Industrial Engineering, Systems Engineering and Engineering Management (ISEM) Conference, Stellenbosch, South Africa.         [ Links ]

[20] Labuschagne, L. et al. 2012. Project management maturity for project success in South Africa 2010. PMSA. In press.         [ Links ]

[21] Yazici, H.J. 2010. Role of project maturity and organizational culture on project success. PMI Research Education Conference, Washington, D.C.         [ Links ]

[22] Berger, M.E. 2010. Contribution of Individual Project Participant Competencies to Project Success. Project Management Institute Inc.         [ Links ]

[23] Watson, J. & Karukonda, A. 1995. The TQM jungle: A dialectical analysis. International Journal of Quality and Reliability Management, 12(9), pp 100-109.         [ Links ]

[24] Royer, P.S. 2000. The undiscovered dimension of project management. PM Network, 14, pp 31-40.         [ Links ]

[25] Thompson, P.A & Perry, J.G. 1992. Engineering construction risks: A guide to project risk analysis and risk management. London: Thomas Telford.         [ Links ]

 

 

* Corresponding author.
# This article is an extended version of a paper presented at the 2011 ISEM conference
1 The author was enrolled for the MSc (Project Management) degree at the Graduate School of Technology Management, University of Pretoria.

Creative Commons License Todo o conteúdo deste periódico, exceto onde está identificado, está licenciado sob uma Licença Creative Commons