Quote:
Originally Posted by Ben Scammell
Chivas, unfortunately that's an awful lot of the usual ifs and buts. One thing in particular:
>>The biggest problem is some in the community not understanding the difference between what the developer is trying to achieve and a promise in past updates<<
A daft side-swipe, if the truth be told. It could be put another way - the community understands only to well, having made huge allowances both prioer to release, during, and since...but grows continually tired of fudged expectations, and partial delivery of results - at best.
It's quite simple - dont promise what you can't deliver. However good your intentions may be. Equally, dont bounce it back onto the users when you fail to deliver, or only partially deliver...and certainly dont go on about better user relations if an initial link is then slowly eroded to the point of nothingness. Best of all, be succinct and truthful with the problems you are encountering, and dont patronise your user base, many of whom are equally as bright and skilled as your own developers, and sometimes developers themselves.
I would have said these points were obvious and basic.
Ben/Falstaff
|
There are ALWAYS alot of IF's and BUT's in a development this complex. We were lucky to be involved in the development at all, its just unfortunate many don't have any experience with developing anything, or the knowledge that prototypes ALWAYS evolve until you have a working product.
There's that promise word again lol " Its simple , don't promise what you can't deliver" The developer continually stated there were no promises.
Its unfortunate the development had to be released before it was finished so there are going to be many problems before its done. These points are so obvious that if you can't see them there is no point my debating it with you.