Table 4.
Sources of reflective constructs.
| Reflective constructs | Construct items | References |
|---|---|---|
| MGTRF | Communication system among all members. | Saqib et al., 2008; Ismail et al., 2012 |
| The control mechanism of project activity. | ||
| The feedback system for all Stakeholders. | ||
| Planning ability of project team. | ||
| Decision-making ability of Project team. | ||
| Prior project management experience of the project team. | ||
| The ability of the project team of risk identification and allocation. | ||
| DRF | Design team experience [design experience of consultant (Architect/Engineers)]. | Saqib et al., 2008 |
| Project design complexity. | ||
| Mistakes/delays in producing design documents. | ||
| Design team's contribution to project. | ||
| Adequacy of plans and specifications. | ||
| CRF | Contractor experience of related projects. | Saqib et al., 2008; Doloi et al., 2011 |
| The ability of a contractor to supervise project activity. | ||
| The ability of the project manager to supervise the contractor. | ||
| The ability of the project team to manage contractor case flow. | ||
| Speed of information between project organization and contractor. | ||
| PMRF | Project manager competence/skill. | Saqib et al., 2008; Seiler et al., 2012; |
| Project manager experience related to project. | Verburg et al., 2013 | |
| Leadership skills of project manager. | ||
| Technical capability of project manager. | ||
| Organizing and coordinating skills of project manager with contractor and subcontractor. | ||
| Reporting skill of project manager with contractor and subcontractor. | ||
| CLRF | Influence of client's representative. | Saqib et al., 2008 |
| Client experience. | ||
| Owner's clear and precise definition of project scope & objectives. | ||
| Owner's risk attitude (willingness to take risks). | ||
| Client's ability to brief the project. | ||
| Client's ability to make appropriate decisions. | ||
| Client's ability to define roles clearly. | ||
| K.C. | The project related internal documents or data files were easily accessible/available. | Songer and Molenaar, 1997 |
| The project related manuals or regulations were easily accessible/available. | ||
| The projected related professionals and experts were easily accessible for a meeting. | ||
| The professional databases or websites were easily accessible to acquire projected related knowledge. | ||
| Our colleagues and supervisors were easily accessible/available for sharing their valuable projected related knowledge. | ||
| We had an opportunity to hold an informal meeting with team members to share our projected related ideas/knowledge. | ||
| Team members were encouraged to keep the records of working knowledge in a written form. | ||
| Team members were encouraged to keep the records of working knowledge as a standardized procedure. | ||
| Team members were encouraged to keep the records of working knowledge in the information system. | ||
| Team members were encouraged to update the work-related profiles for further use. | ||
| Team members were encouraged to store the work-related rules or regulations in a written format or information system. | ||
| Team members were encouraged to transfer their knowledge or experience to others. | ||
| Team members were encouraged to discuss and share their opinions and documents with colleagues. | ||
| Team members were encouraged to quickly respond and provide our team with the necessary information, documents, or techniques whenever they encountered problems. | ||
| CSRF | The project was successful in meeting its functional performance of customers' expectations. | Shenhar et al., 1997 |
| The project was successful in meeting technical specifications as required by the customer. | ||
| The project was successful in fulfilling customers' needs. | ||
| The project was successful in solving customers' problems. | ||
| The customer is using the delivered product effectively/successfully. | ||
| Customers are satisfied with project deliverables. | ||