# Project Charter

Refer to
["Project Charter - Agile Project"](http://web.archive.org/web/20100412014125/http://analytical-mind.com/2009/08/12/project-charter-agile-project/),
["What Should an Agile Project Charter Contain?"](https://www.infoq.com/news/2010/05/agile-project-charter/),
and
["A Guide to the Project Priorities (Prioritization) Matrix"](https://www.indeed.com/career-advice/career-development/project-priorities-matrix)
for additional guidance.

## Vision

> Why do this work?  What challenges do we face?

% TODO: Write just enough of a vision statement with the bottom line
% up front.  Everything else is optional, but if omitting a section,
% include something about the project's objectives, success criteria
% (including the deadline if any), constraints, risks, or stakeholders
% in the vision statement.

## Objectives

> What will this project do?  What's our mission?

% TODO: Write just enough of a mission statement with the bottom line
% up front.  Note the project's deadline, if any.  Complete sentences
% aren't necessary but might look nice.

## Success Criteria

> What effects or outcomes should this project have?

% TODO: Outline the relevant high-level business goals.  Again,
% complete sentences aren't necessary but might look nice.

## Project Priorities

> How is this project constrained?

% TODO: Work with stakeholders and project team members to set
% priorities.

|                                 | Time<br>(Schedule) | Cost<br>(Budget) | Scope<br>(Boundary) |
|--------------------------------:|--------------------|------------------|---------------------|
|   Constrain<br>(Not negotiable) |                    |                  | ✅                  |
| Accept<br>(Difficult to Change) |                    | ✅               |                     |
|         Enhance<br>(Negotiable) | ✅                 |                  |                     |

## Risks

> What might make the project exceed a constraint or alter a priority?

% TODO: List things that might make the project exceed a constraint or
% alter a priority.  Describe any mitigations, if possible.  For
% example, a dependency on an external, incompletely specified process
% would delay a project that is time-constrained.  Mitigating this
% might require prioritizing work items related to communicating with
% the third party that owns the process and documenting it in detail
% well in advance of the deliverables that depend on it.  Mitigations
% can be stated a simply as "We need to work on this hard thing
% immediately or accept any delays it might cause."  We aren't writing
% _un chef d'œuvre_ here.  And again, complete sentences aren't
% necessary but might look nice.

## Stakeholders

> Who depends on the project's success?

% TODO: List individual stakeholders here---name, contact info, the
% organization they represent, their business role.  If stakeholders
% have OpenProject accounts, add them to this project with the
% `Reader` role.  Don't bother listing the project's scrum master and
% project team members.  We can all see those in the project
% membership list.