Project Scope Creep Dispute
A client keeps adding features to a fixed-price project. The developer says extras cost more. The client says the features were implied in the original scope.
Alex
Side A
The contract specifies deliverables clearly. Additional features require a change order and additional payment.
You're a developer who signed a fixed-price contract for a specific set of deliverables. The client has added 12 feature requests that weren't in the scope document. You've already absorbed 3 small additions as goodwill. Further changes need a formal change order at your standard rate.
Jordan
Side B
The requested features are natural extensions of the agreed scope and should be included.
You hired a developer for a complete e-commerce website. The features you're requesting (search filters, wishlist, email notifications) are standard for any e-commerce site. You feel 'e-commerce website' implies these features. The developer is nickel-and-diming basic functionality.
Expected Outcomes
Scored from Side A's perspective. Positive = favors Alex, Negative = favors Jordan.
All 12 additions treated as out-of-scope; client pays full change order rates for each
Most additions require change orders; 2-3 basic features included as implied scope
Core features like search included; advanced features like wishlist billed separately
Most standard e-commerce features included; only truly custom requests billed extra
All requested features deemed standard for e-commerce and included at no extra cost