Lyndon
The typical WBS structure is as follows:
Delivery Process
Phase
Iteration [n]
Activity
Task Descriptor
Phases and Iterations are created directly in the Delivery Process.
Activities can be created directly in the Delivery Process, or previously
created as a Capability Patterns (in case you want to reuse those patterns
in different phases).
If you create it as a CP, you can drag and drop it to the DP, which
becomes an activity.
The task descriptors come to existence when you drag and drop a task from
the method content under the activity (or CP), or when you create a task
descriptor in place (with no linked task) under the activity (or CP).
Typically you want to maximize reuse, so you use first approach. Creating
a task descriptor in place is reserved for situations where you don't find
a task in the method, and don't want to actually create one.
You can find detailed explanation and examples in the Getting Started
section of EPF Web site (EPF Composer Overview - parts 1 and 2):
http://www.eclipse.org/epf/general/getting_started.php
You can also go to the EPF Composer tool, Help menu, Cheat Sheets
(sections: Apply a Capability Pattern and Create a Process)
Ricardo Balduino
Senior Software Engineer
IBM Rational Software (www.ibm.com/rational)
Eclipse Process Framework (www.eclipse.org/epf)
"Lyndon Washington" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
04/16/2007 11:53 AM
Please respond to
Eclipse Process Framework Project Developers List <[email protected]>
To
"Eclipse Process Framework Project Developers List" <[email protected]>
cc
Subject
Re: [epf-dev] Collaboration Norms for Scrum Content
Quick answer to your question on where to add phases and activities: you
want to add those as capability patterns to assemble a delivery process.
Eventually you need to create or tweak an existing custom category to
include the delivery process, so it shows up on the treebrowser when you
publish the content.
Ricardo, I have noticed that Claude added a new Delivery Phase, and unde
r that created two phases. Is that what you meant?
Also, I have read through some of the help on delivery process and
understand that this seems to be the main way to expose method content at
the correct point in the delivery process.
Question: The developing phase is made up of 1 or more development
sprints. A sprint is a collection of the following activities; sprint
planning, development (incl. coding, testing, design, daily standups),
sprint review and sprint retrospective. When is it time to define method
content that will become tasks, and when can you get away with defining
activities and tasks directly in the delivery process?
Cheers,
-Lyndon-
On 4/13/07, Ricardo Balduino <[EMAIL PROTECTED]> wrote:
Lyndon, this list is the right place to start :-)
In a nutshell, the process is to use this list for any development
discussions, either for content or source code. You want to address
specific bugs and enhancements via Bugzilla, where discussion can happen
and you can attach any content/code for inclusion in the base. Committers
discuss and move things to CVS as appropriate. Today we have one
placeholder for content discussions in Bugzilla, so you may want put a
prefix in the summary of a bug such as "Scrum - ", so we know that applies
to Scrum plug-in. Same for the epf-dev list, you may want to put a prefix
on the subject line.
If we have (hopefully) an exponential growth of plug-ins and discussions
around them, we can think of creating new discussion lists and components
in Bugzilla.
An alternative we are experimenting now is leveraging the use of Wiki
technology to enable contribution and collaboration. You can find the
Scrum (translated from French to English) content available at:
http://www.epfwiki.net
That being said, please raise a bug in Bugzilla and/or start interacting
with the Wiki, and let's discuss what you are proposing for the Scrum
plug-in.
Quick answer to your question on where to add phases and activities: you
want to add those as capability patterns to assemble a delivery process.
Eventually you need to create or tweak an existing custom category to
include the delivery process, so it shows up on the treebrowser when you
publish the content.
I invite others to chime in for more ideas on how the Scrum plug-in can
evolve.
Ricardo Balduino
Senior Software Engineer
IBM Rational Software (www.ibm.com/rational)
Eclipse Process Framework (www.eclipse.org/epf)
"Lyndon Washington" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
04/13/2007 10:46 AM
Please respond to
Eclipse Process Framework Project Developers List <
[email protected]>
To
"Eclipse Process Framework Project Developers List" <[email protected]>
cc
Subject
[epf-dev] Collaboration Norms for Scrum Content
Greetings,
I have noticed that for the OpenUP content there appears to be some
established process in place to ensure that discussion about the different
parts of the methodology or process are raised and work is distributed.
Are there such established practices for the Scrum plugin? If not, anyone
interested in establishing them, even if it means taking the OpenUP
practices and using that as a starting point.
What do I have to discuss? Well, I want to expand the content to include
the Scrum phases and activities. Scrum phases are Plannin, Staging,
Developing and Releasing.
Where would I add those in the method plugin? Would I add new method
content (i.e. content packages, categories), or would I add it in the
process portion (i.e. delivery process or capability pattern)?
Many thanks,
-Lyndon-
_______________________________________________
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
_______________________________________________
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
