Hi Saulius,

I don't believe SPEM constains your breakdown structure in any way. 
Someone correct me if I am wrong.

Nevertheless, EPF Composer does not.  As Bruce stated, you can mix your 
level of decomposition in EPF Composer.  For example, you could define an 
activity that contains an activity and three tasks.

It could very well be that the best breakdown for XP is one activity that 
contains the tasks. 

Cheers,
Chris

Chris Sibbald, Ph.D., P.Eng.
Senior Systems Engineer
Mobile: +1 (613) 266 - 5061
Fax: +1 (613) 739 - 4786
[email protected]



Bruce Macisaac <[email protected]> 
Sent by: [email protected]
06/01/2009 11:37 AM
Please respond to
Eclipse Process Framework Project Developers List <[email protected]>


To
Saulius Grigaitis <[email protected]>
cc
revolt revolt <[email protected]>, Eclipse Process Framework Project 
Developers List <[email protected]>
Subject
Re: [epf-dev] XP process







I may not quite be following your question, but you can have  both 
activities and task uses at the same level. 
(I haven't checked the SPEM 2.0 spec - it could be that EPF is more 
flexible than the spec). 
This means that you can group some tasks into an activity, while leaving 
others as tasks as the same level. 

Hope that helps. 

Bruce MacIsaac 
Manager – RMC Content 
[email protected] 
phone: (408)250-3037 (cell) 



Saulius Grigaitis <[email protected]> 
Sent by: revolt revolt <[email protected]> 
05/30/2009 01:39 PM 


To
Bruce Macisaac/Cupertino/i...@ibmus 
cc
Eclipse Process Framework Project Developers List <[email protected]> 
Subject
Re: [epf-dev] XP process








Hi Bruce,

thank you for your response. Yes, I agree that this part should be 
spitted to smaller tasks.

And I have general question regarding to SPEM 2.0 Activity. If I 
understand SPEM 2.0 specification correctly, Delivery Process must 
contain Activities, and Activities contains Tasks Uses, other Activities 
etc. But in some examples I saw only Tasks Uses at top level in 
diagrams, while in some examples there were only activities used at top 
level. The problem with this XP process is that there is no easy way to 
combine some related Task Uses to Activity that those Activities really 
would make sense, because XP is very lightweight process, it has very 
low amount of Task and Tasks Uses are related with each other a lot. So 
then most Activities should contain only one Task Use. Or there should 
be single or two/three general Activities in Delivery Process. EPF 
Composer allows to build delivery process containing only Task Uses (not 
nested under Activities), so I'm a bit confused what actually defines 
SPEM 2.0.

Thanks,
Saulius







Bruce Macisaac wrote:
>
> Hi Saulius,
>
> I'm interested in XP processes - so I reviewed the process you created.
> At first view, it looks like you correctly represent what is happening 
> in XP, but I think it could be presented more clearly.
>
> Specifically, there are the tasks that developers sign up for, and 
> then there are the subtasks that they perform to complete a 
> development task.
> There is a checkbox for "planned item" which we can use in a WBS to 
> indicate a task that is planned and signed up for, vs. lower level 
> tasks that are "doing the work".
> I suggest leveraging this, and nesting tasks under a planned activity 
> called "Develop story" or similar.
>
> Take a look at the OpenUP delivery process's activity "Develop 
> solution increment" - you could create something similar for the XP 
> process.
>
> Bruce MacIsaac
> Manager – RMC Content
> [email protected]_ <mailto:[email protected]>
> phone: (408)250-3037 (cell)
> <http://www-01.ibm.com/software/rational/rsdc/>
>
>
> *Saulius Grigaitis <[email protected]>*
> Sent by: [email protected]
>
> 05/13/2009 12:21 PM
> Please respond to
> Eclipse Process Framework Project Developers List <[email protected]>
>
>
> 
> To
>                  Eclipse Process Framework Project Developers List 
<[email protected]>
> cc
> 
> Subject
>                  [epf-dev] XP process
>
>
>
> 
>
>
>
>
>
> Hello,
>
> Is anybody interested in XP process? There is really a lot of work done 
on
> XP Method Content (http://epf.eclipse.org/wikis/xp/),
> but seems people are not interested in Processes part.
> I'm currently working on academical project "XP Process Model". I'm
> working mainly on Processes
> part of this XP process model. So I'm looking for XP people to get some
> feedback on this process model. Currently I'm looking for feedback on
> initial
> version of XP workflow diagrams:
> http://xp.rubyonrails.lt/xp/deliveryprocesses/xp_F0F4CBB8.html?nodeId=e\
> cfdc854
> <
http://xp.rubyonrails.lt/xp/deliveryprocesses/xp_F0F4CBB8.html?nodeId=ecfdc854
>
> http://xp.rubyonrails.lt/xp/deliveryprocesses/Release_D9160738.html?pro\
> 
c=__UotgTm-Ed60aszglc-35Q&path=__UotgTm-Ed60aszglc-35Q,_xB4tUDvyEd674OST\
> QR24ig
> <
http://xp.rubyonrails.lt/xp/deliveryprocesses/Release_D9160738.html?proc=__UotgTm-Ed60aszglc-35Q&path=__UotgTm-Ed60aszglc-35Q,_xB4tUDvyEd674OSTQR24ig
>
> http://xp.rubyonrails.lt/xp/deliveryprocesses/Iteration_FB458D89.html?p\
> 
roc=__UotgTm-Ed60aszglc-35Q&path=__UotgTm-Ed60aszglc-35Q,_xB4tUDvyEd674O\
> STQR24ig,__MTkoTvyEd674OSTQR24ig
> <
http://xp.rubyonrails.lt/xp/deliveryprocesses/Iteration_FB458D89.html?proc=__UotgTm-Ed60aszglc-35Q&path=__UotgTm-Ed60aszglc-35Q,_xB4tUDvyEd674OSTQR24ig,__MTkoTvyEd674OSTQR24ig
>. 
>
>
>
> Full model is here http://xp.rubyonrails.lt/index.htm (slightly
> different than
> original at Eclipse wiki).
> You can use Git repository directly
> git://www.rubyonrails.lt/xpprocess.git . Any feedback is
> highly appreciated!
>
> Saulius Grigaitis
>
> _______________________________________________
> 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


<<image/jpeg>>

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

Reply via email to