LTS Project Charter Template

Directions: Copy and use this charter and related resources prior to a new project kickoff; some information may be filled in at the kickoff meeting. Additional HUIT resources and templates. Glossary.

Project Name

Project Goals

Problem and Value Statements

Problem Statement

Solution Business Value

Alignment with Harvard Library Multi-Year Goals and Objectives

Alignment with HUIT Objectives

Vision

(Insert Vision table, as below)

<Project Name> Vision
(A vision statement that clearly and succinctly describes the desired future state from an academic or administrative perspective)
Strategic ObjectivesGuiding PrinciplesKey Performance Indicators









Approach

In Scope/Out of Scope

In Scope

Out of Scope

Deliverables and Work Products

Key Tasks and Outcomes

TaskOutcomeResponsible Parties









Definition of Done

Stakeholders

(Who is sponsoring the work? Who is funding the work? Who will accept the work? What organizations, departments, or people will benefit from this work? Link to /wiki/spaces/librarymeetings/overview where relevant.)

StakeholderTitleParticipation









Project Team

(Roles include: Product Owner, Project Manager, Scrum Master, Business Analyst, Quality Assurance Analyst, Architect, Software Engineer, Systems Engineer, UI Designer, Metadata Analyst, Subject Matter Expert, Release Coordinator)

Team MemberProject Role(s)Affiliation









Cost and Estimated Schedule

(Define the resource commitment, project phases with their associated activities, deliverables and milestones. Include a plan for transitioning to a stabilization phase, if needed, and then operations and maintenance. This section may not be relevant for projects for which schedule/date-based information is not available at the time the charter is being written. In that case, be sure to document the schedule, milestones, and deliverable dates in other ways with stakeholders and be transparent about accomplishing them.)

PhasePhase StartPhase EndCompletion Milestone












Assumptions, Constraints, Dependencies, and Risks

Project Assumptions

    • Stakeholders have identified the appropriate subject matter experts to participate in the Working Group and who can accurately and completely define the business requirements for the project
    • Stakeholders will have made available the time required to participate in project activities and to complete tasks as requested
    • Project sponsor and other stakeholders are empowered to make the decision required for the project to be a success
    • Project sponsor will provide written approval to move forward with system development when requested as part of incremental/iterative system demonstrations

Project Constraints

    • Scope
    • Time
    • Cost

Project Dependencies

Project Risks

DescriptionPlanImpactOwner
(Update during course of project as needed.)










Acceptance

Accepted by <Project Sponsor Name>, <Date>

Prepared by <Project Manager Name>

Effective Date: <Date>