AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<Raj.Kumar@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	0BAA09DBFAD04A4DBB6CE240807CB3B9010C85E8EB@cosmail03.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 5 Apr 2010 14:36:07 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Kumar, Raj" <Raj.Kumar@lsi.com>
Subject: Re: Orion File 1 QA schedule
Message-ID: <20100405143607.594f41b9@ripper.onstor.net>
In-Reply-To: <0BAA09DBFAD04A4DBB6CE240807CB3B9010C85E8EB@cosmail03.lsi.com>
References: <0BAA09DBFAD04A4DBB6CE240807CB3B9010C85E8EB@cosmail03.lsi.com>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

I can't read M$ Project.  Can you print it out in pdf possibly?

Tanks!

a

On Mon, 5 Apr 2010 15:29:36 -0600 "Kumar, Raj" <Raj.Kumar@lsi.com>
wrote:

> FYI
> 
> This is a highly guesstimated schedule (especially for phase 2 & 3
> since we don't have much information).
> 
> 
> 
> From: Kumar, Raj
> Sent: Monday, April 05, 2010 2:20 PM
> To: Stark, Brian
> Subject: Orion File 1 QA schedule
> 
> Brian,
> 
> Attached  is the schedule, you can use the excel sheet to get the
> higher level estimates for each phases/iterations. Please aware of
> the following assumptions that I made:
> 
> 
> 1.       The estimates are not based on *man days*, these are based
> on the actual resources and lots of parallel tests taken into account.
> 
> 2.       Even though the plan is built based on the current
> iterations plans for each phase, I believe when we roll out features
> for testing they will come in different order than the current
> iteration plan. However that doesn't affect the current estimates
> much because the estimates for each features should remain same,
> however it may affect the estimates badly if it changes the way I
> planned the parallel execution per resource.
> 
> 3.       I assume almost all the features are available after
> iteration 1.
> 
> 4.       I have provided estimates for each iterations per phase. For
> each iterations the tasks are allocated to be run in parallel based
> on the resources we have. I also built-in lots of parallel testing
> between iterations (spiral model), and of course this will only work
> if we have most of the functionalities working at the time QA start
> the testing, for example:
> 
> 
> 
> (a)    Water fall Model:
> 
> File 1 Phase 1     88 days
> 
> Iteration 1           22 days
> 
> Iteration 2           21 days
> 
> Iteration 3           45 days
> 
> 
> 
> (b)   Spiral model (This is the one I used, it's risky but efficient)
> 
> File 1 Phase 1     45 days
> 
> Iteration 1           22 days
> 
> Iteration 2           21 days
> 
> Iteration 3           45 days
> 
> 
> 
> 5.       I do not have any technical documentation (design documents)
> for phase 2 & 3 and I just made estimates based on my current
> understanding. Based on the natures of changes we may need to
> re-adjust the schedule, let us see how this goes. I have few items
> that are planned in Phase 3 (e.g. NDMP regressions ) which are
> actually the place holders for items like Service VM & clustering
> integration, IO VM and failover integration, etc.
> 
> 
> 
> 
> 
> Thanks.
> 
> 
> 
> Raj
> 
