Re: [epf-dev] Sequential activity for planning next iteration.

[Ricardo Balduino <balduino@xxxxxxxxxx>]

Chris,

This is a good topic to bring to discussion
on the next BUP SIG meeting when we will cover Project Management discipline
(Monday 27, 8am PST).
I hope you can be there to discuss that
with us.

Regards,

Ricardo Balduino
IBM | EPF Committer

ChrisDoyle@xxxxxxxxxxxxxx
Sent by: epf-dev-bounces@xxxxxxxxxxx

02/23/2006 01:00 PM

Please respond to
Eclipse Process Framework Project Developers List <epf-dev@xxxxxxxxxxx>

To	epf-dev@xxxxxxxxxxx
cc
Subject	[epf-dev] Sequential activity for planning next iteration.

Hi All,

Looking at the WBS for the various phases i.e. inception, elaboration,
construction etc, they all end with a “sequential” activity for assessing
and planning the next iteration. I think this is unnecessarily 
restrictive. Most other activities are performed in parallel so why must
the assessment of the current iteration and planning for the next be 
sequential?

As a suggestion couldn’t the planning tasks be made part of manage 
iteration? And don’t we continually assess status? If there is a 
sequential activity at the end of an iteration I’d rather think of it
as 
“publish next iteration plan” which could include a status assessment.

Regarding the stated purpose of the Assess Results task i.e. “Determine
success or failure of the iteration. Apply the lessons learned to modify
the project or improve the process.” I don’t have any problems with the
second sentence but I do with the first sentence, the “success or 
failure”. I think if you are applying the process properly, it cannot
be a 
“failure”, a setback maybe but “success of failure” promotes the wrong
connotations for iterative development.

Regards Chris

Chris Doyle
Solution Specialist
Synergy Plus Pty Ltd 

_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev