| Sampling Factors: |
Location (Not Relevant: The locations covered are Bangalore, Chennai, Mohali, Noida, Gurgaon and Manila. The location of execution of a project does not have a bearing on Process Execution.)
Customer (Not Relevant: FIS executes projects for its parent organization in the US. The process followed is based on FIS”s Quality Management System. Hence Customer does not have a bearing on process execution.)
Size (Not Relevant: FIS executes projects of various sizes. However, the processes followed are not dependant on the size of the project and same QMS is followed for projects of all sizes. Hence size does not have any bearing on process execution.)
Organizational Structure (Not Relevant: The projects in FIS are organized under a single Business Unit named CIO Organization. Hence the Organizational Structure does not have a bearing on process execution.)
Type of Work: FIS executes development projects in Waterfall and Agile lifecycles. The type of lifecycle has an influence on the processes followed. The services projects executed by FIS are categorized as Maintenance and Remote Infrastructure Management based on their scope of work. This has a bearing on process execution. |
| Sampling Factor Values: |
Waterfall (Type of Work): Projects following waterfall lifecycle in development
Agile (Type of Work): Projects following Agile lifecycle in development
Maintenance (Type of Work): Projects following maintenance mode in services
RIM (Type of Work): Projects following remote infrastructure management mode in services |
| Subgroups: |
S1: Waterfall: Waterfall projects
83 People, 5 Basic Units
– Waterfall
S2: Agile: Agile projects
178 People, 7 Basic Units
– Agile
S3: Maintenance: Maintenance projects
131 People, 4 Basic Units
– Maintenance
S4: RIM: Remote Infrastructure Management projects
1082 People, 2 Basic Units
– RIM |