Data for the Paper: Agile Values or Plan-Driven Aspects: Which Factor Contributes More toward the Success of Data Warehousing, Business Intelligence, and Analytics Project Development?
Description
The data analysis requires creation of a structural model, which can be analyzed using SmartPLS, as follows: Agile Values -> Project Success; Plan-Driven Aspects -> Project Success; Technological Capability -> Agile Values; Shared Understanding -> Agile Values; Shared Understanding -> Plan-Driven Aspects; Top Management Commitment -> Agile Values; Top Management Commitment -> Plan-Driven Aspects; Complexity -> Agile Values; Complexity -> Plan-Driven Aspects. Survey: Project Success 1. The project meets or is expected to meet the budgetary estimate. 2. The project meets or is expected to meet the schedule estimate. 3. The project meets or is expected to meet the customer requirements. 4. The project improves or is expected to improve decision-making. 5. The project meets or is expected to meet quality requirements. Agile values 1. We value individuals and interactions over processes and tools as an important aspect of DW/BIA development. 2. We value working software over comprehensive documentation as an important aspect of DW/BIA development. 3. We value customer collaboration over contract negotiation as an important aspect of DW/BIA development. 4. We value responding to change over following a plan as an important aspect of DW/BIA development. Plan-Driven Aspects 1. The project has processes to manage scope creep. 2. The project has processes to manage customer expectations. 3. The project has processes to manage commitments such as contracts or promises. 4. The project has processes to manage controls on schedule, cost, and quality. 5. The project has processes to manage risk. Shared Understanding 1. For reaching a common understanding, IT and business members use dialogue to remove ambiguities. 2. For reaching a common understanding, IT and business members use dialogue to remove domain knowledge gaps. 3. For reaching a common understanding, IT and business members participate in information sharing sessions. 4. For reaching a common understanding, IT and business members use dialogue to understand the other party’s perspective. Top Management Commitment: For the successful completion of the project, the top management 1. provides the leadership. 2. provides the governance structure. 3. is willing to invest a great deal of effort beyond that is normally expected. 4. is committed. Technological Capability: The development team has the ability to employ technological tools to deliver solutions that meet the 1. business requirements. 2. functional requirements. 3. non-functional requirements. 4. architecture requirements. Complexity: During the project completion, difficulties were caused by 1. a large number of pieces during integration. 2. the reconciliation of inadequate quality of incoming data. 3. the frequent changes in requirements. 4. the excess coordination effort among the stakeholders.
Files
Steps to reproduce
1. Run the structural model in SmartPLS using Tab 2 of the sheet. Tab 1 provides the complete data but one indicator - scope creep - was dropped because of reliability issue. 2. The third tab of the data provides the segments according to PLS-POS (prediction oriented segmentation). Segregate the data according to group. Agile-plan balanced segment (group 1) has 85 cases and Agile Heavy segment has 39 cases. Run the SmartPLS algorithm again.