Linking trust and collaboration in project teams to project management success

Purpose – The purpose of this paper is to emphasise the importance of high levels of trust and collaboration for increasing the likelihood of project management (PM) success. However, the link between these three constructs remains unclear. Design/methodology/approach – In this study, the authors use structural equation modelling (SEM) based on the findings from an international survey of 151 project practitioners to demonstrate the significance of project team trust and collaboration for increasing the likelihood of PM success. Findings – The results indicate that PM success becomes more likely as the degree of collaboration improves which, in turn, is influenced by an increase in the level of trust between team members. The two factors of PM success are project performance and knowledge integration and innovation. The six factors of the degree of collaboration that were studied are physical proximity, commitment, conflict, coordination, relationships and incentives. The three factors of the level of trust investigated are expectations, knowledge exchange and imported trust. Practical implications – The results of the study are expected to provide insight for project practitioners to increase the likelihood of PM success by taking cognisance of the factors that influence collaboration and trust. The results of the study may also provide insight into teaching and learning in tertiary education, in terms of professionalism and integrity issues. Originality/value – This paper presents a new perspective for investigating PM success. SEM techniques are used to determine the likelihood of PM success by promoting trust and collaboration in the project team. This unique approach highlights the “human factors” that influence perceived PM success which should benefit both researchers and practitioners.


Introduction
The constituents of project success have been widely researched (Andersen et al., 2006;de Carvalho et al., 2015;Pinto and Slevin, 1988). The prevalent interest in project success is due to the increasing efforts (and resources) that companies are expending to implement project management (PM) (de Carvalho et al., 2015).
PM literature frequently associates project success with measures of cost, time and quality, also known as the "iron triangle" (Atkinson, 1999;Berssaneti and Carvalho, 2015).

Literature review
Practitioners and researchers place a great deal of emphasis on achieving the objectives of the "iron triangle" of PM success (Agarwal and Rathod, 2006;Fortune and White, 2006;Turner and Cochrane, 1993) and focus less on the human-related aspect of projects which are woven into the very fabric of all the success factors that have been identified in literature (Cooke-davies, 2002). It is people who deliver projects, not processes and systems (Cooke-davies, 2002). A discussion of the human-related aspects of the PM success framework is important as it can be applied in most project contexts.
Linkages between project trust, collaboration and PM success have been purported (Buvik and Rolfsen, 2015;Holton, 2001;Manu et al., 2015). Two Australian studies, which were based on two different surveys of 57 and 50 alliancing subject matter experts, respectively, resulted in the development of models and a taxonomy that places collaboration as pivotal in building trust for effective information and knowledge sharing (Davies et al., 2016;Walker and Lloyd-Walker, 2015). In contrast, Buvik and Rolfsen (2015) and Daspit et al. (2013) found that cross-functional teams are dependent on the degree of trust between them to engage in collaborative interaction, as trust was identified as an important component of teamwork (Webber, 2008). Trust is recognised as a key factor contributing to project success (Wong et al. in Buvik and Tvedt, 2017). Handy (1995) found that the ability to work collaboratively is recognised as a core competency of a learning organisation or team, but that trust determines the dynamic of this collaboration.
Collaborative learning as the basis for effective organisational team building requires a level of personal familiarity, intimacy and trust (Holton, 2001). In the construction industry, the sentiment is the same, a trust-based collaborative environment is required to facilitate high levels of information sharing and to secure commitments of the supply chain from the very early stages of a project (Manu et al., 2015). However, Manu et al. (2015) point out that significant research attention is still required on how to achieve trust-based collaboration in the construction supply chain. As literature offers stronger support for trust determining the degree of collaboration, this is also the direction of the relationship proposed in the model (Figure 1). Müller (2003) established that communication improves project member collaboration and trust. Similarly, Bond-Barnard et al. (2014) found theoretical support for the proposition that, based on a foundation of quality communication, project trust and collaboration influence PM success. The authors acknowledge that quality communication is required for trust and collaboration in the project to thrive. However, this paper does not investigate the influence of

435
Trust and collaboration in project teams communication as a success factor in much detail as the focus in this paper is on the relationship between (and factors influencing) trust, collaboration and PM success. Based on the fact that literature purports and that these human project success factors are actually constructs, a conceptual diagram of the structural model is presented in Figure 1 depicting the link between trust, collaboration and PM success based on literature, and the various factors/ variables influencing each construct. The arrow represents the direction of proposed influences in the structural model. The corresponding hypotheses are as follows: H1. PM success becomes more likely as the degree of collaboration increases.
H2. The degree of collaboration increases as the level of trust in the project increases.
The intent of this paper is to measure the perceptions of clients, project leaders, team members and other stakeholders to determine which factors influence the level of trust and degree of collaboration by using confirmatory factor analysis (CFA) and SEM. The literature used to identify the factors for each construct are briefly discussed below, and Table AI provides more information as to how these factors were measured.

Level of trust construct
Trust can be defined as a function of the predictability and expectations of others' behaviours or a belief in others' competencies, which affects performance through activation of cooperation (Tyler, 2003) or other collaborative processes (Chiocchio et al., 2011a). When there is trust, people ask for help, speak openly and honestly, take risks, accept new challenges and carry out their activities with less anxiety and stress (Carvalho, 2008;Fox, 2001). Following a comprehensive literature review, it was decided to only focus on the following factors that influence trust, namely, the degree of knowledge exchange, dealing with uncertainty (risk) and meeting team members' expectations. 2.1.1 Knowledge exchange factor. Knowledge exchange is the push and pull found in the multiple, directional movement of data, information and knowledge between individuals and groups for mutual benefit (Levesque, 2005). Trust between the project team and the stakeholders or between any two or more stakeholders/team members is earned by doing what one says one will do on a continued, repeated basis. Trust develops from repeatedly receiving and sending project information across various formal and informal channels of communication which infers a level of reliability in the modality as well (Lesko and Hollingsworth, 2010).
For initial knowledge exchange to take place, some trust must exist between the team members so that information can flow along the agreed upon and appropriate lines of communication (Lesko and Hollingsworth, 2010). For this reason, Daim et al. (2012) state that it is important that the project manager promotes knowledge exchange by leading by example. He can do so by importing trust in the team or at the inception of the project through team member introductions that are positive and explain an individual's role and importance to the team. Knowledge exchange is a process that builds trust between the individuals or groups that are exchanging knowledge. In so doing, the level of trust in the project and in project relationships continues to grow.
2.1.2 Imported trust factor. "Swift trust" according to Daim et al. (2012), refers to the situation whereby members of a global virtual team (GVT) import trust from other familiar settings. Members initially employ category-driven information processing in forming stereotypical impressions of others. Thereafter, trust is maintained by a high level of action within the teams. High levels of action promote members' confidence that the team is able to manage uncertainties, risk and vulnerabilities. This type of trust is different than the traditional concepts of trust, since swift trust imports trust instead of developing trust over time via interpersonal relationships. As a result, Daim et al. (2012) state that maximum amount of "swift trust" is usually achieved at the project's inception.
In contrast, Meyerson et al. (1996) state that swift trust is category-driven trust, between highly specialised professionals where the actors deal with one another more as roles than as individuals. Expectations, consequently, are more standardised and stable and defined more in terms of tasks than personalities: "We trust engineers because we trust engineering and believe that engineers are trained to apply valid principles of engineering" (Dawes in Meyerson et al., 1996).
Literature supports Meyerson et al.'s (1996) definition of swift trust (Dietz and Hartog, 2006;Grabher, 2002;Mumbi and McGill, 2008;Mumbi, 2007). For this reason, it is proposed that the trust that Daim et al. (2012) refer to above should actually be defined as "imported trust". Imported trust stems from team members introducing trust into a new project based on previous interactions. Imported trust differs from swift trust in that swift trust is a category-driven trust where actors have usually not met each other before but decide to trust one another based on the other actor's specialised role and existing competencies which are required to achieve the objectives of the project. Imported trust as defined by Daim et al. (2012) will be investigated in this paper. Specifically, its influence on the level of trust experienced by project team members. It is proposed that imported trust influences the level of trust in the project team if some (or all) the team members have previously interacted with each other, worked together or had a personal relationship.
2.1.3 Expectations factor. A factor in promoting trust and cooperation is the anticipation of future association (Daim et al., 2012). Trust between project stakeholders is earned by doing what one says one will do on a continued, repeated basis (Lesko and Hollingsworth, 2010). The realisation of expectations is important for the development of trust (Chiocchio et al., 2011a;Tyler, 2003). For example, broken promises on likely availability of design information is an important issue in the construction industry which leads to the breakdown of trust (Lesko and Hollingsworth, 2010;Rounce, 1998). This is because trust between project stakeholders is earned by doing what one says one will do on a continued, repeated basis (Lesko and Hollingsworth, 2010).
2.1.4 Risk factor. Risk is an uncertain event or condition that, if it occurs, may have a positive or negative effect on a project's deliverables (PMI, 2017). As the relationship between risk and trust is reciprocal, an acceptable degree of risk is responsible for an increase in the level of trust in a project. In the literature, one of the major reasons for the failure of GVT is related to building trust. Trust is crucial in any GVT as it allows people to engage in risk-associated activities that they cannot control or monitor (Daim et al., 2012). Therefore, risk can either positively or negatively influence the level of trust in a project team.

Degree of collaboration construct
Collaboration and cooperation are interchangeable terms which are defined as a recursive process where people or organisations work together in an intersection of common goals by sharing knowledge, learning and building consensus (Dietrich et al., 2010). Collaboration can occur between individuals, between organisations or between an organisation and its customers. Only interpersonal collaboration is considered here. To better understand how one can promote interpersonal collaboration in a project team, it is important that one is aware of the influence that various factors have on the degree of collaboration (Dodgson, Hoegl et al. in Dietrich et al., 2010;Jap, 1999;Mohr and Spekman, 1994).
According to Tyler (2003), trust affects performance through activation of cooperation or other collaborative processes. Trusting teams enhance cooperative and collaborative processes, which assist them to better manage the interdependencies among their respective areas of expertise. In addition, the interplay of situation-appropriate teamwork, communication, synchronicity and coordination has also been found to increase 437 Trust and collaboration in project teams collaboration in the project which is a factor of team performance (Chiocchio et al., 2011a;Kozlowski and Bell, 2003;LePine et al., 2008). High-quality collaboration in projects is characterised by cohesion which is defined as the collaborative spirit between actors (Dietrich et al., 2010;Hoegl and Gemuenden, 2001) and the resultant of all forces acting upon members to remain in the group (Festinger in Lin and Peng, 2010). Cohen and Bailey (1997) found that cohesion is one of the key issues that determine the individual's willingness to engage in collaboration. However, as cohesion is not frequently mentioned as a collaboration factor it was excluded from the study. At an individual and team level, collaborative work predicts task and team performance (Chiocchio et al., 2011a). Following a comprehensive literature review, it was decided to only focus on the following factors that influence the degree of collaboration in a project team, namely, relationships, coordination, proximity, commitment, conflict and incentives. These factors are discussed in more detail below. 2.2.1 Relationships factor. A relationship is a way in which two or more people or things are connected, or the state of being connected (Oxford University Press, 2017). Relationships are important in projects mainly because they form the basis for collaboration in the team which ultimately influences project performance. Research on the relations between project actors and their effect on project performance is widely researched (Ahola, 2009;Artto et al., 2008;Dietrich et al., 2010). Most of the literature, however, focusses only on collaboration in customer-supplier relationships specifically in the construction industry (Bresnen, 2007;Dietrich et al., 2010;Errasti et al., 2007). Collaboration processes improve the relationships between individuals or organisations. However, the nature of these relationships may vary depending on their strength (Granovetter in Dietrich et al., 2010). Successful collaboration induces hope and expectation within the team members for future collaborations which provide motivation in partnering relationships (Bresnen and Marshall, 2000;Dietrich et al., 2010). There are several challenges involved in establishing organisational project relationships: • discontinuity of demand, i.e., infrequent projects lead to difficulty increasing the level of trust and commitment in the project team (Eloranta, 2007); To encourage the development of relationships or social capital in projects, it is important to promote collaborative practises which involve the exchange of knowledge between team members (Dietrich et al., 2010). Uzzi in Dietrich et al. (2010) describe relationships in which organisations operate in a truly collaborative mode to achieve a common goal or gain mutual benefits, as embedded relations which are generally characterised by trust and commitment.
2.2.2 Coordination factor. High-quality coordination is defined by Hoegl and Gemuenden (2001) as the shared understanding of mutual goals, related activities, interdependencies between the activities and the status of member contributions. Coordination is one of the factors that determine the quality of collaboration (Bedwell et al., 2012;Chiocchio et al., 2011a;Dietrich et al., 2010;Hoegl and Gemuenden, 2001;LePine et al., 2008). High coordination is a prerequisite for fluent interactions in collaborative settings and ensures harmonised and synchronized co-action (Dietrich et al., 2010). Coordination in projects is mainly used to align the team with the project goal. Congruent or collaborative goals weaken conflicts and increase the quality of collaboration (O' Leary-Kelly et al., 1994;Pinto et al., 1993) as well as increasing the exchange of knowledge between members (Tjosvold in Dietrich et al., 2010). Coordination is often perceived to be a way in which the project team and the project outcomes can be controlled to meet expectations. Martín-Rodríguez et al. (2005) add that communication and coordination mechanisms, policies, protocols and standardised documentation may benefit collaborative processes. For example, Pinto et al. (1993) examined inter-unit collaboration in projects and found that team rules improve the collaboration. Similarly, the results of Silén-Lipponen et al. (2002) show that rules and procedures represent an important role in coordination and collaboration between professionals. Norms regarding the rules and procedures that must be followed in a project increase the predictability of collaborative actor behaviour. High-quality collaboration requires each participant to accept and respect required effort norms (Dietrich et al., 2010). When the team collaborates by coordinating their efforts, the cost of controlling and the probability of failure is reduced (Ahola, 2009;Dubois and Gadde, 2000;Ingram and Baum, 2001).
2.2.3 Proximity factor. Project team-based collaboration often spans across national borders and/or between organisations. Studies have shown the positive effects of physical proximity on collaborative behaviour (Dietrich et al., 2010). Physical proximity is defined as nearness in space and in the context of projects, proximity refers to the physical distance between project team members. Van den Bulte and Moenaert (1998) examined R&D team co-location and found a positive relationship between co-location and the frequency of communication. Other empirical studies have shown that co-locating people enables informal communication, enhances the creation of shared understanding and increases cohesion between collaborative actors (Kahn and McDonough, 1997;Moodysson and Jonsson, 2007;Pinto et al., 1993). A study by Arslanian-Engoren in Dietrich et al. (2010) confirms this by stating that physical proximity has a positive effect on collaboration.
2.2.4 Commitment factor. Commitment is characterised by the acceptance of and strong belief in the goals and values of the project, the willingness to engage in the project and the desire to maintain membership in the project (Hoegl et al., 2004). In projects, commitment is one of the key success factors for interpersonal and interorganisational collaboration (Buvik and Rolfsen, 2015;Dietrich et al., 2010;Herscovitch and Meyer, 2002;Mohr and Spekman, 1994). According to Bresnen and Marshall (2000), an actor's commitment to project tasks increases the collaboration quality. Hoegl et al. in Chen et al. (2010) found that commitment also has a positive effect on teamwork quality in product development projects. Empirical studies prove similar results in cross-disciplinary collaboration in a hospital context (Liedtka and Whitten in Dietrich et al., 2010). Furthermore, Vandenberghe et al. (2004) found that commitment has a direct and indirect effect on job performance through commitment to the supervisor and organisational commitment, respectively. Commitment increases a collaborator's genuine interest to participate, engage in mutual support, and sets actors' priorities to favour the collaborative task at hand (Dietrich et al., 2010).
2.2.5 Conflict factor. Some researchers argue that conflicts are "characteristic" of collaborative projects and should be managed by formal and informal governance mechanisms or coordination to strengthen the relationship between the collaborating actors (Vaaland, 2004). It is important to address conflict in a project as the increased complexity and diversity of the technical workforce in teams will increase workplace tensions (Dietrich et al., 2010;Farris and Cordero, 2002). The relationship between conflict resolution and collaboration has been tested in empirical studies. For example, Tjosvold et al. (2003) showed that a positive attitude to conflict is positively related to collaborative interaction in teams. Some studies have found a negative relationship between conflict and collaboration (Duarte and Davies in Dietrich et al., 2010), while others also emphasise the positive aspects of conflicts (Vaaland and Håkansson, 2003) as task conflict has a beneficial effect on the performance of decision-making teams (O'Neill et al., 2013). De Dreu and Weingart (2003) executed meta-analysis on the effects of relational and task conflicts on team performance and team member satisfaction and found that both of these conflict types are negatively 439 Trust and collaboration in project teams related to team performance and team member satisfaction. These findings strengthen the notion that resolving conflicts has a direct positive effect on collaboration quality (Dietrich et al., 2010;O'Leary-Kelly et al., 1994;Pinto et al., 1993). 2.2.6 Incentives factor. Incentives are things that motivate or encourage someone to do something and are often used in projects to boost project team performance and collaboration (Oxford University Press, 2017). According to Dietrich et al. (2010), the alignment of incentives is one of at least eight interrelated issues that impact directly on the fluency of collaboration between different project actors. To guarantee that each of the collaborating actors support the achievement of the common goal and to ensure that mutual support exists between them, the incentives of the different actors should be aligned. When Faerman et al. (2001) studied public-private collaboration, they found that the alignment of incentives served as one of the most important issues that related to success of the collaborative process. Similarly, Dietrich et al. (2010) state that alignment of incentives are an important factor for effective collaboration. A study by Bresnen and Marshall (2000) reveals, however, that most of the incentive systems used in projects do not provide expected motivation for collaborating actors. They advise, therefore, that individual differences, social relations and a balance between extrinsic and intrinsic rewards and incentives must be considered to improve the degree of collaboration in the project.

PM success construct
Success can mean different things to different people (Freeman and Beale in Jugdev and Müller, 2005). The requirements of each project stakeholder will differ and, therefore, their perception of what constitutes success will vary. The stakeholder's satisfaction with the project is determined as the difference between his perception of the project's success vs his expectations thereof (Koelmans, 2004;Maylor, 2003). A stakeholder's perception of project success can be influenced by issues such as the responsiveness of the team to stakeholder requests, project communication, degree of collaboration and/or trust in the team, etc.
Before the constituents of project success are discussed in more detail, it is important to distinguish between project success (measured against the overall objectives of the project) and PM success (measured against the widespread and traditional measures of performance against cost, time and quality) (Cooke-davies, 2002;De Wit, 1988;Jugdev and Müller, 2005). The second distinction one must make is the difference between success criteria (the measures by which success or failure of a project or business will be judged) and success factors (those inputs to the management system that lead directly or indirectly to the success of the project or business) (Cooke-davies, 2002). The success of a project is not only dependent on how the project performs in terms of its success criteria but it is also dependent on the stakeholders' perception of project success. PM success is measured by "things-related" criteria such as the budget, schedule and quality of the project deliverable (hereafter collectively referred to as project performance) and "people-related" criteria such as communication, trust and collaboration which determine the team morale and stakeholder satisfaction in the project, amongst others (Koelmans, 2004). Furthermore, literature states that there is an additional construct, knowledge integration and innovation that influences PM success by bridging the gap between the "things-related" and "people-related" factors. Both project performance and knowledge integration and innovation are discussed in more detail below. Several factors that are beyond the scope of this paper can also influence PM success. These include for example the level of risk accepted, the match between organisational capabilities and project requirements and several aspects of the planning process.
2.3.1 Project performance factor. Project performance is concerned with the attainment and continuous measurement of the project determinants, time, cost and quality to establish the project's relative success. These three project measures are concerned with the internal efficiency of PM tasks (Dalcher and Societies, 2009). Project performance is an important determinant of PM success, as the effectiveness of projects needs to be considered on a regular basis throughout the course of the project to establish the project's relative success (Dalcher and Societies, 2009;Mir and Pinnington, 2014).
2.3.2 Knowledge integration and innovation factor. Knowledge integration is a project team or organisation's effective use of the ideas and information available to it (Cambridge University Press, 2017). Innovation involves deliberate application of information, imagination and initiative to derive greater or different values from resources, and includes all processes by which new ideas are generated and converted into useful products (Web Finance Inc., 2017). Knowledge integration and innovation is a product of knowledge exchange/transfer and collaboration which is supported by an environment of trust. Research indicates that an appropriate level of collaboration between customer and supplier reduces the costs of controlling, decreases the probability of failure and creates potential for innovations and learning (Ahola, 2009;Dubois and Gadde, 2000;Ingram and Baum, 2001). Henderson and Cockburn in Dietrich et al. (2010) found that higher project performance was associated with knowledge transfer mechanisms that actively encouraged the exchange of information across organisational units and across organisational boundaries. To achieve PM success, open channels for knowledge exchange need to be available, which allows new external knowledge to be imported and synthesised with existing internal knowledge so that the knowledge can be integrated into the project (Henderson and Cockburn in Dietrich et al., 2010). Knowledge integration and innovation was shown to exert significant positive effects on project performance and proper knowledge acquisition and dissemination was found to be crucial for learning by increasing the variability of project performance (Yang, 2005). Thus, the acquisition and integration of specialized knowledge, especially tacit, influences the outcome of project success (Leonard-Barton in Brady, 2004;Teece et al. in Smyth et al., 2010).
The theoretical link between the constructs trust, collaboration and PM and their factors as discussed above and summarised in Table I are presented as a structural model in Figure 1. The arrow represents the direction of hypothesised influences in the structural model. The corresponding hypotheses are as follows: H1. PM success becomes more likely as the degree of collaboration increases.
H2. The degree of collaboration increases as the level of trust in the project increases.

Research methodology
A questionnaire was designed for respondents to assess the level of trust, the degree of collaboration and the perceived likelihood of PM success they had experienced in the project teams they had participated in. Respondents were asked to rate their response, on a ten-point scale, regarding the relevant factors impacting the constructs and overall success of a project. A sample of the questionnaire is shown in Table AI.
Before undertaking the industry-wide survey, a pilot study was conducted among a six-member project reference group explaining the research intent and the questions in order to validate the contents for accurate translation of the overall model. Based on the feedback received, modifications were made to the content and the organisation of the questionnaire to improve accuracy and number of responses.
Purposive sampling was used. The questionnaire was distributed to the members of five different open and closed PM LinkedIn groups. The questionnaire was also sent to 19 PM experts who were identified from literature and it was circulated to current students 441 Trust and collaboration in project teams and alumni of PM courses. This target population was chosen to ensure that respondents had detailed knowledge of projects and occupied key positions of responsibility within a project environment, i.e., project leaders (i.e. project/programme managers), project team members, project stakeholders (e.g. subcontractor, functional manager, regulatory authority, external party, etc.) and project sponsors/clients. The survey was conducted by means of an online, self-administered questionnaire using Qualtrics. Data were collected from a total of 270 international self-selected respondents working on medium size projects in various industries, for both government and private institutions. Of the 270 responses received only 151 (56 per cent) were valid and complete. Table II shows the profile of the respondents for each of the typical roles in the project in terms of gender, age, field of work and nature of business entity. The valid data set was analysed using IBM SPSS Statistics 22 and its structural equation component AMOS.
Relationships Ahola (2009)  Trust and collaboration in project teams

Model specification and refinements
Analysing the initial SEM posited in Figure 1, based on theoretical expectations and past empirical findings, would have been premature. A SEM model consists of two partsa measurement component and a structural component. A feasible model should be selected based on the recommended goodness-of-fit (GOF) measures of the measurement parts of the model. Only a model that satisfies both theoretical expectations and GOF should be selected for the final SEM analysis that includes the structural regression paths (Doloi et al., 2011;Molenaar et al., 2000). Thus, CFA was first performed for each of the constructs separately to determine their relevance to the model before analysing the complete model.

Modelling the constructs
Typically, CFA and SEM utilise the method of maximum likelihood (ML) to obtain the parameter estimates for the regression weights, the assumptions being that the data are measured on a continuous scale and have a multivariate normal distribution (Byrne, 2010). CFA and SEM estimate a variance-covariance matrix that resembles the sample variance-covariance matrix as closely as possible; however, both variances and co-variances are sensitive to kurtosis. As data become increasing non-normal, the χ 2 value for ML estimation becomes excessively large. This situation encourages researchers to seek further modification of their hypothesised model in an effort to obtain an adequate fit for the data. However, these efforts can lead to inappropriate and nonreplicable modifications to otherwise theoretically adequate models. Second, when sample sizes are small (even in the event of multivariate normality), the ML estimators yield χ 2 values that are somewhat inflated and a greater proportion of the model fails to converge or results in an improper solution. Third, when data are non-normal, fit indexes such as the Tucker-Lewis (1973) index and the comparative fit index (Bentler, 1990) yield values that are modestly underestimated. Finally, non-normality can lead to low standard errors with moderate to severe underestimation, which causes regression paths and factor/error co-variances to be statistically significant although they may not be so in the population (Byrne, 2010). Tests of normality were hence performed to assess whether the criterion for multivariate kurtosis was met. Byrne (2010) states that rescaled kurtosis values greater than or equal to 7 for the variables indicate an early departure from normality. Mardia's normalised estimate greater than 5 is indicative of non-normally distributed data. For the construct level of trust, Mardia's coefficient is 24.5 and for degree of collaboration, it is 63.6. Since the data were measured on a Likert scale and the important assumption of multivariate kurtosis is evidently violated, the method of unweighted least squares (ULS) was used to obtain the parameter estimates. Kaplan in Arbuckle (2008) explains that the ULS method is actually a type of ordinary least squares estimation that minimises the sum of squared differences between sample and model-implied co-variances. All the factors for the level of trust model had positive regression weight estimates except for the factor risk (item 20) that had an estimate of −0.031. This item also had a very small squared multiple correlation of 0.01, i.e., it is estimated that the error variance of risk is approximately 99 per cent of the variance of itself. Therefore, risk as a factor or indicator of the level of trust was not relevant. This is an interesting finding as it contradicts Daim et al. (2012) who state that risk can facilitate the development of high initial and final trust in a team if the members successfully cope with technical uncertainties and take initiative in the project. Risk was consequently removed from the second order CFA for the level of trust, which resulted in all regression weight estimates being positive. The fit indices, displayed in Table III, all met the generally accepted criteria (values W0.95 where 0 indicates no fit and 1 perfect fit).
Before the degree of collaboration was modelled, item 25_1 in Figure 1 (a factor for relationships) was removed as there were too much missing data. The model for degree of collaboration also had positive regression weight estimates and adequate fit indices (Table III).

Estimating the model
Once it was established that a suitable fit was obtained for the level of trust and degree of collaboration, the next step was to estimate the entire model. The standardised regression weight estimates which indicate the relative strength of each specific parameter estimate in the model are given in Table IV. It is important to emphasise the strength of the links between the level of trust and the degree of collaboration (value of 0.768) and degree of collaboration and PM success (value of 0.792). The squared multiple correlations estimates in Table V indicate the strength of association between the parameter and its construct and the fit indices are shown in Table VI.
By eliminating one of the factors, risk, from the degree of collaboration construct, the GOF indices attained the recommended levels. This model was adopted to fit level of trust,

445
Trust and collaboration in project teams degree of collaboration and overall PM success, and is adequately supported based on the essential GOF measures. The GFI index value of 0.96 and the AGFI index value of 0.949 both indicate an acceptable model fit to the data. The standardised root mean residual value is 0.077 which is below the recommended upper limit of 0.08. Furthermore, all the other indices that are routinely reported, namely, normal fit index and relative fit index, have values above 0.9, providing strong evidence that the fit between the measurement model and the data is acceptable (Doloi et al., 2011). The method of ULS does not provide standard errors, hence critical ratios with the corresponding p-values cannot be calculated to assess if parameter estimates differ significantly from zero. In order to evaluate the stability of the parameter estimates, 90 per cent bootstrap confidence intervals were calculated for the model and are provided in Table VII. The procedure of "bootstrapping" is a way to handle multivariate non-normal data (West et al., 1995;Yung and Bentler, 1996;Zhu, 1997). Bootstrapping serves as a resampling procedure by which the original sample is considered to represent the population. Multiple subsamples of the same size as the parent sample are then drawn randomly, with replacement, from this population and provide the data for empirical investigation of the variability of the parameter. From Table VII, it is clear that all coefficients differ significantly from zero, as zero is not included in any of the confidence intervals. Figure 2 depicts the final model after deleting the redundant path (risk as a factor for the level of trust). As hypothesised, all the path coefficients are positive, confirming the relevance of the measured factors in the model. The final SEM results suggest that the level of trust correlates strongly with the degree of collaboration (regression coefficient of 0.823 and standardised regression coefficient of 0.768). The model as a whole accounts for why the endogenous variables, trust and collaboration, co-vary with each other and also with the exogenous variables (Kline, 2010). Furthermore, the degree of collaboration strongly influences PM success with a standardised regression coefficient ¼ 0.792. Expectations was found to have the highest association with the level of trust in a project (standardised regression coefficient ¼ 0.869) and imported trust (with a standardised regression coefficient of 0.497) had the least influence. These findings are aligned with literature as the expectation factor is embedded in the very definition of trust as formulated by Kadefors (2004) and Rousseau et al. (1998), which is that trust is a psychological state Trust and collaboration in project teams comprising the intention to accept vulnerability based upon positive expectations of the intentions or behaviour of another. Similarly, imported trust has in several other instances been found to improve the level of trust in a project team (Grabher, 2002;Meyerson et al., 1996;Mumbi and McGill, 2008). The fact that risk was removed since it was inconsequential in determining the level of trust in a project alters the widely accepted view that the relationship between risk and trust is reciprocal; an acceptable degree of risk is responsible for an increase in the level of trust in a project (Bond-Barnard et al., 2014;Daim et al., 2012).

Results of SEM analysis and discussion
Coordination and relationships had the highest and second highest correlation (with a standardised regression coefficient ¼ 0.899 and 0.842, respectively) with the degree of collaboration. This finding supports literature which emphasises the importance of team member relationships to enable collaboration (Manu et al., 2015). Due to the high uncertainties in project environments, firms are better able to respond to new information and approach work in a flexible manner when relationships are driven by trust, thus contributing to significant time and cost savings (Swan et al., 2002). Project actors are also less likely to withhold information deliberately and act against the interest of the overall project when relationships are trust driven, hence resulting in open and reliable flow of information (McDermott et al., 2004).
Among the six factors determined by the degree of collaboration, coordination (standardised regression coefficient of 0.899) had the most influence and incentives (standardised regression coefficient of 0.392) the least. It is interesting that team member incentives had the least influence on the degree of collaboration of all the factors as project manager incentives are one of the strongest predictors of project construction schedule, in a study conducted by Scott-Young and Samson (2008). However, they concede that further research is warranted on the potential impact of incentives for project team members. This study goes some way in investigating this topic.
One of the unexpected findings from the study was the high measure of association between two factors of collaboration, namely, proximity and incentives. Co-location has long been considered an essential component for superior project performance and goal achievement. However, in Scott-Young and Samson's (2008) empirical study, there was no significant relationship between team co-location and project success or any of the other factors they identified such as manager incentives. The reason for this significant association could be that physical proximity to colleagues serves as an incentive for project team members. Physical proximity promotes collaboration (Arslanian-Engoren in Dietrich et al., 2010), therefore, when the project team is able to work is close proximity to each other they collaborate more which also incentivises them.
The results in Tables IV and VII support the links between level of trust, degree of collaboration and success in a project, which validates both H1 -PM success becomes more likely as the degree of collaboration increasesand H2, the degree of collaboration increases as the level of trust in the project increases. The findings are limited to practitioners' perceptions who are part of the study's target population.

The relationship between level of trust and degree of collaboration
This study has confirmed the hypothesis that the level of trust predicts the degree of collaboration, which in turn, predicts the success of the project. When practitioners promote trust and collaboration in a project, it is more likely that the project will be a success in terms of time, cost and quality objectives but more specifically that it will be perceived to be a success by all the stakeholders involved. It has been revealed that the expectations that project stakeholders have of each other as well as the exchange of knowledge between them is integral in determining the level of trust in a project. Moreover, coordination and the relationship between stakeholders are crucial for collaboration, which together with trust leads to PM success.
The strong relationship between trust and collaboration validates previous research which found that trust and respect is the second most important indicator for team integration practice (Ibrahim et al., 2015). Furthermore, the requirement to trust other team members and recognise that they are trying to achieve the very best results of which they are capable (i.e. expectations) is one of the most fundamental differences in the collaborative approach according to the Strategic Forum for Construction (2003) in Ibrahim et al. (2015).

Conclusions
The results corroborate the H1 that PM success becomes more likely as the degree of collaboration increases and the H2 that the degree of collaboration increases as the level of trust in the project increases. The model, in spite of a relatively small sample size, produced good results which are commensurate with similar studies (Doloi et al., 2011). Empirical evidence is provided that indicates that PM success becomes more likely as the degree of collaboration improves, which in turn, is influenced by an increase in the level of trust between team members. These findings address the gap in literature as to the factors that determine trust, collaboration and PM success and the strength of the association/link between them. Some practical insights for PM are that by promoting collaboration and trust in a project by taking cognisance of each construct's factors, the likelihood of PM success could improve. The results of the study may also provide insight into teaching and learning in tertiary education in terms of professionalism and integrity issues. It was determined that the level of trust in a project is influenced by: • the expectations that the project team have of each other; • the knowledge exchange that takes place between them; and • the degree of trust that is imported from other familiar settings (imported trust).
The degree of risk present in the project was found to have no significant link with the level of trust experienced in the project. This alters the widely accepted view that the relationship between risk and trust is reciprocal and contradicting the results published by Daim et al. (2012) which contended that an acceptable degree of risk is responsible for an increase in the level of trust in a project. This study similarly found that the degree of collaboration in a project is influenced by: • the physical proximity between its team members; • the commitment the team members have towards the project; • conflict between the team members where less conflict improves the collaboration; • the degree of coordination in the project team; • the strength of the relationships between team members and other stakeholders; and • a balance of intrinsic and extrinsic incentives.
The overall review of the key findings has provided an interesting insight into the main "human-related" success factors in projects. However, a case study-based analysis on a number of successful and failed projects where the focus is on the extent of trust and collaboration in the project may further validate the findings from a practical perspective. The contrast between the successful and failed projects will be an important determination to highlight any distinctions between the factors impacting on success. Similar research conducted elsewhere with a large sample size would be more appropriate for realistic estimations of impacts and accuracy of results asserted in SEM analysis. Further research is currently being undertaken by the authors to model the relation between quality of communication and the other constructs.

Trust and collaboration in project teams
Corresponding author Taryn Jane Bond-Barnard can be contacted at: taryn.barnard@up.ac.za Question No.

Model variable input Question Scale
Project trust Please think about your experience of working with other project team members in a typical project, before answering the following questions Extent on a scale of 1 (to an extremely small extent) to 10 (to an extremely large extent)