.....
people want simple answers as to whether or not they are still on schedule for this May 1 date. if you don't have them shut the fuck up and stop acting like a little bitch because your golden goose is shitting all over it's customers.
**********
Simple answer is that when they know they will tell you.
I'd rather them work on my miner then hop here and provide an update that you will take out of context for which they will need to take time out and reply again.
I could probably make them post 50 updates here daily that would make even me at least 3 hours sitting here adjusting the timeline of the release date. How would that help you?
If anything major comes up they would post it, but any analytics of the release date on time frame of +1hr gain with this -2hr loss with this not helping anyone.
They are entering probably the most critical stage right now as if anyone understands logistics of working with multiple vendors and making sure that pieces fall into the right places on time.
On top of that there must be a backup plan for everything, parts, vendors anything you can possibly think that could go wrong.
I progressed with BA on quite a few issues regarding refunds, releasing more information and as well as advising on their hosting center.
This is not official BA posting. Just ramblings from my experience in manufacturing.
My experience in Manufacturing (and indeed that for the my experience across the industry as a whole) has been the exact opposite.
Any time there's a product like this being produced (especially for the first time) there's going to be a project manager(s) in the mix (although not having one would explain a lot in BA's case) Someone who operates at the 20Kft level who sees where all the pieces come together and holds each party responsible for meeting the deadlines. (In my world this is me many times) Having a punch list of major deliverables that the "ship date" is dependent on, and with a realtime a %complete, target date up/down is already part of the job. Pushing that out to anyone who needs a status update is a business 101 process that takes all of 1 minute to publish. In my case I usually do/can do reporting for projects that are based on milestone, phase, and date (or any combination of the three)
Some people want to know when "the next important step" is done no matter when, others want to know when the next group of steps are met, some only want to know what's done by the next due date (which is the route of the BA weekly updates) I have some customers who get a daily update EOB and it takes me little or no time to update this daily (on multiple projects) And I capture down to the "work in seconds" on some projects.
If BA couldn't get a detailed update out with some level of certainty about what is/isn't done and if there will/won't be delays on a daily basis, then they shouldn't be in business period. I'm sure they CAN,..it's simply that the weekly format simply allows for a lot of "noise" to cover mistakes, and conversely lets you emphasize anything good that happens through the week as the emphasis for the entire update. But when your biggest problem is a customer sat issue,.. one where "Your lack of communication is abysmal" is the single biggest thing that's been screamed for months,.. to not go the extra mile and KILL people with info, is just another key indicator that while these guys may be smart engineers/designers etc.. they aren't a "good business".
This is simply another case of how this forum's perception and portrayal of the time/work related to real world events is hilarious. I saw someone say it took them months to migrate a customer DB a while back in this thread.. *LOL* We've migrated (and repaired) DBs (SQL, Oracle, hell even DB2 DBs with mass corruption (millions of XR entries) all fixed in several days, with only one person working on it part time. A DB noob with access to Google could learn DB admin, fix a med/large cust database, export and import in less than two weeks if they were full time on it.
