15 ms·
There are plenty of ways to screw clients with fixed-fee projects. The most common is to ask the client what they want, write that down, and build it for a fat
by wpietri 5y ago
There are plenty of ways to screw clients with fixed-fee projects. The most common is to ask the client what they want, write that down, and build it for a fat fee based on the value they imagine they'll be getting. It turns out clients mostly don't know shit about what they actually need. Indeed, for many projects it's impossible to know the right thing to build up front, as much of the data is unavailable until you start shipping things. So what they sign up for and what will actually help them can diverge wildly.
Now that you have shipped the technically correct but not very useful thing, you collect the fee and then start accepting "change orders" at a punitive rate. At this point switching to another contractor will be even more risky and expensive, so they'll probably just suck it up. Or if you're really good at the game, you then negotiate a whole new fixed-fee contract with a higher price tag, and the deliver what they now think they want.
Bonus points if, as I've seen a big-name global contractor do, you deliver something not even barely working but possibly conforming to specs, and then just walk off the job. Even though the client has contractual obligations that they can't fulfill if the software doesn't work. At that point, the client realizes that a) they still need the software, b) the big-name contractor is the only who can deliver in time, and c) suing is risky, will take years, and anyway the big-name contractor can afford more lawyers. In this case the client signed another multi-million dollar contract with the big-name contractor, easily doubling the "fixed" fee. I lost touch with my contacts there before the thing ever worked, so I don't know how many times the big-name global contractor pulled this off on the same job.
- eatYourFood 5y agoAnd the clients aren’t to blame? Some will force waterfall on you then change their minds on requirements, am I a charity that just gives work away for free when they change their mind? Many large companies absolutely refuse agile delivery and require fixed scope and cost to get anything done.
- wpietri 5y agoHow quickly we go from, "Clients should pay for value" to "fuck the clients, they deserve to get cheated". Yes, waterfall is a bad choice. But no, clients aren't to blame for trusting a vendor to do right by them.
- eatYourFood 5y ago> "fuck the clients, they deserve to get cheated". Why use quotation marks for something I didn't say? Nothing I've said means "fuck the clients" unless you are maliciously taking the worst possible interpretation. A change that takes a massive amount of time and effort isn't something I should do for free. I'm more than happy to build a backlog, refine it, and build until there's a RC... so few enterprise clients want to subscribe to the perceived risk, they'd rather spend months specifying everything upfront to make some senior person happy whether that delivery methodology has been proven to work or not.
- wpietri 5y agoYes, I was paraphrasing. We both know you didn't say those exact words, so I thought you'd figure it out. Hopefully now you can.