Agile Delivery on Fixed-Price Contracts: A Framework for Success

Federal acquisition professionals often view Firm-Fixed-Price (FFP) contracts and Agile delivery as oil and water. Agile requires flexibility; FFP requires certainty. But in reality, they can coexist — and thrive — if you change what you are fixing.

The Misconception

The traditional view is that FFP requires a fixed scope. This can lead to a common challenge where requirements are locked down in a PWS, and sprint cycles become mini-milestones rather than true iterative delivery.

The Framework: Fixed Capacity, Fixed Outcome, Variable Scope

To make Agile work on FFP, you must invert the triangle. Fix the budget (price) and the schedule (period of performance), but leave the scope variable, bounded by a vision.

1. Buy a "Software Factory," Not a Product

Structure the contract to purchase a specific team capacity (e.g., "3 scrum teams for 12 months") rather than a specific list of features. The deliverable is "sprints delivered" according to a definition of done.

2. Use a Statement of Objectives (SOO)

Instead of a prescriptive Performance Work Statement (PWS), use a SOO that defines the business problem.

• ▸Bad: "The vendor shall build a SQL database with these 50 tables."
• ▸Good: "The vendor shall provide a system that reduces claim processing time by 50%."

3. The "Detailed Design" CLIN

If your contracting officer (KO) is risk-averse, split the contract.

• ▸CLIN 001 (FFP): Discovery and Roadmap (3 months). Deliverable: A repository of user stories and a high-level architecture.
• ▸CLIN 002 (FFP): Agile Development Services. Deliverable: Code releases.

4. Performance Incentives

Tie profit to outcomes, not output.

• ▸Adoption Metrics: Bonus if 80% of users switch to the new system.
• ▸Defect Rates: Penalty if critical bugs exceed a threshold.
• ▸Velocity Stability: Incentive for predictable delivery.

Conclusion

FFP contracts provide the budget predictability Congress requires. Agile provides the operational flexibility missions require. By fixing the process and the outcome rather than the requirements, agencies can get the best of both worlds.