3 ms·
Sometimes, 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'
by chii 13y ago
Sometimes, 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.