| Sampling Factors: |
Location (Not Relevant: One location – This has no bearing on process execution.)
Customer (Not Relevant: Work is not performed differently depending on the customer served by that work. Set of standard processes being used does not differ based on customer. This has no bearing on process execution.)
Size (Not Relevant: Work is not performed differently depending on the size of the project. Projects are of medium size that ranges from 5 to 25 persons. Set of standard processes being used does not differ based on size. This has no bearing on process execution.)
Organizational Structure (Not Relevant: One division as depicted on an organization chart. This has no bearing on process execution.)
Type of Work: Work is performed differently based on the type of work i.e. Software Development Projects, Software Maintenance Projects. Process areas affected are Project Management and Engineering process areas.
Lifecycle Model: Work is performed differently based on the lifecycle model i.e. Agile Lifecycle Model, Maintenance Lifecycle Model. Process areas affected are Project Management and Engineering process areas. |
| Sampling Factor Values: |
Software Development Projects (Type of Work): Development of software i.e. new solutions with tasks covering such as requirements gathering, design, coding, testing.
Software Maintenance Projects (Type of Work): Software Maintenance projects covers enhancement and change implementation scope of work. Maintenance of software with tasks covering such as requirements gathering, design, coding, testing.
Agile Lifecycle Model (Lifecycle Model): The GTL Agile Lifecycle Model is based on SCRUM methodology with tweaks to make it more disciplined. Requirements are captured in a product backlog and Development is conducted in a series of sprints. GTL agile process has more roles, events and deliverables in comparison to a conventional SCRUM.
Maintenance Lifecycle Model (Lifecycle Model): Maintenance Lifecycle Model in GTL is based on the waterfall model lifecycle model of software development. Maintenance projects exist for a specified duration, typically the entire financial year. However Change requests are taken up based on the approval from the client for each CR, planned and executed. |
| Subgroups: |
SG1: Software Development projects executed using Agile Lifecycle Model
39 People, 3 Basic Units
– Software Development Projects
– Agile Lifecycle Model
SG2: Software Maintenance projects executed using Maintenance Lifecycle Model
40 People, 4 Basic Units
– Maintenance Lifecycle Model
– Software Maintenance Projects |