| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html |
| PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| <html lang="en-us" xml:lang="en-us"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> |
| <meta name="copyright" content="(C) Copyright Eclipse contributors 2005, 2006" /> |
| <meta name="DC.rights.owner" content="(C) Copyright Eclipse contributors 2005, 2006" /> |
| <meta name="security" content="public" /> |
| <meta name="Robots" content="index,follow" /> |
| <meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> |
| <meta name="DC.Type" content="task" /> |
| <meta name="DC.Title" content="Create a Delivery Process" /> |
| <meta name="DC.Relation" scheme="URI" content="process.html#process" /> |
| <meta name="DC.Relation" scheme="URI" content="capabilitypattern.html#capabilitypattern" /> |
| <meta name="DC.Relation" scheme="URI" content="deliveryprocess.html" /> |
| <meta name="DC.Format" content="XHTML" /> |
| <meta name="DC.Identifier" content="createadeliveryprocess" /> |
| <meta name="DC.Language" content="en-us" /> |
| <!-- |
| Copyright (c) 2005, 2006 IBM Corporation and others. |
| All rights reserved. This program and the accompanying materials |
| are made available under the terms of the Eclipse Public License v1.0 |
| which accompanies this distribution, and is available at |
| http://www.eclipse.org/legal/epl-v10.html |
| Contributors: |
| IBM Corporation - initial implementation |
| --> |
| <link rel="stylesheet" type="text/css" href="./ibmdita.css" /> |
| <title>Create a Delivery Process</title> |
| </head> |
| <body id="createadeliveryprocess"><a name="createadeliveryprocess"><!-- --></a> |
| |
| <h1 class="topictitle1">Create a Delivery Process</h1> |
| <div><div class="p"><p>A Delivery Process describes a complete and integrated approach |
| for performing a specific type of project. A Delivery Process describes what |
| is produced, how it is produced and the required staffing for the entire project |
| lifecycle.</p> |
| A Delivery Process is created for a particular type of project |
| to reflect the specific planning and project management needs. <p>Before |
| creating a delivery process:</p> |
| <ul><li>Select a method plug-in to hold your process. For more information, see <a href="methodplugin.html#methodplugin">Method Plug-in</a>.</li> |
| <li>Find or create a process package.</li> |
| </ul> |
| </div> |
| <div class="section">There are several ways to populate a process with method elements:<ul><li>By incorporating individual method elements by dragging the elements onto |
| an activity in the process.</li> |
| <li>By including already defined capability patterns.</li> |
| <li>By including parts of already defined capability patterns.</li> |
| <li>By creating descriptors directly in the process, which are either unrelated |
| to any method content or related to method content at a later point in time.</li> |
| </ul> |
| To create a Delivery Process:</div> |
| <ol><li class="stepexpand"><span>Once you have selected or created a process package, right click |
| the process package.</span></li> |
| <li class="stepexpand"><span>Click <strong>New > Delivery Process</strong>. The New Process Component |
| dialog appears.</span></li> |
| <li class="stepexpand"><span>Type a name for the delivery process into the <strong>Name</strong> field |
| and then select a default configuration from the drop down list. Your process |
| can contain content from many different method plug-ins. for this reason you |
| need to define a configuration that defines the visible set of elements and |
| relationships when the process is authored. This process authoring configuration |
| is referred to as the Default Configuration for the process and should define |
| the largest reasonable set of method plug-ins, content packages, and other |
| processes from the method library that will be referred to by the process |
| at some point.</span></li> |
| <li class="stepexpand"><span>Click <strong>OK</strong>. The process is created and the process editor |
| is opened.</span> <div class="note"><span class="notetitle">Note:</span> If the Properties window opens to the right of |
| the process editor, click the <strong>x</strong> to close it.</div> |
| </li> |
| <li class="stepexpand"><span>In the process editor, under the Description tab, document your |
| process using the available text fields.</span> <div class="note"><span class="notetitle">Note:</span> You can use the |
| Rich Text Editor to edit or enter the text for any field that has a twisty |
| symbol <img src="collapsed.gif" alt="" />. Simply click the symbol |
| to access the Rich Text Editor. Click the symbol again to close the Rich Text |
| Editor. For more information see <a href="richtexteditor.html#richtexteditor">Rich Text Editor</a></div> |
| </li> |
| <li class="stepexpand"><span>Decide on your primary process authoring view. You develop a process |
| using three different views:</span><ul><li><strong>Work Breakdown Structure</strong>: Define a work breakdown structure |
| in your process. Create iterations and activities first, and then populate |
| your activities by applying tasks from your Method Content. For more information |
| see <a href="developaworkbreakdownstructure.html">Develop a Work Breakdown Structure</a>.</li> |
| <li><strong>Team Allocation</strong>: Define which teams and roles shall participate |
| in activities and then find responsible work products and tasks from there. |
| For more information, see <a href="developateamallocationstructure.html#developateamallocationstructure">Develop a Team Allocation Structure</a>.</li> |
| <li><strong>Work Product Usage</strong>: Define which work products should be created |
| in activities and find tasks and roles from there. For more information see <a href="developaworkproductusagestructure.html#developaworkproductusagestructure">Develop a Work Product Usage Structure</a>.</li> |
| </ul> |
| </li> |
| <li class="stepexpand"><span><a href="applyacapabilitypattern.html#applyacapabilitypattern">Apply a Capability Pattern</a> or capability pattern parts to the delivery process.</span></li> |
| </ol> |
| </div> |
| <div> |
| <ul class="ullinks"> |
| <li class="ulchildlink"><strong><a href="deliveryprocess.html">Delivery Process</a></strong><br /> |
| </li> |
| </ul> |
| <div class="relconcepts"><strong>Related concepts</strong><br /> |
| <div><a href="process.html#process">Process</a></div> |
| <div><a href="capabilitypattern.html#capabilitypattern">Capability Pattern</a></div> |
| </div> |
| </div> |
| </body> |
| </html> |