University of New England
<Insert Project Name>
Project Charter
TABLE OF CONTENTS
1 PROJECT PURPOSE AND JUSTIFICATION...3
2 PROJECT SCOPE AND DELIVERABLES...3
3 PROJECT RESOURCES...3
4 PROJECT CRITICAL SUCCESS FACTORS/BUSINESS OBJECTIVES...4
5 PROJECT ACCEPTANCE CRITERIA...4
6 PROJECT HIGH LEVEL ASSUMPTIONS...4
7 PROJECT HIGH LEVEL RISKS AND MITIGATION...5
8 PROJECT ROLES AND RESPONSIBILITIES...5
9 PROJECT PHASES AND KEY MILESTONES...5
10 IMPLEMENTATION PLAN...6
11 ESTIMATED PROJECT SIZE/COMPLEXITY...7
12 DOCUMENT HISTORY...7
1 Project Purpose and Justification
Insert purpose and business justification for the project. This should provide an overview of the current business environment (i.e. problem that needs be resolved or opportunity to be seized); what the solution will achieve; and why the project should be undertaken (i.e. why it’s worth doing).
2 Project Scope and Deliverables
Project Scope defines the objectives or items that are considered in-scope for the project. These scope statements should be matched with the acceptance criteria (section 4) and critical success factors (section 5), and together will be used to determine project completion and success. Out-of-scope items should be noted for any specific objectives or items that may be discussed as potentially in-scope but were then specifically ruled out. This serves to clarify what is specifically in and out of scope for this project.
Deliverables may list a specific set of expected deliverables that the project is to produce as part of achieving the scope (i.e. user manuals; training
documents/sessions; software installations, etc.)
In Scope:
Item One
Item Two
Out of Scope:
Item One
Item Two
Deliverables:
Item One
Item Two
3 Project Resources
Project Team Members
Name Role Title/Organization
Business Owner* Project Coordinator* Business SME Technical SME
Name Role Title/Organization
Senior Administrator* Stakeholder
Stakeholder
*Required for all projects
4 Project Critical Success Factors/Business Objectives
Success Factors / Business Objectives are measurements of project success. The defined success factors must be met to consider the project a success. These factors may include measurable improvements in process efficiency, increased functionality; reduced costs; etc. and should be derived from the project scope and deliverables.
1. Insert success factors and business objectives for the project 2. Success2
3. Success3
5 Project Acceptance Criteria
Project acceptance criteria provides specific measurements for determining the scope and deliverables defined for the project have been met and provides inputs into project sign-off documentation.
General Acceptance Criteria:
All issues and action items have been completed and signed off All required deliverables have been produced
Deliverables meet the project requirements
All known deficiencies have been either resolved, accepted, or accepted with post-implementation resolution action plans
Project Specific Acceptance Criteria:
Criteria 1 – based on specific project requirements / scope statements Criteria 2
Criteria 3
6 Project High Level Assumptions
Assumptions are conditions that are considered to exist inside or outside the project environment that are necessary to project success. These may include things such as assuming that an underlying technology or system will not change; required personnel will be available when needed; related systems will be
available; RFP’s will receive acceptable response(s), etc.
2. Assumption2 3. Assumption3 4. Assumption4
7 Project High Level Risks and Mitigation
Project risks are anything known that may be a risk to project success. Risks may include unavailability of key personnel, inadequate budget, inadequate technology to achieve objectives, timeline constraints, etc. Include known risks and a short description of the mitigation strategy to minimize or respond to the risk. If needed, a separate, more detailed risk log may be maintained for the project as it
progresses.
8 Project Roles and Responsibilities
Project roles and responsibilities may be included here or by reference to a roles and responsibilities document that describes standard project roles
9
Project Phases and Key Milestones
Project Phases
Initiation Phase – Initiate project with high-level project charter, prioritize project; obtain approval to proceed to detailed Planning.
Planning Phase – Develop detained project charter, requirements budget, timeline, and obtain approval to proceed to Execution.
Execution Phase – Execute project tasks, resolve issues, complete testing, prepare for implementation; obtain approval to proceed with Implementation.
Implementation Phase – Move project deliverables to production state, verify project scope is complete; obtain approval to proceed with project Closeout.
Closeout Phase – Complete project closeout activities, transition any required items to support status, communicate project success.
Key Milestones
10
Implementation Plan
Include or reference the detailed implementation tasks, schedule and milestones here.
Initiation Phase
Task/Milestone Start Date End Date Complete?
Planning Phase
Task/Milestone Start Date Due Date Complete?
Execution Phase
Task/Milestone Start Date Due Date Complete?
Implementation Phase
Task/Milestone Start Date Due Date Complete?
Closeout Phase
Task/Milestone Start Date Due Date Complete?
11 Estimated Project Size/Complexity
The levels are not meant to be absolute but are used only as a planning guide. Very Small could be a project that can be completed in 2 – 4 weeks with minimal expense; Very Large could be a major software implementation.
12
Document History
Revision Record
Number Date Author Revision Notes
13 Attachments
Estimated Size
