Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [epf-dev] Sequential activity for planning next iteration.


Hi Chris,
 
I agree with your suggestion. The way I've usually seen this activity performed is to do much of the assessing and replanning during the iteration, and the "Assess and Plan the Next Iteration" is a formal meeting at the end of the iteration to acknowledge lessons learned and get agreement for the new plan. I'd feel better about keeping it as its own activity separate from Manage Iteration, but running in parallel with it.
 
Regarding the success or failure of an iteration, that refers to how successful the team was in meeting the goals of the iteration: were all risks planned to be mitigated actually mitigated? Were all the requirements planned to be implemented actually tested successfully? Maybe we could re-word it to make that clearer.
 
- Jim
 
____________________
Jim Ruehlin
RUP Content Developer, IBM Rational Software
email:   jruehlin@xxxxxxxxxx
phone:  760.505.3232
fax:      949.369.0720
 


From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx] On Behalf Of ChrisDoyle@xxxxxxxxxxxxxx
Sent: Thursday, February 23, 2006 1:01 PM
To: epf-dev@xxxxxxxxxxx
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

Back to the top