X-Sylpheed-Account-Id:2
S:andy.sharp@lsi.com
SCF:#mh/Mailbox/sent
X-Sylpheed-Sign:0
X-Sylpheed-Encrypt:0
X-Sylpheed-Privacy-System:
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 12 Apr 2010 10:37:06 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: Brian Stark <brian.stark@lsi.com>
Cc: Nelson Nahum <Nelson.Nahum@lsi.com>, "Skrivanek, Cindy"
 <Cindy.Skrivanek@lsi.com>
Subject: Memo: Tuxstor continued delays
Message-ID: <20100412103706.2dec995e@ripper.onstor.net>
Organization: LSI
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hello,

I'm writing this to communicate an issue with continuing delays in the
tuxstor project, and what I propose be done about it.

The tuxstor project has been steadily slipping since the beginning of
the year, and maybe before that.  I feel that action must be taken in
order to stem the bleeding.

As some of you are aware, Bill Fisher continues to substantially
underperform in his engineering duties, the current "never-ending
changelist saga" being just the latest incarnation.  That, combined with
his prediliction to attack, threaten, acost and otherwise attempt to
intimidate anyone who dares call him on his unwillingness to produce,
is tearing the project apart.

Our latest deadline of March 17th has long since come and gone, and
while we met it in a minimalist way, we really didn't meet it at the
level intended.  The tasks remaining to meet that deadline in a
meaningful way remain bottled up behind Bill's task, which has been
dragging on since December time frame.  So many tasks are bottled up
behind Bill's tasks that the project is almost at a standstill, and yet
week after week goes by with only token progress.

Proposal: Bill be moved off the project.  The remaining members of
the team are quite capable of finishing the project from here,
especially when you consider that Bill has been contributing only drama
and delays for about six months now.  The tasks that are assigned to
Bill and which are holding up the project can easily be absorbed by the
remaining team members in just a matter of days (some already have
been), and the schedule brought under control.

Cost: we can only save by taking this action.  Keeping Bill on the
project only adds interminable delays.  Putting an end to those delays
will cost nothing and return predictability to the schedule.

Resources: since Bill is, in actual fact, contributing next to nothing,
this will not have the affect of losing any resources.

Time:  I would like this decision to be reached in the next couple of
days, say Wednesday at the latest.  However long we wait is just more
slippage added to the schedule.

I hope everyone can understand the need for this action.  If there are
any concerns or questions, don't hesitate to contact me.

Thanks,

a
