| Sampling Factors: |
Location (Not Relevant: OU performs its activities from Mumbai and Chandigarh development facilities however there are no location specific processes. OU is governed with a common set of processes hence no significant process variation across locations.)
Customer (Not Relevant: OU provides services to its internal operations team and there is no customer specific process tailoring or variation required.)
Size: Different size for development life cycle projects i.e. Large and Mini has a bearing on process execution.
Organizational Structure (Not Relevant: OU operates as a single unit within the organization. There are no separate processes or process variation within OU based on internal structure.)
Type of Work: Different life cycle activities i.e. development and maintenance has a bearing on process execution. |
| Sampling Factor Values: |
Large (Size): These are the large development projects where the estimated coding effort is more than 180 hrs. These follow the detailed life cycle as defined in QMS.
Mini (Size): These are the small development projects where the estimated coding effort is less than 180 hrs. They follow the tailored life cycle as defined in QMS.
Development (Type of Work): These are the development projects which involve development of new functionality. These cover both large and mini lifecycle projects.
Maintenance (Type of Work): All the client requests for enhancement, where the estimated coding effort is less than 40 hrs, follow the life cycle of SMLC (Software Maintenance Life Cycle). Emergency bug fixes are also included as part of this life cycle |
| Subgroups: |
G1-Development Large: This covers all large size development projects.
83 People, 7 Basic Units
– Large
– Development
G2-Development Mini: This is a life cycle for small sized projects
54 People, 5 Basic Units
– Development
– Mini
G3- Maintenance: All the projects in this subgroup follow maintenance life cycle defined in QMS
155 People, 12 Basic Units
– Maintenance |