(template) Project Charter: [Project name]

Statement of Need

Describe what the project necessitates

• Existing need or problem that requires project focus:
• Historical context of the situation:
• Alternatives considered:
• Reference business case (if applicable):
• Project goals:

Users and Support

] List intended end-users, benefiting audience, and support chain

• End-users and/or benefiting audience
  • (Group) will use this product
  • (Group) will benefit from or see the results produced by this product
• Support Chain
  • (Group) will provide functional support to end-users/benefiting audience
  • (Group) will provide administrative support to end-user group
  • (Group) will provide technical support for back-end issues

Deliverables and Requirements

List and briefly describe what will be delivered

• Deliverables of the project
  • Mandatory:
  • Optional:
• Objective used to determine the definition of completed (done):
• Plan for transition from current state to desired future state:
• Plan for continuous improvement:

Statement of Work

Explain the project approach and high-level steps

• Describe the work to be completed:
  • How will the team work together to complete the project?
• Methodology that will be used: (traditional, Scrum, Kanban)
• End-user acceptance testing method:
  • End-user population: (students, faculty, staff/office)

Triple-constraint Priorities: Time, Resources, Scope

List and briefly explain any constraints to delivery. Indicate which constraints are fixed (maximized) and which have flexibility.

• Time
  • Estimated schedule of tasks and events needed to complete the project:
  • Is there a drop-dead date for delivery? Is there a range of preferred delivery? Is the project time-boxed?
• Resources
  • Estimated staff resources needed to complete the project:  
    • Add population for end-user testing:
  • Can team members be added? Is hiring contractors an option? Do resources have other priorities at any point during the project?
• Scope
  • Estimated tasks and activities required to manage the project and produce deliverables:
  • Key milestones:
  • Anticipated performance of contractors, vendors and suppliers:
  • Would the project be delivered late in order to get to a base-level of completion of the deliverables? How well is the scope understood? Can users easily add new deliverables or features throughout the project?

Out of Scope

List and briefly explain any feature or condition that one might assume is included in the project, but is not.

• (Feature that will not be delivered)
• (Feature that will not be delivered)

Assumptions

List and briefly explain conditions or situations that are expected to persist during the project life cycle, but could produce consequences for the project if changed.

• Assumptions made in regard to:
  • Estimated staff resources needed to complete the project
  • Estimated tasks and activities required to manage the project and produce deliverables
  • Anticipated performance of contractors, vendors and suppliers
  • Estimated schedule of tasks and events needed to complete the project
  • Use and applicability of project management standards

Known or Potential Risks

List and briefly explain conditions, situations, or events that could negatively affect project outcome, if they were to occur. Consider schedule, resources, technology, scope, vendor performance, communication, funding, quality, internal factors, and external factors.

• (Known or potential risk)
• (Known or potential risk)