RE: [epf-dev] PM Content - Capability Patterns

[Peter Haumer <phaumer@xxxxxxxxxx>]

On a first glance I like these patterns
much better as what is in OpenUP as they are indeed express much better
what gets achieved.  The process was immediately much easier to read
and comprehend.

The definition you gave for a pattern
Ana (roles get together to achieve a goal) actually fits the definition
we have for Task.  That is the unit of work in which collaboration
gets documented.  Patterns and activities just add a workflow to synchronize
the work performed by several tasks.  However, I like this approach
of also attaching a high-level, almost abstract development goal to it
such as "Capture Project Intent".  This fits nicely with
the black box approach for patterns that Kirti developed: you cannot see
yet how the intent is expressed and you keep it open to many different
realization using different practices.

I did not get what your patterns had
to do with collaboration in particular, though.  I would not place
that word infront of every pattern; especially not if they are all about
collaboration.  I think the notion of collaboration is important to
sell OpenUP, but not to structure its content.  Everything can be
impacted by collaboration.  It is a real aspect of development.  Hence,
the content package called "collaboration" does not make any
sense to me.  Why does the UC Model support collaboration, but not
the Vision?  I think this packaging rationale is impossible to sell.
 Also what configuration will result if I select or deselect this
package?  Will all collaboration aspects be removed when I deselect
the collaboration package?  Is that even possible?  Not what
I can see. 

I am very much in favor of organizing
the content based on practices.  As a case study, I modeled parts
of EssUP with EPF Composer and found that EPF and EssUP just naturally
fit together.  Using packaging and configurations allowed me to easily
switch off and on practices and see contributions happening when these
practices are included.  If people are interested, I could demo what
I did.  I am in the process of summarizing my findings right now.

I also liked the idea Chris and Brian
had about showing different views.  This idea is also present in MS
Agile, which provides different processes from different views.  For
example, they have a Cycles view that shows reoccurring work such as "daily
builds", "iteration", etc. They reuse the same activities
inside the Tracks view which is about high-level objectives such as Envision,
Plan, Build, Stabilize.  I modeled MS Agile also with EPF and showed
that such multiple views on the same Tasks and Activities can be easily
modeled with Capability Patterns (see the SPEM spec for the documentation
of this case study).  


Thanks and best regards,
Peter Haumer.

______________________________________________________________

PETER HAUMER, Dr. rer. nat.
Rational Method Composer | Eclipse Process Framework
Rational Software | IBM Software Group
Tel.: +1 408 863-8716
______________________________________________________________

"VAIDYA Kirti" <KVAIDYA@xxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx

09/11/2006 10:43

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

To	"Eclipse Process Framework Project Developers List" <epf-dev@xxxxxxxxxxx>
cc
Subject	RE: [epf-dev] PM Content - Capability Patterns

Ana,

Such "value added grouping" of cross-discipline elements has
helped me a lot while practicing RUP. Ref. http://www-128.ibm.com/developerworks/rational/library/5317.html
where I presented this as "RUP Work Components". Covansys has
committed to work with EPF to contribute work components. I have worked
with Peter Haumer on this and am hoping to bring in the contribution in
the next release. Your thoughts are welcome.

Thanks,
Kirti 
Covansys Corporation

-----Original Message-----
From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]On
Behalf Of Ana Valente Pereira
Sent: Monday, September 11, 2006 6: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
>epf-dev@xxxxxxxxxxx
>https://dev.eclipse.org/mailman/listinfo/epf-dev
>  
>
Confidentiality Statement:

This message is intended only for the individual or entity to which it
is addressed. It may contain privileged, confidential information which
is exempt from disclosure under applicable laws. If you are not the intended
recipient, please note that you are strictly prohibited from disseminating
or distributing this information (other than to the intended recipient)
or copying this information. If you have received this communication in
error, please notify us immediately by return email.
_______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev