| Sampling Factors: |
Location (Not Relevant: All work is performed at the Keymind site in Virginia)
Customer (Not Relevant: All projects are for federal customers.)
Size (Not Relevant: Though staff size varies between 4 – 8, people are not dedicated full time to projects. Size has been shown not to have an impact on the way work is performed)
Organizational Structure (Not Relevant: In total 16 people work at Keymind in a flat organizational structure)
Type of Work (Not Relevant: All 4 projects develop web applications using similar technology)
Life cycle used: The life cycle uses is either partially agile (requirements analysis done up front, followed by SCRUM development) or iterative/agile The partially agile projects are T&M, whereas the fully iterative/agile projects are FFP
Type of contract: Two projects are contracted as Time and Material (T&M), while the other two are Firm Fixed Process (FFP) contracts The projects that is FFP are the ones following the iterative/agile lifecycle. Whereas the partially agile projects are T&M |
| Sampling Factor Values: |
Partially agile/iterative (Life cycle used): All requirements and high level design done. Coding uses the agile/iterative lifecycle
Fully agile/iterative (Life cycle used): All development activities done in iterations
T&M (Type of contract): Time and Materials
FFP (Type of contract): Firm Fixed Price |
| Subgroups: |
T&M/Partially agile: Technical refresh of system. Requirements and design are done up front. Coding follows the agile life cycle 3.5 FTEs
9 People, 2 Basic Units
– Partially agile/iterative
– T&M
FFP/Fully Agile: Technical refresh. Under firm fixed price contract using an agile life cycle 2.5 FTEs
6 People, 2 Basic Units
– FFP
– Fully agile/iterative |