Project Charter
The project charter formally authorizes a project or phase and describes the initial understanding of scope and requirements that satisfy the stakeholders’ needs and expectations. It defines the project W5+ characteristics
- What the project is for – scope outline
- Why the project is being undertaken – business benefits
- Who will be undertaking the project and who will be impacted – identify stakeholders
- When the project will occur – schedule outline
- Where will the project be done – logistics outline, resources required
- How the project will be undertaken – approach outline
When working on an Agile project the initial statement of work might be deliberately light on detail since it is anticipated that more accurate details will best emerge through iterative prototype evaluation rather than further upfront analysis. Also, the contract being used may be an Agile inspired contract that seeks “fitness for business purpose” rather than exact specification compliance.
If this is the first use of Agile methods in an organization then the Project Charter should explain any new approaches that will be used to set expectations, such as iterative development, increased business involvement, empowered teams, frequent retrospectives, etc.