| <?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="-7CRmNPPwEM-jEAQnjShe8g" |
| name="new_role,_ctbZ8FkVEdul8L-IGeA7TA" guid="-7CRmNPPwEM-jEAQnjShe8g" changeDate="2006-10-27T03:43:45.389-0700" |
| version="1.0.0"> |
| <mainDescription><p>
 |
| This role provides the key focus for design decisions. Working closely with the <a class="elementLink" href="./../../openup_basic/roles/project_manager.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>, <a class="elementLink" href="./../../openup_basic/roles/developer.html" guid="_0YDosMlgEdmt3adZL5Dmdw">Developer</a>(s), <a class="elementLink" href="./../../openup_basic/roles/tester.html" guid="_0ZM4MclgEdmt3adZL5Dmdw">Tester</a>(s) and
 |
| the <a class="elementLink" href="./../../openup_basic/roles/architect.html" guid="_0X9iEMlgEdmt3adZL5Dmdw">Architect</a>, the Ambassador User drives the system's requirements, bringing&nbsp;input
 |
| and ideas to the various sessions on behalf of the users; and keeping the other users informed of what is happening.
 |
| The holder of the Ambassador User role must have the desire, authority, responsibility and knowledge to be able to
 |
| ensure that the right system is built for the business. This does not necessarily imply a senior position within the
 |
| organisation, but a level of empowerment during the project to fulfil the role and a clear allocation of time to
 |
| participate in the project as required.
 |
| </p>
 |
| <h2>
 |
| <a id="Responsibilities" name="Responsibilities">Responsibilities</a>
 |
| </h2>
 |
| <ul>
 |
| <li>
 |
| Providing key input to business requirements and design sessions
 |
| </li>
 |
| <li>
 |
| Communicating with other users and getting their agreement
 |
| </li>
 |
| <li>
 |
| Providing input into prototyping sessions
 |
| </li>
 |
| <li>
 |
| Reviewing documentation
 |
| </li>
 |
| <li>
 |
| Reviewing and accepting delivered software
 |
| </li>
 |
| <li>
 |
| Providing user documentation
 |
| </li>
 |
| <li>
 |
| Ensuring user training is adequately carried out
 |
| </li>
 |
| <li>
 |
| Organising and controlling user testing
 |
| </li>
 |
| </ul></mainDescription> |
| <keyConsiderations><p>
 |
| Ambassador Users must be representative of the entire community of users. The whole user community should see them as
 |
| such - not just the user management. They must have authority delegated to them to make decisions and to guide the work
 |
| of the developers. This is particularly important when considering changes of scope due to time limitations.
 |
| </p></keyConsiderations> |
| <skills><ul class="noindent"> |
| <li> |
| Knowledge of the relevant business area goals and the organisation politics |
| </li> |
| <li> |
| High-level view of how the computer system should function to support the business |
| </li> |
| <li> |
| Good communication skills |
| </li> |
| <li> |
| Ability to disseminate knowledge and ideas. |
| </li> |
| </ul></skills> |
| <assignmentApproaches><p> |
| Ambassador Users should have a positive attitude towards the development since they will be exposed to a whole raft of |
| new ideas and technologies that can be daunting. |
| </p> |
| <p> |
| <span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-GB; mso-fareast-language: EN-US; mso-bidi-language: AR-SA"> |
| For some critical projects, it may be necessary for Ambassador Users to be on the project full-time, but this is often |
| not possible and may even be counter-productive.</span> It is perfectly acceptable for an Ambassador User to be |
| part-time. However, the presence on the project needs to be continuous, e.g. at specified times of the day and/or on |
| agreed days of every week. |
| </p></assignmentApproaches> |
| </org.eclipse.epf.uma:RoleDescription> |
