Project: [project name]

Project Charter and Plan Lite

For Class I and II Projects

IT Management Champion:
Submitted by:
Lead:
Project Team:
Date: / Version:

Instructions:

This tool has been divided into sections to match the logical flow of Class I and II projects. Approval (in the form of a signature or a pasted approval from an email) is required to pass from one section to the next. These sections are clearly indicated within the tool. Every effort was made to optimize efficiency and minimize paperwork.

Part 1: What are we trying to accomplish?

1.1.Project Description (required)

1.2.Business Need / Opportunity (required)

1.3.Project Results, Products, Objectives (optional)

1.4.Project Scope (required)

1.5.Constraints (optional)

1.6.Project Stakeholders

Stakeholder / Department / Comments

1.7.Roles & Responsibilities Project Planning & Work Team Members

Team Member / Role / Responsibilities / Planning or Work Team Member or Both?

1.8.Quotes (for equipment, maintenance, education, budget approved and purchase completed) (optional)

1.9.Acceptance Criteria and Success Factors (list specific parameters for completion and success) (required)

Success Criteria or Quality Metric / Measureable? IF so, how? / Comments / Approved after delivery?

1.10.Back-Out Plan (optional)

1.11.Assumptions (optional)

1.12.Project Requirements

Requirements may be divided into components (Technical, Business, Architecture, Training, Quality, etc.)

Requirement / Technical or Business Requirement? / Comments / Will this be included in the test plans?

STOP! – Before continuing with project have your IT Management Champion sign off on all sections through 1.9

1.13.Project Charter Approvals (required)

Approval may be pasted from an email and inserted into this space.

IT Management Champion / Approval for sections through 1.12 / Signature and Date

2.0 Design

Design Options- Provide diagrams or schematics if appropriate

Design Option 1 / Pros / Cons
Design Option 2 / Pros / Cons

2.1 Design Recommendations

Specify the preferred design recommendation resulting from team consensus.

Approval may be pasted from an email and inserted into this space

STOP! – Before continuing with project have your IT Management Champion sign off on all section 2 (Design) before continuing

IT Management Champion / Design Approval / Signature and Date

3.0 High-level tasks, milestones (required)

Major Deliverables and their associated tasks may be divided into components. Milestones are required to be entered here; tasks may be captured using another tool that all team members can access, e.g. Cherwell, MS Project, etc.

Project Task/Milestone / Responsible Person / Date Due or Expected Completion
Milestone 1
Task 1.1
Task 2.1
Task 3.1
Task 4.1
Milestone 2
Task 2.1
Task 2.2
Task 2.3
Task 2.4
Milestone 3
Task 3.1
Task 3.2
Task 3.3
Task 3.4

3.1 Risk Log

Risks may be documented outside of this document on the project SharePoint Site if applicable (or any other collaborative site that is approved by the team)

Risk and Date Logged

/

Severity and Likelihood of Triggering

/

Status (has the risk triggered?)

/

Comments and Mitigation Strategy

3.2 Issues & Decision Log

Issues and Decisions may be documented outside of this document on the project SharePoint Site if applicable (or any other collaborative site that is approved by the team)

Issue or Decision

/

Date logged

/

Comments

/

Other

3.3 Recommendations for Transition to Operational Support

Part 4: Project Closure

A summary of the results of the project, how well objectives were met, and accountability for remaining activities and ongoing processes.

4.1 Project Results (Compare to Acceptance Criteria)

Task or Objective or Requirement / Status as of Closure
Was it met? / Accountability for Follow-up and Completion

4.2 Lessons Learned

Lessons learned should be forwarded to the PSMO so they can be added to the UNM IT master list of Lessons Learned.

Lesson Learned / Comment / Accountability for Follow-up and communication to PSMO

4.3 Ongoing Ownership

Product or Ongoing Process / Owner

4.4 Location of Project Repository (wiki, SharePoint, Confluence)

4.5 Project Closure Acceptance

The IT Management Champion accepts the results of the project and assumes responsibility for the outstanding issues and ongoing operational processes.

This approval may be cut and pasted from an email.

Date Reviewed:

IT Management champion: (Name)

Comments:

______(signed)

1

Project Charter Lite template v3.0 May 2015