<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:PracticeDescription 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" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-EywbC9-OjkU1AygGXtoGZQ" name="new_practice,_a7qSUB4nEd2bS8fFOQ7WWA" guid="-EywbC9-OjkU1AygGXtoGZQ" changeDate="2011-07-14T16:29:16.612-0700" version="7.5.0">
  <additionalInfo>&lt;p>&#xD;
    For more information on the shared vision practice, see the following:&#xD;
&lt;/p>&#xD;
&lt;table border=&quot;0&quot; summary=&quot;layout table&quot; width=&quot;100%&quot;>&#xD;
    &lt;tbody>&#xD;
        &lt;tr>&#xD;
            &lt;td colspan=&quot;2&quot;>&#xD;
                A. Hickey, A. Davis &lt;em>Elicitation Technique Selection: How Do the Experts Do It?&lt;/em>, International&#xD;
                Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press, Sep.&#xD;
                2003&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td width=&quot;10%&quot;>&#xD;
            &lt;/td>&#xD;
            &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
                Descriptions&amp;nbsp;of elicitation techniques that will help&amp;nbsp;define the vision.&amp;nbsp;&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td colspan=&quot;2&quot;>&#xD;
                &lt;p>&#xD;
                    Ivy Hooks, Lou Wheatcraft Scope - Magic, Compliance Automation&amp;nbsp;Inc., 2001. &lt;a&#xD;
                    href=&quot;http://www.reqexperts.com/media/papers/scope_magic.pdf%20(Get&quot;>http://www.reqexperts.com/media/papers/scope_magic.pdf&lt;/a>&#xD;
                    (&lt;a href=&quot;http://get.adobe.com/reader/&quot; target=&quot;_blank&quot;>Get Adobe Reader&lt;/a>)&#xD;
                &lt;/p>&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td width=&quot;10%&quot;>&#xD;
            &lt;/td>&#xD;
            &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;>&#xD;
                Excellent whitepaper on defining&amp;nbsp;and communicating the scope and constraints&amp;nbsp;for a product.&amp;nbsp;&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
    &lt;/tbody>&#xD;
&lt;/table></additionalInfo>
  <problem>&lt;p>&#xD;
    Establishing and maintaining a shared vision of the problem being solved (stakeholder needs) and the high-level&#xD;
    properties of the proposed product (product features)&amp;nbsp;reduces the risk associated with stakeholder and market&#xD;
    acceptance by aligning expectations.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Unfortunately, misunderstandings and miscommunication about the product strategy often lead the development team to&#xD;
    develop a system that fails to meet stakeholders' needs and vision.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    It is&amp;nbsp;essential that the development team and stakeholders&amp;nbsp;share the same expectations.&amp;nbsp;The&#xD;
    product&amp;nbsp;&lt;a class=&quot;elementLink&quot; href=&quot;./../../../core.tech.common.extend_supp/workproducts/vision_2E71B03C.html&quot;&#xD;
    guid=&quot;_0WVxcMlgEdmt3adZL5Dmdw&quot;>Vision&lt;/a>&amp;nbsp;identifies the stakeholders, provides a common understanding of&amp;nbsp;the&#xD;
    problem being addressed,&amp;nbsp;captures&amp;nbsp;the&amp;nbsp;high-level stakeholder&amp;nbsp;needs and project constraints, and&#xD;
    provides the background and context for requirements that will be detailed later. A shared vision serves as input for&#xD;
    communicating the fundamental &quot;what and why&quot; for the project, and provides a strategy against which all future&#xD;
    decisions must be validated.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Establishing and maintaining a shared vision is also essential for planning and monitoring the scope of the&#xD;
    development&amp;nbsp;effort.&amp;nbsp; The product Vision&amp;nbsp;establishes the long-term vision for the product,&amp;nbsp;a vision&#xD;
    that typically spans several releases, and provides the information required for&amp;nbsp;cost-benefit analysis and&#xD;
    prioritization of work.&#xD;
&lt;/p></problem>
  <application>&lt;p>&#xD;
    The best way to read this practice is to first familiarize yourself with its overall structure: what it is in it and&#xD;
    how it is organized.&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Review the template for the &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../core.tech.common.extend_supp/workproducts/vision_2E71B03C.html&quot;&#xD;
    guid=&quot;_0WVxcMlgEdmt3adZL5Dmdw&quot;>Vision&lt;/a> to understand the information it captures.&amp;nbsp; Then review the task &lt;a&#xD;
    class=&quot;elementLink&quot; href=&quot;./../../../practice.tech.shared_vision.base/tasks/develop_technical_vision_9D36CF2F.html&quot;&#xD;
    guid=&quot;_0fOAoMlgEdmt3adZL5Dmdw&quot;>Develop Technical Vision&lt;/a> to see the steps describing &quot;what&quot; needs to&#xD;
    be&amp;nbsp;performed to capture this information.&amp;nbsp; Associated guidelines provide more detailed information on &quot;how&quot;&#xD;
    to perform the task.&amp;nbsp; Finally,&amp;nbsp;the associated checklist provides a means to verify&amp;nbsp;that you have&#xD;
    captured all of the required information.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    For step-by-step instructions on how to adopt this practice, see &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../../practice.tech.shared_vision.base/guidances/roadmaps/how_to_adopt_2DBBBCD6.html&quot;&#xD;
    guid=&quot;_TcmHIDzQEd2XwI9llpWEBA&quot;>How to Adopt the Shared Vision Practice&lt;/a>.&#xD;
&lt;/p></application>
</org.eclipse.epf.uma:PracticeDescription>
