Project – a temporary endeavor undertaken to create a unique product, service or result. It has a defined beginning and end, and therefore, defined scope and resources.

Tier 1 Projects (Strategic Projects) – projects that are the most visible to the campus community and appear on the division’s strategic plan. These projects are typically resource intensive and utilize resources from multiple units within and external to the Information Technology Division. Therefore, these projects should exhibit the most stringent level of project management to ensure success throughout the duration of the project.

Tier 2 Projects (Key Projects) – highly visible projects within the campus community that would have a significant impact on the university or the reputation of the division should they be perceived unsuccessful. Therefore, these projects should exhibit a strong level of project management to ensure success throughout the duration of the project.

Tier 3 Projects (Local) – all projects that are not categorized as Tier 1 or Tier 2.

Gantt Chart – a graphic display of schedule-related information which may vary in detail from high-level milestones to complex work breakdown structures.

Project Management Plan (PMP) – a formal, approved document that defines how a project is executed, monitored, controlled, and closed. It may be summarized or detailed and may be composed of one or more subsidiary management plans and other planning documents.

Milestone – a significant event in a project that occurs at a point in time. Certain project milestones should be submitted for inclusion into the IT Division’s milestone visibility process.

Project Sponsor – the person or group that provides the financial resources, in cash or in kind, for the project.

GUIDELINES AND PROCEDURES

Determination of the appropriate tier for a project shall be done by utilizing a rubric found here. The vice president for Information Technology (VPIT) may make an exception to the tier of a project.

Each project tier has a specific set of minimum requirements as outlined in the table below.

Requirements

Tier 1/Strategic

Tier 2/Key

Tier 3/Local

Business Case Summary

Business case summary should be a one- to two-page document outlining the justification and relevance for the project, including any clear relationship to university and divisional goals and initiatives, opportunities and benefits, and pertinent design decisions.

Business case summary should be a one- to two-page document outlining the justification and relevance for the project, including any clear relationship to university and divisional goals and initiatives, opportunities and benefits, and pertinent design decisions.

Business case summary is encouraged but optional and most likely would be included within the charter scope.

Project Manager (PM) Assignment

The Project Management Office (PMO) will provide PM services to the project at this level.

The PMO will provide PM services to the project at this level unless a PM within a department that is more suited is identified.

PM roles are assigned by the appropriate associate vice president (AVP).

Project Charter

The project charter shall utilize the IT Division’s standard charter template for Tier 1 and 2 projects. The project charter can be found here. Project charter must be signed by all key stakeholders of the project and IT Council (ITC).

The project charter shall utilize the IT Division’s standard charter template for Tier 1 and 2 projects. The project charter can be found here. Project charter must be signed by all key stakeholders of the project.

The project charter shall utilize the IT Division’s standard charter template for Tier 3 projects. The charter can be found here.

Project Management Plan (PMP)

A comprehensive PMP must be created and signed by the VPIT.

Some elements of a PMP are required at the discretion and approval of the appropriate AVP.

Only a project schedule is required.

Gantt Chart with Dependencies

The PM maintains accessible Gantt charts with task dependencies.

The PM maintains accessible Gantt charts with task dependencies.

Gantt chart is optional, but some method of schedule tracking must be implemented.

Resource (Staff) Assignments

The PMP must expand on the project charter to include individual resource assignments. All resources must sign off on their task commitments and schedules with approval from their immediate supervisor.

The PMP must expand on the project charter to include individual resource assignments. Resources not in the chain of command of the sponsor (usually AVP) must sign off on their task commitments and schedules with approval from their immediate supervisor.

This process is managed locally by the appropriate AVP.

Marketing and Communications Campaign Plan

A detailed marketing and communications campaign plan must be created, driven, and maintained by the IT Marketing and Communications coordinator as part of the project plan approval.

A clear marketing and communications campaign plan must be created and approved by the IT Marketing and Communications coordinator as part of the project plan approval.

At the discretion of the appropriate AVP, a marketing and communications plan must be created as part of the project planning process.

Issues Log

An issues log must be maintained and available to the project team and ITC as part of the PMP.

An issues log must be maintained and available to the project team and ITC.

This process is managed locally by the appropriate AVP.

Project Milestone

Pertinent project milestones meeting a criterion set by ITC must be applied to the divisional Project Milestone Chart.

Pertinent project milestones meeting a criterion set by ITC must be applied to the divisional Project Milestone Chart.

Milestones are at the discretion of the appropriate AVP or VPIT.

Project Reporting

A project progress summary report will be presented to ITC by the appropriate AVP monthly, to include any pertinent issues and mitigations.

A written project status report will be provided to ITC monthly.

Reporting can be done at ITC round table, when appropriate.

Budget Approval

The project budget must be introduced and approved by the VPIT as part of the business case summary and charter approval process.

The project budget must be approved by the appropriate AVP if no additional funding is required. If additional funding is required, it must be approved by the VPIT.

The project budget must be approved (or approval delegated) by the AVP of the area managing the project.

Project Closure

A formal project closure document including all the standard elements required is circulated for review and approval to the stakeholders and sponsors reflected in the charter.

A formal project closure document including all the standard elements required is circulated for review and approval to the stakeholders and sponsors reflected in the charter.

The sign-off completion process is managed locally by the appropriate AVP.

A project registry of open Tier 1 and Tier 2 projects shall be maintained by the PMO and made available to the ITC.

REVIEWERS OF THIS PPS

Reviewers of this PPS include the following:

Position

Date

Vice President for Information Technology

April 1 EY

Assistant Vice President for Information Technology, Business Operations

April 1 EY

Associate Vice President for Instructional Technologies Support

April 1 EY

Associate Vice President for Technology Resources

April 1 EY

Associate Vice President for University Libraries

April 1 EY

Chief Information Security Officer

April 1 EY

Information Technology Marketing and Communications Coordinator

April 1 EY

Project Management Director

April 1 EY

Special Assistant to the VPIT

April 1 EY

CERTIFICATION STATEMENT

This PPS has been reviewed by the following individuals in their official capacities and represents Texas State Information Technology policy and procedure from the date of this document until superseded.

Vice President for Information Technology; senior reviewer of this PPS