3 ms·
no the dev doesn't Mike, in his own words: I went through the app, listed out the bugs I was finding for each component, mocked up a couple small grap
by x0x0 13y ago
no the dev doesn't
Mike, in his own words:
I went through the app, listed out the bugs I was finding for each
component, mocked up a couple small graphical changes, and sent them over to
the developer.
bugs are covered under a fixed price contract. Changes aren't. And Mike is a marketer / photographer; do you really believe he has any idea of the difference between a "small graphical change" and something that requires a code change? The developer is at fault only for agreeing to any changes without a price increase.
And thus the classic problem with fixed price contracts: when I've done them I've been really clear with clients that no changes are included. Bugs yes, but every change is a renegotiation. Now often the lines between those two are a bit blurry, and I try to give clients the benefit of the doubt. But I bid to a very specific spec, and what can seem like a tiny change often goes against the grain of assumptions built into the code and is anything but tiny. To a person, clients agree then whine down the road when guess what, that change is a price increase. Sigh. The answer is to not do fixed price; it just sets you up in a very adversarial relationship with your client.
Plus, well, if you pay bottom price you get bottom quality.
- chii 13y agoSometimes, non-technical people don't (or can't) tell the difference between a "bug" and a "change". when the thing doesn't do what they expected in their mind's eye, its a bug, not a change. A change is when a completely new feature that isn't mentioned in the spec. So "bugs" like, moving a menu around, or swapping screens seems easy to someone who has never written anything before, but it isn't trivial (unless, of course, you had time to write nicely abstracted code. But for $800 and two weeks, i doubt that's the case). May be there should be an app that lets clients make mockups, and when they change their mockups, it computes a "diff" that then is heuristically used to generate an expected price...
- reeses 13y agoThat's why change orders should happen for anything that isn't specified at the time of signing the contract. They can be zero cost, they can be clarification change orders, they can swap scope, or they can involve additional cost. I try to get to a cadence of about one change order a week on projects lasting longer than ten weeks. Sometimes, depending on how onerous getting an SOW signed can be, we'll even queue up change orders (with the client's willing participation) to execute right after the SOW is approved by legal. There are plenty of apps that version mockups, but it's also possible to add layers to existing documents as well, whether it's photoshop, visio, etc.