        
 |
 |
|
|
|
|
|
|
 |
 |
|
|
Roles and Responsibilities
| Role |
|
Description and Responsibilities |
| Consultant |
|
A person who will be providing advice to the project team, but will not be responsible for any deliverables. |
| Data Steward |
|
The person who is the data owner, with responsibility for correct usage of the data. They may also be the subject matter expert (SME). |
| Functional lead |
|
A person who will lead the functional activities, who is empowered to provide functional requirements and signoff. They will also be responsible for development of the test plan and training materials. This is generally a subject matter expert, manager or director. They may also be the requestor. |
| Functional sponsor |
|
A person outside of IS who provides upper management support and ensures that adequate functional resources are committed to the project. This is generally an Associate Vice President/Associate Dean or above. |
| Functional team |
|
The group of people who will be responsible for performing functional tasks (e.g. setup, testing). |
| Project manager |
|
A person who ensures that the project is managed according to the plan, good project management practice and IS standards. |
| Project team |
|
The entire group of people who will be involved in task completion for the project, both functional and technical. |
| Requestor |
|
A person who requests a product or service from IS. They are responsible for the business case (including the ROI spreadsheet). |
| Subject matter expert |
|
A person who is an expert in the subject. They may also be the data steward. |
| Technical lead |
|
A person who will lead the technical activities, working closely with the functional lead. They are responsible for the technical project plan, technical specifications and implementation plan. This is the person listed as project leader in IPMS. |
| Technical team |
|
The group of people who will be responsible for performing technical tasks (e.g. installation, coding). |
TLC Artifact responsibility matrix
| Artifact |
Phase |
Description |
Responsible Role |
| Architecture review |
Plan |
Minutes of the architecture review meeting to determine if project proposal meets architectural standards. |
Project manager |
| Even swaps |
Plan |
This is the documented output of the even swaps process, which lists the features upon which a decision will be based and the importance attached to each, as well as the ratings of multiple solutions/products for these features. |
Functional lead,
Technical lead,
Project manager |
| Functional specifications |
Design |
List of functional requirements for project - i.e. how the end result must work in the functional area(s). |
Functional lead |
| Implementation plan |
Build |
Schedule for release of product/service to population. |
Functional lead,
Technical lead,
Project manager |
| IS Request Form |
Plan |
Narrative description of what the project is about, who it affects, and why it should be done. |
Requestor |
| Project charter |
Plan |
This is a narrative document documenting the scope and major deliverables for the project as well as the roles and responsibilities of the functional and technical team members. |
Functional lead, Technical lead,
Project Manager |
| Project cost worksheet |
Plan |
This is a spreadsheet with the estimated effort and cost estimates. |
Technical lead |
| Project plan |
Plan |
A list of tasks needed to complete the project, with responsible person and target date. |
Functional lead,
Technical lead,
Project manager |
| Technical specifications |
Design |
List of technical solution for each functional requirement and documentation of technical standards used. |
Technical lead |
| Test plan |
Design |
List of tests that will be performed to ensure that the product meets the functional requirements. |
Functional lead |
|
|
|
