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