Traci
This is inappropriate for an employer/employee relationship, The 'boss' may not realise the
consequences of their actions, but then that is not necesarilly their job.
If you take such a belacose position why shouldn't they?
Neven MacEwan (B.E. E&E) Ph. 09 621 0001 Mob. 0274 749062
Traci Sumpter wrote:
I would finish the project with the original specifications.
In addition to supplying the original product to the client (on time) put in the proposal for New Features in next version. depending on time for this proposal, will say wheather it is an 'advertising brief' i.e look out for the next version including the following features, or a full scale spec including timeframe and scope.
From experience.... every time a boss or client comes to you with a 'one last minute change' stop work on the origional project. Write up a new brief saying this will cost XXX more and will reqire XXX weeks to be added to the delievery date. and then ask them if it is still what they want.
Some change their mind back quickly, others will accept. whatever the cast the party is aware that if they do have these 'one last minute changes' that there is a consequence...
Becomes dificult if the 'boss' knew about this for ages (then I would say 'Ha Ha') and put it back on the boss to explain to the client that it is not able to be done.
I may seam a bitch, but I would rather do this than 'stress'.... People respect you if you are consistant even if you aren't the nice accomodating programmer that some people would love. But because people never see the work (unless there's something visible to see) needed in changes they have the assumption that there is no work.... Break that habit NOW!!! not only for you, but for all developers out there!!!
-----Original Message----- *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of *tracey *Sent:* Friday, 10 September 2004 9:48 a.m. *To:* NZ Borland Developers Group - Offtopic List *Subject:* [DUG-Offtopic] what do YOU do if.....
Hi guys.
Just thought I would start one of those “Friday” discussions.
As developers with many years of experience you must have had this come up many times.
Scenario:
* You are a sole developer working your arse off to get your program finished and “unexpected feature”-less by D-day. * It’s the day before your software goes live. * Your boss comes and tells you about “changes to requirements” which means quite a few changes to your database structure and software code. * It’s still the day before your software goes live. * There is still only one of you.
I’m looking forward to learning your techniques for handling these situations.
And HAVE A GREAT FRIDAY & WEEKEND
Cheers
Tracey
------------------------------------------------------------------------
_______________________________________________
Offtopic mailing list
[EMAIL PROTECTED]
http://ns3.123.co.nz/mailman/listinfo/offtopic
_______________________________________________ Offtopic mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/offtopic
