- Sampling Summary：
（抽样汇总） -
Sampling Factors: Location (Not Relevant: Projects are executed at multiple locations. However process followed by projects is consistent across life cycles of projects irrespective of location. Hence location is not an influencing factor.)
Customer (Not Relevant: Projects are executed for multiple customers (defence agencies). Process followed by projects is consistent across life cycles of projects irrespective of customer. Hence customer not an influencing factor.)
Size (Not Relevant: Projects executed in the OU are of similar size. Hence size is not an influencing factor.)
Organizational Structure (Not Relevant: OU is organized as a single unit. Projects are executed in the same unit. Hence organizational structure does not influence process.)
Type of Work (Not Relevant: Only one type of work, i.e. Development projects are executed in the OU. Hence Type of work is not an influencing factor.)
Life Cycle: (Relevant: Two life cycles are followed by projects (traditional and agile). Life cycle followed influences the process.)Sampling Factor Values: Traditional (Life Cycle): Projects following traditional life cycle like waterfall.
Agile (Life Cycle): Projects following agile life cycle.Subgroups: CS – Traditional: Projects under this subgroup follow waterfall life cycle model. This model ensures that requirements and designs are complete and accurate. This enables successfully planning for the project development, and manage the process. The model also emphasizes documentation production, as well as source code, as key products. The full documentation of requirements, design, and development practices ensures continuity of knowledge.
7 People, 1 Basic Units
– Traditional
CS – Agile: Projects under this subgroup follow agile life cycle model. In this approach, not all requirements will be fully defined at the outset of the project. Customers will likely know what the key requirements are, and allows the team to focus on building those features first. Customers also provide immediate feedback and can adjust requirements and priorities to react to any needed changes. The team will manage itself and focus on the priority needs of the project.
12 People, 1 Basic Units
– Agile