| Sampling Factors: |
Location (Not Relevant: Most projects and activities are occurring either at a centralized location, or are managed by Microsoft SharePoint collaboration technologies thereby ensuring that location has little or no significant impact on process implementation and performance.)
Customer (Not Relevant: Although each customer tends to have its own preferences relating to details such as progress report formats, information, and frequency, the customer does not have a significant influence on how processes are implemented or performed within the organizational unit.)
Size: Generally, process performance can vary significantly—and in accordance with tailoring criteria—as a function of project size.
Organizational Structure (Not Relevant: The organizational unit has a relatively flat management structure. Therefore organizational structure does not cause significant variations in the performance of processes.)
Type of Work (Not Relevant: The organizational unit performs one type of work: product development and maintenance.) |
| Sampling Factor Values: |
Regular (R) (Size): A regular project has at least one of the following characteristics: (1) Period of performance > 2 years; (2) team size > 10 and < 15;=”” (3)=”” total=”” project=”” value=”” between=”” $2m=”” -=””>
Small (S) (Size): A small project has at least one of the following characteristics: (1) Period of performance < 2=”” years;=”” (2)=”” team=”” size=””>< 10;=”” (3)=”” total=”” project=”” value=””><> |
| Subgroups: |
Regular: Projects are categorized, implemented, and managed as “Regular” projects organizationally labeled as P1 or P2 project type.
22 People, 2 Basic Units
– Regular (R)
Small: Projects are categorized, implemented, and managed as “Small” projects organizationally labeled as ‘P3’ project type.
22 People, 5 Basic Units
– Small (S) |