| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:RoleDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-nJn-jwljg2OgNZnS4jT87g" |
| name="new_role,_hQJ-QFkVEdul8L-IGeA7TA" guid="-nJn-jwljg2OgNZnS4jT87g" changeDate="2006-10-11T06:06:47.359-0700" |
| version="1.0.0"> |
| <mainDescription><p>
 |
| The Visionary is a business role. The Visionary is the one who is usually responsible for getting a project started
 |
| through enthusiasm and commitment to the idea and business goals. The Visionary should remain involved throughout the
 |
| design and delivery process to ensure the original objectives are being met. If any issues arise during the project,
 |
| which must be considered by higher management, the Visionary will either provide the decision or provide higher
 |
| management with the business viewpoint.
 |
| </p>
 |
| <p>
 |
| The Visionary role ensures the project excellence from the business point of view and the Technical Co-ordinator does
 |
| the same from the technical point of view.
 |
| </p>
 |
| <h4>
 |
| <a id="Responsibilities" name="Responsibilities">Responsibilities</a>
 |
| </h4>
 |
| <ul>
 |
| <li>
 |
| Promoting the translation of the vision into working practice
 |
| </li>
 |
| <li>
 |
| Taking a wider view of the end-to-end business process
 |
| </li>
 |
| <li>
 |
| Contributing to key requirements sessions
 |
| </li>
 |
| <li>
 |
| Contributing to key design sessions
 |
| </li>
 |
| <li>
 |
| Contributing to key review sessions
 |
| </li>
 |
| <li>
 |
| Resolving conflicts across the business areas owned by the Visionary
 |
| </li>
 |
| <li>
 |
| Ensuring user resources are available as needed
 |
| </li>
 |
| <li>
 |
| Monitoring progress in relation to the original vision
 |
| </li>
 |
| <li>
 |
| Commitment and availability throughout the development cycle
 |
| </li>
 |
| </ul></mainDescription> |
| <keyConsiderations><p>
 |
| The Visionary has the high-level view of the original reasons for initiating the project: this must not be dissipated
 |
| during development. Unfortunately, this happens in many projects. It is very easy once development is under way to
 |
| involve only those staff who will use the computer system on a day-to-day basis but who, perhaps, do not fully
 |
| understand all the business vision. This can result in a dilution of the original goals and a tendency towards simply
 |
| re-specifying the system to be replaced. It is imperative that the Visionary is present when important user events
 |
| occur or when management decisions about the progress of the project are made.
 |
| </p>
 |
| <p>
 |
| The Visionary must commit business staff to the project as <a class="elementLink" href="./../../dsdm_openup/roles/ambassador_user.html" guid="_ctbZ8FkVEdul8L-IGeA7TA">Ambassador User</a>(s). These people should be available to the project on a continuous basis throughout the life of the project -
 |
| not necessarily full-time but "contracts" for the Ambassador Users time should be agreed with the <a class="elementLink" href="./../../openup_basic/roles/project_manager.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a> before leaving the Business Study phase, e.g. "Ambassador User X
 |
| will work in the project team every Monday, Wednesday and Friday morning". The <a class="elementLink" href="./../../dsdm_openup/roles/advisor_user.html" guid="_avOA0FkVEdul8L-IGeA7TA">Advisor User</a>(s) involvement will be more <em>ad hoc</em> but should be well planned in advance.
 |
| </p></keyConsiderations> |
| <skills><ul class="noindent"> |
| <li> |
| Excellent communicator |
| </li> |
| <li> |
| Excellent awareness of business goals |
| </li> |
| <li> |
| High-level awareness of technological possibilities. |
| </li> |
| </ul></skills> |
| <assignmentApproaches><p> |
| The Visionary and <u><a class="elementLink" href="./../../openup_dsdm/roles/exec_sponsor,_fULZwFkVEdul8L-IGeA7TA.html" guid="_fULZwFkVEdul8L-IGeA7TA">Executive Sponsor</a></u> roles may be held by the same |
| person. |
| </p></assignmentApproaches> |
| </org.eclipse.epf.uma:RoleDescription> |
