|
PureBytes Links
Trading Reference Links
|
Gang -
without question, the management of the TS2000i project created the mess we
are seeing today.
My impression is that the original technical architecture of Tradestation 4
COULD NOT BE SALVAGED.
This caused a total REWRITE of the code.....a magnanamously difficult
task....and one I believe that management would not appreciate.
Delivery schedule "slippage" caused the project managers to continue to
eliminate "features" from the initial TSi2000 product. That is why we are
only NOW seeing MAJOR changes in the SP3 version......STRATEGY vs. SYSTEM. I
mean, WOW, to change TERMINOLOGY in an interim release.....UNHEARD OF....and
a stupid move in my belief.
My guess is that few, IF ANY, of the original TS2000i developers or project
managers are still with Omega.....NOT GOOD, NOT GOOD AT ALL.
> -----Original Message-----
> From: Gary Fritz [mailto:fritz@xxxxxxxx]
> Sent: Thursday, November 11, 1999 3:20 PM
> To: omega-list@xxxxxxxxxx
> Subject: Re: Software Testing Team; Beta testing
>
>
> > Most articles I've read say that if fixing a bug in the design
> > phase takes 1 unit of effort, fixing it during development will
> > take 20 units of effort and fixing it during beta testing will take
> > 400 units of effort. That's what we are witnessing with TS2K.
>
> It's even worse than that. The 400 units in beta-test assumes a REAL
> beta test, i.e. testing by a small team of qualified users BEFORE
> product release.
>
> The costs for fixing go up even more after product release. Not to
> mention the costs in customer dissatisfaction, bad word-of-mouth,
> lost sales, etc.
>
> Omega shot themselves in the foot BIGtime with this product. They
> cost themselves HUGE amounts of development costs and lost revenue
> because they let management dictate the delivery schedule to please
> the shareholders, instead of paying attention to the realities of
> development time.
>
> > Professionals can organize themselves properly and do very large
> > and effective projects in C++. If you don't have professional
> > programmers, then professional managers should be able to compensate.
>
> Agree 100%.
>
> But even if you have professional programmers, incompetent management
> (e.g. dictating schedules) can sink any project. And that, I'm
> afraid, is what we're really witnessing with TS2K.
>
> Gary
>
|