| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription 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="-G9wByhMaPQHqKvp12aZFEA" name="how_to_adopt,_TcmHIDzQEd2XwI9llpWEBA" guid="-G9wByhMaPQHqKvp12aZFEA" changeDate="2009-07-20T05:21:44.000-0700" version="7.5.0"> |
| <mainDescription><h3>
 |
| Getting started&nbsp;
 |
| </h3>
 |
| <p>
 |
| Creating a shared vision involves understanding and agreeing on the fundamental "what" and "why" of the product under
 |
| development. This ensures that stakeholders and the development team have a common understanding of the problem to be
 |
| solved, and understand the stakeholders' needs.
 |
| </p>
 |
| <p>
 |
| Begin by reviewing the reference material associated with this practice to better understand the intent of the
 |
| practice. 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 that it captures. Tailor the template for the
 |
| specific needs of the project. Review the <a class="elementLink"
 |
| href="./../../../practice.tech.shared_vision.base/tasks/develop_technical_vision_9D36CF2F.html"
 |
| guid="_0fOAoMlgEdmt3adZL5Dmdw">Develop Technical Vision</a> task to understand what needs to be performed to capture
 |
| and communicate the vision. Review the guidelines on requirements gathering techniques and requirements reviews
 |
| associated with the Develop Technical Vision task, and select the appropriate technique(s) for the project. Educate the
 |
| development team and relevant stakeholders on the purpose of this practice, and get buy-in on the techniques that will
 |
| be used to establish and maintain a shared vision.
 |
| </p>
 |
| <p>
 |
| This practice is related to many other useful practices. For example:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Requirements practices: the vision is one of the outcomes of stakeholder requests elicitation. It is also the
 |
| primary input for developing more fine-grained technical requirements. stakeholders and the development team use
 |
| the vision to provide the context and high-level objectives for the detailed technical requirements.
 |
| </li>
 |
| <li>
 |
| Architecture practices: the vision outlines the high-level objectives and constraints for the system that inform
 |
| architectural design decisions.
 |
| </li>
 |
| <li>
 |
| Project management practices: the vision defines the scope and constraints of the project that are the basis for
 |
| work prioritization and initial estimates of effort. The value delivered by the team at each milestone must align
 |
| with stakeholders' expectations, expressed by the project vision.
 |
| </li>
 |
| </ul>
 |
| <h3>
 |
| Common pitfalls
 |
| </h3>
 |
| <p>
 |
| <b>Rushing into a solution before the problem is understood.</b> The result is typically a system that fails to solve
 |
| stakeholder problems and satisfy stakeholder needs. Avoid design while capturing the vision. Focus on the "what" and
 |
| "why" of the product, rather than detailing the solution. Detailed technical requirements will be developed later, in
 |
| conjunction with architectural design and trade-off analysis.
 |
| </p>
 |
| <p>
 |
| <b>Failure to gain agreement on the problem to be solved.</b> Make sure that you have identified all stakeholders,
 |
| captured their needs and wishes, and obtained agreement on the problem to be solved and associated constraints. Missing
 |
| a critical stakeholder can result in significant re-work later.
 |
| </p>
 |
| <p>
 |
| <b>Failure to manage scope.</b> Rome was not built in a day (or in a single project). Make sure that you capture
 |
| stakeholder needs and features, and prioritize them to deliver as much value as early as possible. If the estimated
 |
| effort is too great to commit to for a single external release, divide and conquer. The product vision may span more
 |
| than one release of the product, providing a roadmap for future work, as well as work planned for the current project.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
