Unless you know exactly what you are delivering and exactly how long it will take to deliver, fixed price is dumb. How many people exactly nail their estimates? If you can do that then fixed price is low risk. But software is normally a journey or discovering the unknown. How can you do fixed price without horrendously padding the price?
Came up with a saying today. You've heard the saying "Definition of insanity is doing the same thing over and over and expecting a different result." My new saying: Definition of Software development is doing the same thing over and over and getting a different result. On Thu, 22 Oct 2015 at 4:49 PM, Grant Molloy <graken...@gmail.com> wrote: > Although this should be a standard clause in an IT contract, unfortunately > it is not in this one, and we're probably too far down the track to start! > > Is pretty annoying as they refuse to use electronic meeting facilities too. > > Has anyone successfully implemented charging for meetings partway into a > contract (fixed price)? > On Oct 22, 2015 6:39 PM, "Craig van Nieuwkerk" <crai...@gmail.com> wrote: > >> Tell them you charge for meetings on normal hourly rate even if they are >> cancelled. >> >> Craig >> >> On Thu, Oct 22, 2015 at 7:28 PM, Grant Molloy <graken...@gmail.com> >> wrote: >> >>> Hi list, >>> >>> I'm working on a long running project for a client. >>> They've been reviewing recent mods and have called a meeting. I was >>> provided a date range for said meeting where I was told all 3 reps from >>> client would be available. I've selected a convenient date and time and >>> have responded to their request. >>> Meeting was all booked in and now one of them says they're unavailable >>> for the selected timeslot. >>> I have a feeling I'm being dicked around and am wondering how to respond. >>> >>> Have others had similar issues? >>> How has it been handled? >>> >> >>