It may also be useful to discuss creating a vision statement so we have
a clear understanding of what we need to provide to the users. We may
also want to discuss scheduling and when we'd like to see the next
version released.

 

- Jim

 

____________________

Jim Ruehlin, IBM Rational

RUP Content Developer

Eclipse Process Framework (EPF) Committer www.eclipse.org/epf

email:   [EMAIL PROTECTED]

phone:  760.505.3232

fax:      949.369.0720

 

________________________________

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of "Lyndon Washington" <[EMAIL PROTECTED]>
Sent: Tuesday, May 01, 2007 8:17 AM
To: Eclipse Process Framework Project Developers List
Subject: [epf-dev] [Scrum] Scrum Status Meeting 03 May 2007 - Proposed
Agenda

 

In preparation for Thursday's Scrum status call, here are a list of bugs
that will be discussed at the meeting.  Please reply to this posting
with additional topics that you would like to see in the agenda.

Cheers, 
-Lyndon-

ID 

Sev 

Pri 

OS 

Assignee 

Status 

Resolution 

Summary 

176503 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=176503>  

nor 

P3 

All 

[EMAIL PROTECTED] 

ASSI 

 

Scrum - Develop guideline for Introduction of Scrum 

184288 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=184288>  

nor 

P3 

Linu 

[EMAIL PROTECTED] 

NEW 

 

[scrum] Scrum phases should get added as a Delivery process 

184297 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=184297>  

nor 

P3 

Linu 

[EMAIL PROTECTED] 

NEW 

 

[scrum] The structure of the left-hand navigation content... 

184285 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=184285>  

nor 

P3 

Linu 

[EMAIL PROTECTED] 

REOP 

 

[scrum] The banner image for the publish site needs say "... 

 

 

 

 

 

 

 

 

 

_______________________________________________ 
epf-dev mailing list 
[email protected] 
https://dev.eclipse.org/mailman/listinfo/epf-dev 
_______________________________________________
epf-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/epf-dev

Reply via email to