X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8BE83.285A8D58@onstor-exch02.onstor.net>; Sun, 25 May 2008 09:19:50 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8BE83.285A8D58"
Content-class: urn:content-classes:message
Subject: RE: Technical lead meeting
Date: Sun, 25 May 2008 09:19:49 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0A1C29FD@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0A1C29CB@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Technical lead meeting
Thread-Index: AcixliprrcwrA5zRRWWAWK7OM2f4fQAABy2gAAARQDAAAEcaMALuX11AACSvDYAAJ2lksA==
References: <BB375AF679D4A34E9CA8DFA650E2B04E09DFA3E7@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E09DFA3E9@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E09DFA3EF@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0A1C29AF@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E0A1C29CB@onstor-exch02.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Jonathan Goldick" <jonathan.goldick@onstor.com>,
	"Jobi Ariyamannil" <jobi.ariyamannil@onstor.com>,
	"Paul Hammer" <paul.hammer@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8BE83.285A8D58
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I agree that these are good things to cover.  I also agree that we don't
wait for the next meeting if any of these comes up, particularly if
someone is overloaded or has blocker issues that they need help on.

I think the triage process is working well in assigning defects.  The
schedule is determined by how long it takes to fix these defects, and we
will not hold the schedule to a certain date if there are known defects.
However, as we discussed in the engineering staff meeting, time is not
infinity and we need to be realistic about the schedule.  As Bob
mentioned, please come talk to me if you want to discuss any specific
defects in detail.

As for the technical lead meeting, it's not going to work if people show
up late or not at all.  I think it's most useful to have the meeting
before the Dev meeting, but I am fine with moving the meeting to another
time.  As an alternative, we could do it at 11:30 right after the core
team meeting.


Brian


> _____________________________________________=20
> From: 	Jonathan Goldick =20
> Sent:	Saturday, May 24, 2008 2:23 PM
> To:	Jobi Ariyamannil; Brian Stark; Paul Hammer; Tim Gardner; Andy
> Sharp
> Subject:	RE: Technical lead meeting
>=20
> These are good things to cover.  We do a lot of that in the triage
> meeting and in daily conversations, but more ad hoc.  However, most of
> these issues are probably not the kind of things to wait a week to
> cover given the time pressure.  When these issues come up I talk to
> Tim about it that day. =20
>=20
> _____________________________________________
> From: Jobi Ariyamannil=20
> Sent: Friday, May 23, 2008 10:58 PM
> To: Brian Stark; Paul Hammer; Jonathan Goldick; Tim Gardner; Andy
> Sharp
> Subject: RE: Technical lead meeting
>=20
> When I proposed to have this meeting, I thought we get an opportunity
> to go through the following as well:
>=20
> 1.	The leads share the status of the progress being made by their
> teams and discuss blocker issues if any.
> 2.	Check if anybody is overloaded and try to balance the load.
> 3.	Check if correct resources are assigned on the critical issues.
> 4.	Triage team decides which defects are MF defects for Beta and
> GA.  I think the dev leads must check whether we have enough resources
> to address all those MF defects within the schedule.  I am not sure
> whether we have some other meeting in which these concerns are
> discussed - if there is one, I would like to attend that meeting.  We
> should prioritize the critical issues from the MF defects list and
> assign appropriate resources.
> 5.	Major changes coming in, regression focus etc
> 6.	Any other issues the leads would like to discuss.
>=20
> These may sound obvious, but I think these are very critical for the
> success of the cougar project.
> I would like to see some realistic plans.
>=20
> We had two meetings so far. Those meetings were useful, but I think we
> should allocate some time to go through the above as well.
>=20
> Comments?
>=20
> Regards,
> Jobi
>=20
> _____________________________________________
> From: Brian Stark=20
> Sent: Thursday, May 08, 2008 11:00 PM
> To: Paul Hammer; Jonathan Goldick; Jobi Ariyamannil; Tim Gardner; Andy
> Sharp
> Subject: RE: Technical lead meeting
>=20
> OK, we can talk about this in the first meeting.  I'll send out a
> meeting request for Tuesday at 1pm...
>=20
>=20
>=20
> 	_____________________________________________=20
> 	From: 	Paul Hammer =20
> 	Sent:	Thursday, May 08, 2008 10:39 PM
> 	To:	Jonathan Goldick; Brian Stark; Jobi Ariyamannil; Tim
> Gardner; Andy Sharp
> 	Subject:	RE: Technical lead meeting
>=20
> 	Works for me.=20
>=20
> 	There is a pro and con with this pre-meeting approach that we
> can discuss in this first meeting; it is having a discussion vs. a
> presentation, which one do we want to achieve in this forum? Both
> approaches work depending on what you are trying to achieve.
>=20
> 	-Paul
>=20
> 	_____________________________________________
> 	From: Jonathan Goldick=20
> 	Sent: 2008-05-08 22:34
> 	To: Brian Stark; Jobi Ariyamannil; Tim Gardner; Andy Sharp; Paul
> Hammer
> 	Subject: RE: Technical lead meeting
>=20
> 	Sounds good to me.
>=20
> 	_____________________________________________
> 	From: Brian Stark=20
> 	Sent: Thursday, May 08, 2008 10:33 PM
> 	To: Jobi Ariyamannil; Jonathan Goldick; Tim Gardner; Andy Sharp;
> Paul Hammer
> 	Subject: Technical lead meeting
>=20
> 	Jobi made a good suggestion that we have a pre-meeting between
> the technical leads prior to the Dev meeting on Tuesday at 1:30pm.
> This would give us a chance to talk between ourselves about status and
> also come up with a plan for the 1:30 meeting. =20
>=20
> 	I think this is a good idea.  Maybe at 1pm on Tuesday?
> Alternatively, we could also do it on Monday afternoon, maybe right
> before the triage meeting.
>=20
>=20
> 	Brian
>=20

------_=_NextPart_001_01C8BE83.285A8D58
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: Technical lead meeting</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I agree that these =
are good things to cover.&nbsp; I also agree that we don't wait for the =
next meeting if any of these comes up, particularly if someone is =
overloaded or has blocker issues that they need help on.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">I think the triage =
process is working well in assigning defects.&nbsp; The schedule is =
determined by how long it takes to fix these defects, and we will not =
hold the schedule to a certain date if there are known defects.&nbsp; =
However, as we discussed in the engineering staff meeting, time is not =
infinity and we need to be realistic about the schedule.&nbsp; As Bob =
mentioned, please come talk to me if you want to discuss any specific =
defects in detail.</FONT></P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">As for the technical =
lead meeting, it's not going to work if people show up late or not at =
all.&nbsp; I think it's most useful to have the meeting before the Dev =
meeting, but I am fine with moving the meeting to another time.&nbsp; As =
an alternative, we could do it at 11:30 right after the core team =
meeting.</FONT></P>
<BR>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Brian</FONT>
</P>
<BR>
<UL>
<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Jonathan Goldick&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Saturday, May 24, 2008 2:23 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Jobi Ariyamannil; Brian Stark; Paul Hammer; Tim Gardner; =
Andy Sharp</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: Technical lead meeting</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">These are good things =
to cover.&nbsp; We do a lot of that in the triage meeting and in daily =
conversations, but more ad hoc.&nbsp; However, most of these issues are =
probably not the kind of things to wait a week to cover given the time =
pressure.&nbsp; When these issues come up I talk to Tim about it that =
day.&nbsp; </FONT></P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Jobi Ariyamannil<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Friday, May 23, 2008 10:58 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Brian Stark; Paul Hammer; Jonathan Goldick; Tim =
Gardner; Andy Sharp<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: Technical lead meeting</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">When I proposed to =
have this meeting, I thought we get an opportunity to go through the =
following as well:</FONT>
</P>
<UL>
<OL TYPE=3D1>
<LI><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">The leads share the =
status of the progress being made by their teams and discuss blocker =
issues if any.</FONT></LI>

<LI><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Check if anybody is =
overloaded and try to balance the load.</FONT></LI>

<LI><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Check if correct =
resources are assigned on the critical issues.</FONT></LI>

<LI><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Triage team decides =
which defects are MF defects for Beta and GA.&nbsp; I think the dev =
leads must check whether we have enough resources to address all those =
MF defects within the schedule.&nbsp; I am not sure whether we have some =
other meeting in which these concerns are discussed &#8211; if there is =
one, I would like to attend that meeting.&nbsp; We should prioritize the =
critical issues from the MF defects list and assign appropriate =
resources.</FONT></LI>

<LI><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Major changes coming =
in, regression focus etc</FONT></LI>

<LI><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Any other issues the =
leads would like to discuss.</FONT></LI>
<BR>
</OL></UL>
<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">These may sound =
obvious, but I think these are very critical for the success of the =
cougar project.</FONT>

<BR><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I would like to see =
some realistic plans.</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">We had two meetings =
so far. Those meetings were useful, but I think we should allocate some =
time to go through the above as well.</FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Comments?</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Regards,<BR>
Jobi</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Brian Stark<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Thursday, May 08, 2008 11:00 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Paul Hammer; Jonathan Goldick; Jobi Ariyamannil; Tim =
Gardner; Andy Sharp<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: Technical lead meeting</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">OK, we can talk about =
this in the first meeting.&nbsp; I'll send out a meeting request for =
Tuesday at 1pm...</FONT>
</P>
<BR>
<BR>
<UL>
<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Paul Hammer&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Thursday, May 08, 2008 10:39 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Jonathan Goldick; Brian Stark; Jobi Ariyamannil; Tim =
Gardner; Andy Sharp</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: Technical lead meeting</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Works for me. </FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">There is a pro and =
con with this pre-meeting approach that we can discuss in this first =
meeting; it is having a discussion vs. a presentation, which one do we =
want to achieve in this forum? Both approaches work depending on what =
you are trying to achieve.</FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">-Paul</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Jonathan Goldick<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> 2008-05-08 22:34<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Brian Stark; Jobi Ariyamannil; Tim Gardner; Andy Sharp; =
Paul Hammer<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: Technical lead meeting</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Sounds good to =
me.</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Brian Stark<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Thursday, May 08, 2008 10:33 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Jobi Ariyamannil; Jonathan Goldick; Tim Gardner; Andy =
Sharp; Paul Hammer<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> Technical lead meeting</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Jobi made a good suggestion that we =
have a pre-meeting between the technical leads prior to the Dev meeting =
on Tuesday at 1:30pm.&nbsp; This would give us a chance to talk between =
ourselves about status and also come up with a plan for the 1:30 =
meeting.&nbsp; </FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I think this is a good idea.&nbsp; =
Maybe at 1pm on Tuesday?&nbsp; Alternatively, we could also do it on =
Monday afternoon, maybe right before the triage meeting.</FONT></P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Brian</FONT>
</P>
</UL></UL>
</BODY>
</HTML>
------_=_NextPart_001_01C8BE83.285A8D58--
