hiho, I like the idea of revisiting the capability patterns.
What is the feasibility of revisiting them in light of your ideas and in light of your ideas and Chris Armstrong's capability pattern ideas captured in this attachment https://bugs.eclipse.org/bugs/attachment.cgi?id=47379 to bug 152354 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=152354)? I liked Chris' notion that some patterns might be within a specific sub-process but that other capability patterns transcend any one sub-process and show how the sub-processes work together. I wouldn't want to go down a path of stressing the importance of collaboration and then only show it within each sub-process. I have a fear that this is worthy of more communication & collaboration amongst the process authors than can be scheduled in the next few weeks as we try to have content reviews to move the existing bugs from Verified to Closed. But maybe there are some changes that can be done to move us in the right direction. ------- b -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ana Valente Pereira Sent: Monday, September 11, 2006 7:56 AM To: Per Kroll Cc: Eclipse Process Framework Project Developers List Subject: Re: [epf-dev] PM Content - Capability Patterns What if we give up on capability patterns per discipline and create some collaboration patterns instead?...where the several roles have to get together to achieve some goal on each of the processes (intent, solution and management).... please take a look at the attached proposal... i did not add much text because the collaboration names should speak by itself on explaining the project lifecycle... I also tried to reuse most of the existing tasks or capabilities in order to avoid by changes at this time Ana Per Kroll wrote: > > For those interested in Capability Patterns for PM. > > Impacts > _147965_ <https://bugs.eclipse.org/bugs/show_bug.cgi?id=147965> Wed > 12:02 maj P2 PC ASSI EPF Content 1.0 1.0 M5 PM - Capability > Pattern assess_and_close_out_project - cr... > _147967_ <https://bugs.eclipse.org/bugs/show_bug.cgi?id=147967> Wed > 11:24 maj P2 PC ASSI EPF Content 1.0 1.0 M5 PM - Capability > Pattern assess_and_plan_iteration - creat... > _147969_ <https://bugs.eclipse.org/bugs/show_bug.cgi?id=147969> > 22:45:10 maj P2 PC ASSI EPF Content 1.0 1.0 M5 PM - > Capability Pattern manage_iteration - create content > > > _151783_ <https://bugs.eclipse.org/bugs/show_bug.cgi?id=151783> > 2006-08-23 nor P3 PC RESO EPF Content 1.0 --- PM - Task: > Close Out Project - remove > > > _147968_ <https://bugs.eclipse.org/bugs/show_bug.cgi?id=147968> Thu > 20:11 maj P2 PC RESO EPF Content 1.0 1.0 M5 PM - Capability > Pattern initiate_project - create content > > > plus each of the 4 Iteration Capability Patterns, as well as naturally > the delivery process itself. > > I did not find any bugs for these iteration capaility patterns and the > delivery process. > > > I suggest that we only have 2 capability patterns for Management: > Keep "Initiate Project" as is <Contains Define Vision and Plan the > Project> > Modify "Manage Iteration" to contain Plan Iteration, Manage Iteration, and > Assess Results. Each of the iteration Capability patterns would > contain Manage > Iteration CP, and only Inception contains Initiate Project. > 1) This means that Plan Iteration is done in the beginning of > iteration, not at > the end of previous, which is reflected in the task description. > 2) It simplifies CP patterns for the iterations. > 3) It avoids having Plan Iteration in every iteration, since Assess > Results is > already discussing that you need to update the Project Plan based on the > results of the assessment. > > Comments? > > I entered this in > https://bugs.eclipse.org/bugs/show_bug.cgi?id=147969 > > > > Cheers > > Per Kroll > STSM, Manager Methods: RUP / RMC > Project Lead: Eclipse Process Framework > Rational Software, IBM Corp > 408-342-3815 > >----------------------------------------------------------------------- - > >_______________________________________________ >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
