Agile Contracts for Software Consultants
summary
Argues that consultants should use time-and-materials agile contracts instead of fixed-price scope, showing what clauses and practices actually shift risk: not-to-exceed clause, 30-day cancellation, and clear automated tests and code ownership. Describes dedicated teams, weekly sprints with demos, ballpark estimates plus prioritization, and occasional cost ceilings. Claims PromptWorks runs over 30 T&M projects in two years, loses roughly 25% at proposal stage, and delivers working features iteratively so clients can stop early if needs are met.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:54Disclaimer
- 2:21Preamble
- 18:33Assumptions of FPFS contracts
- 19:37Frequent delivery of working software....
- 25:01Contract documents
- 25:43Project proposal
- 27:00Peter Stevens: Types of Contracts
- 27:55Our Time and Materials Approach
- 31:53Responses
- 36:01Master Services Agreement (MSA)
- 36:26MSA Highlights
- 39:08Scope of Work (SOW)
related talks
48mHow to Win and Start Contract Development Projects That Leverage Agile Values
46mExtreme Contracts: free to work the way we love toward the right design
56mTips from the Trenches
59mDelivering Agile Methodologies & Emerging Tech in Hostile...
37mAre projects agile?
06mProtecting an agile project from the consultants
46mAgile Recruitment - The Missing Step In Your Agile Transformation
04mAgile Transition - How to Build an Effective Agile Team