<?xml version="1.0" encoding="UTF-8"?>
<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1">
  <org.eclipse.epf.uma:ProcessDescription xmi:id="-Z6YA3AI8LA097zCJ_GuGvA" name="Justification,_kxy14LjkEe2ItPaV9bHRfA" guid="-Z6YA3AI8LA097zCJ_GuGvA"/>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-KzNGb_o0UDQer4etOVSMAA" name="vision,_ghx9eLo9Ee2ItPaV9bHRfA" guid="-KzNGb_o0UDQer4etOVSMAA">
    <keyConsiderations>&lt;p>&#xD;
    It is good practice to keep this artifact brief, so you can release it to stakeholders as soon as possible, and to make&#xD;
    the artifact easy for stakeholders to read and understand. You can accomplish this by including only the most important&#xD;
    features and avoiding details of requirements.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Projects that focus on product development might extend the marketing section and include a more detailed product&#xD;
    position statement that is based on their needs and research.&#xD;
&lt;/p></keyConsiderations>
  </org.eclipse.epf.uma:DescriptorDescription>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ivVJEZjfFsd9TWTf57_MUA" name="enterprise_vendor,_gh7uebo9Ee2ItPaV9bHRfA" guid="-ivVJEZjfFsd9TWTf57_MUA">
    <refinedDescription>&lt;p>&#xD;
    The resuable assets of enterprise are placed in this vendor for resuse in other project.&#xD;
&lt;/p></refinedDescription>
  </org.eclipse.epf.uma:DescriptorDescription>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-tB7Sv8S_CxV6LgIliaX9Vw" name="non-compete_clause,_gh7ufLo9Ee2ItPaV9bHRfA" guid="-tB7Sv8S_CxV6LgIliaX9Vw">
    <refinedDescription>&lt;p>&#xD;
    A&amp;nbsp;non-compete clause (often NCC) is a clause under which one party (usually an employee) agrees not to enter into&#xD;
    or start a similar profession or trade in competition against another party (usually the employer).&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The use of such clauses is premised on the possibility that upon their termination or resignation, an employee might&#xD;
    begin working for a competitor or start a business, and gain competitive advantage by exploiting confidential&#xD;
    information about their former employer's operations or trade secrets, or sensitive information such as customer/client&#xD;
    lists, business practices, upcoming products, and marketing plans.&#xD;
&lt;/p></refinedDescription>
  </org.eclipse.epf.uma:DescriptorDescription>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-eEYAa4xC6evzTy_rirhYRw" name="non-disclosure_agreement,_gh7uf7o9Ee2ItPaV9bHRfA" guid="-eEYAa4xC6evzTy_rirhYRw">
    <refinedDescription>&lt;p>&#xD;
    A non-disclosure agreement (NDA) is a legal contract or part of a contract between at least two parties that outlines&#xD;
    confidential material, knowledge, or information that the parties wish to share with one another for certain purposes,&#xD;
    but wish to restrict access to.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    It is a contract through which the parties agree not to disclose any information covered by the agreement. An NDA&#xD;
    creates a confidential relationship between the parties, typically to protect any type of confidential and proprietary&#xD;
    information or trade secrets&#xD;
&lt;/p></refinedDescription>
  </org.eclipse.epf.uma:DescriptorDescription>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-ias1PlojFH0V_rbmyfi4Xg" name="task_board,_gh7ugro9Ee2ItPaV9bHRfA" guid="-ias1PlojFH0V_rbmyfi4Xg">
    <refinedDescription>&lt;p>&#xD;
    The task board shows all the work the team is&amp;nbsp;doing during a sprint or daily work. It is updated&amp;nbsp;continuously&#xD;
    throughout the sprint–if someone thinks of a new task they&amp;nbsp;write a new card and puts it on the board. Either&#xD;
    during or before Daily Meeting, estimates are changed (up or down) and cards are moved around the board.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The task board might look like this:&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    &lt;span class=&quot;articleImage&quot;>&lt;img style=&quot;HEIGHT: 336px; WIDTH: 461px&quot; alt=&quot;&quot; src=&quot;./../../waad/workproducts/./resources/MockedTaskBoard.jpg&quot;&#xD;
    width=&quot;600&quot; height=&quot;447&quot; />&lt;a&#xD; 
    href=&quot;http://www.mountaingoatsoftware.com/system/hidden_asset/file/29/MockedTaskBoard.jpg&quot; >&lt;u>&lt;font&#xD;
    color=&quot;#0000ff&quot;>&amp;nbsp;&lt;/font>&lt;/u>&lt;/a>&lt;/span>&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    &lt;span class=&quot;articleImage&quot;>&lt;br />&#xD;
    &amp;nbsp;&lt;/span>&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Each row on the task board is a product backlog item (in this&amp;nbsp; particular example stories). During&#xD;
    the&amp;nbsp;planning meeting the team selects thework items they can complete during the coming sprint or day.&#xD;
    Each&amp;nbsp;work item is turned into multiple backlog&amp;nbsp;items. Each of these is represented by one task card that is&#xD;
    placed on the task board. Each task card starts on the task board in the “To Do” column. The columns are:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;b>Story&lt;/b>–The story description (“As a user I want to…”) shown on that row.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>To Do&lt;/b>–This holds all the cards that are not done or in process.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Work In Process&lt;/b>–Any card being worked on goes here. The programmer who chooses to work on it moves it over&#xD;
        when she’s ready to start the task. Often this happens during the Daily Scrum when someone says, “I’m going to work&#xD;
        on the boojum today.”&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>To Verify&lt;/b>–A lot of tasks have corresponding test task cards. So, if there’s a “Code the boojum class” card&#xD;
        there is likely one or more task cards related to testing: “Test the boojum”, “Write FitNesse tests for the&#xD;
        boojum,” “Write FitNesse fixture for the boojum,” etc. Some task cards don’t often get corresponding test cards&#xD;
        (“Fix Bug #321 in Bugzilla”) so those are placed in the “To Verify” column.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Done&lt;/b>–Cards pile up over here when they’re done. They’re removed at the end of the sprint.&#xD;
    &lt;/li>&#xD;
&lt;/ul></refinedDescription>
  </org.eclipse.epf.uma:DescriptorDescription>
  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-BQuNCU8bxwRV20sa5bI9Ew" name="work_item_pool,_giJJ0bo9Ee2ItPaV9bHRfA" guid="-BQuNCU8bxwRV20sa5bI9Ew">
    <refinedDescription>The pool of Requirements, Bugs, Tutorials, Support, Fixed Delivery Date and Intangilble items.</refinedDescription>
  </org.eclipse.epf.uma:DescriptorDescription>
</xmi:XMI>
