Terminology

Many IT projects use certain terms or acronyms that may be unfamiliar to many people. Therefore, to reduce complexity and confusion, it may be useful to include a glossary giving the meaning of terms and acronyms, allowing all the project's stakeholders to use a common language. Figure 3.3 provides a template for a project charter. Feel free to adapt this template as needed.

Figure 3.3 Project Charter Template
Project Name or Identification
Project Stakeholders

  • Names
  • Titles or roles
  • Phone numbers
  • E-mail addresses

Project Description

  • Background
  • Description of the challenge or opportunity
  • Overview of the desired impact

Measurable Organizational Value (MOV)

  • Statement or table format

Project Scope

  • What will be included in the scope of this project
  • What will be considered outside the scope of this project

Project Schedule Summary

  • Project start date
  • Project end date
  • Timeline of project phases and milestones
  • Project reviews and review dates

Project Budget Summary

  • Total project budget
  • Budget broken down by phase

Quality Issues

  • Specific quality requirements

Resources Required

  • People
  • Technology
  • Facilities
  • Other
  • Resources to be provided
    • Resource
    • Name of resource provider
    • Date to be provided

Assumptions and Risks

  • Assumptions used to develop estimates
  • Key risks, probability of occurrence, and impact
  • Constraints
  • Dependencies on other projects or areas within or outside the organization
  • Assessment project's impact on the organization
  • Outstanding issues

Project Administration

  • Communications plan
  • Scope management plan
  • Quality management plan
  • Change management plan
  • Human resources plan
  • Implementation and project closure plan

Acceptance and Approval

  • Names, signatures, and dates for approval

References
Terminology or Glossary
Appendices (as required)

Back to '3.1: Business Case'