Project Charter - Revision history

Cristelags at 22:07, 16 October 2018

2018-10-16T22:07:13Z

← Older revision		Revision as of 18:07, 16 October 2018
Line 1:		Line 1:
	This section covers project charters and memorandum of understandings. Please contribute additional information or other examples to the '''[[DLF Project Managers Toolkit]]'''.		This section covers project charters and memorandum of understandings. Please contribute additional information or other examples to the '''[[DLF Project Managers Toolkit]]'''. If you have examples to share, please provide some context, such as the purpose or goal, institution, teams and team size, etc.


	=== Project Charter ===		=== Project Charter ===

Cristelags: Added content

2018-10-16T22:03:15Z

Added content

@@ Line 1: / Line 1: @@
 The goal of a [[Project Charter]] is to document agreement between all parties (sponsor, stakeholder, staff) about the goals, scope, and deliverables of the project. Ideally, the document defines time, scope and cost.
@@ Line 34: / Line 38: @@
      Rewrite
      Repeat until consensus
 A Memorandum of Understanding can be used to build out a project charter and be used to manage expectations, project planning and increase transparency, communication and understanding. The University of Texas Arlington hosts a [https://rc.library.uta.edu/uta-ir/handle/10106/25646 Memorandum of Understanding Collection] which was developed by a group of librarians for library specific projects and includes a workbook and templates.

Cristelags: Created page with "The goal of a Project Charter is to document agreement between all parties (sponsor, stakeholder, staff) about the goals, scope, and deliverables of the project. Ideally,..."

2018-10-16T21:55:38Z

Created page with "The goal of a Project Charter is to document agreement between all parties (sponsor, stakeholder, staff) about the goals, scope, and deliverables of the project. Ideally,..."

New page

The goal of a [[Project Charter]] is to document agreement between all parties (sponsor, stakeholder, staff) about the goals, scope, and deliverables of the project. Ideally, the document defines time, scope and cost.

It is useful to use this time to answer questions about cost/benefit and the extent to which people can actually reasonably contribute to the project. The Project Management Group recommends discussing the following questions at this stage:

'''Why?'''
What are the objectives of the project?
What are the expected benefits of the project?
'''Scope?'''
What is the scope of the project? (specifically, what's not in scope...)
How will we know the the project is done?
'''Who are the stakeholders?'''
Who is the end user audience?Who?
Who is going to work on the project?
Who is managing the project?
Who is/are the sponsors of the project?
'''How much time can participants reasonably spend on the project'''

[[File:Digital_Project_Charter_Template.docx|Digital Project Charter Template Example]]

After the answers to these questions have been decided upon, the Project Charter itself should be drafted. The following is the basic format of a Project Charter:

Project name
Description (high-level statement of your project goal)
Success criteria (how will we know when the project is done?) – SMART goals
Requirements (deliverables, options, & out of scope)
Project team (including roles)
Milestones/Schedule (high-level + proposed dates)

Drafting the charter is an iterative process:

Write a draft
Share it with project team
Share it with stakeholders
Rewrite
Repeat until consensus

A Memorandum of Understanding can be used to build out a project charter and be used to manage expectations, project planning and increase transparency, communication and understanding. The University of Texas Arlington hosts a [https://rc.library.uta.edu/uta-ir/handle/10106/25646 Memorandum of Understanding Collection] which was developed by a group of librarians for library specific projects and includes a workbook and templates.