Project Charter Terminology
Term | Definition |
---|---|
Project | The body of deliverables and work performed by an organization one time to produce a unique outcome. A project has a definite beginning and a definite end. |
Sponsor | The person or group that provides the financial resources, in cash or in kind, for the project. |
Stakeholder | An internal or external individual or organization with a vested interest in achieving value through a particular outcome. |
Service Owner | The person who is accountable for the delivery of the end-to-end service. The liaison between the Business and IT Services. |
Project Manager | The person who is responsible for the management and execution of the project from initiation to completion. Works closely with the service owner and solution architect to develop a project plan, deliverables and manage the task assignments. |
Solution Architect (formerly Technical Lead) | The person responsible for technical design and decisions of the system being implemented. |
Enterprise Architect | Technical architect for the IT Services organization whose primary responsibility is the implementation of overall architectural standards for systems and applications in the ITS portfolio. |
Requestor | Any user, customer, or business stakeholder who makes use of or has a vested interest in the service. A project is typically requested by the business process owner in coordination with the service owner after an advisor or governance body determines the need. |
Governance Committee | Provides strategic leadership, establishes campus-wide IT priorities and policies, and is accountable and transparent to the University community. |
Advisory Group | Provides focused input regarding specific campus business processes, needs, and improvements. Escalates key decisions to Governance Committee. |
Business Unit | The campus business unit who is accountable for or otherwise involved in the business process. |
ITS SMT | IT Service Senior Management Team, responsible for strategic alignment, stakeholder management, and service delivery of campus IT services. |
PPMO | The Project Portfolio Management Office, responsible for the maintenance and governance of ITS projects, tools, resources, frameworks and guidelines for efficient project management. |
Project Team | A group of individuals with key roles and responsibilities for delivering some or all components of a project. |
Project Go-Live Date | The date, agreed by core project team, upon which the system is made available for use in a live environment. |
Project End Date | The date when all activities scoped within the project are completed including closeout activities, service transition, and resources are released from the project. |