Squarepeg wrote:
@Andy - I hear ya on doing it right the first time, just do us all a favor and start doing regular updates on time-frames, expected releases dates, etc. If you say it's going to be a few weeks, but find out at the end of the 2nd or third week that it's going to take a coupe/few more weeks, TELL US. Don't let it get to the 4th week and then act surprised when customers like me say 'where's the udpate?'
Update & simply explain to us like this:
'it's been an m-f'n bizotch getting everything compatible with J3, and although we are running out of hair to rip out of our skullz, we've finished A, B & C. But have to finish X, Y & Z and estimate it's going to take some serious pain-killers [still bleeding from the scalp] and an additional couple [Two], or few [Three] Weeks. But, make sure to check back next week, as we will stop our furious werkin long enough to post an update on our progress.'
Voila! took me 45 seconds to write those 3 sentences.
Personally, I would much rather have the bad news that something is going to be delayed, and have that information for proper planning, than to than to be kept in the dark wondering when.
I agree strongly.
Just update us and make a (new) time schedule to get us a little more into the timing.
I think everybody will understand a delay for a detailed reason, but dont understand a delay for a too general reason.
In general we like your way of development but your communication behaviour is not acceptable in this highly informed world.