A team charter is used to clarify and gain consensus on the role and responsibilities of a product team.

TEAM  CHARTER

Kenneth Crow
DRM Associates

2001 DRM Associates  All rights reserved.
Approved for personal use with attribution. Permission required for other use.

Product Development Forum
NPD Body of Knowledge
Team Charter Example
Product Development Teams
DRM Associates

The team sponsor (product/project manager) either gives or works with the team to define its mission or objectives based on a project/product need. This is documented in the form of a team charter.

A charter is...

A declaration or document setting forth the aims and principles of a group

Webster's New World Dictionary

A team charter is a clear description of the team's mission, as well as the authority and resources provided to accomplish that mission. The charter typically includes a statement of mission, objectives or statement of work; background; authority or boundary conditions (scope, constraints, resources, and schedule); membership; requirements or specifications, and interface responsibilities. (See team charter example.)

The charter should be specific enough to get the team started in the right direction, but not so limiting as to dictate process or outcome at the outset. Teams will establish more specific goals and plan once they comprehend the scope of their work, and the original charter may be re-negotiated with the sponsor.

At The Outset: Confusion, conflicts, or disagreements about the charter must be resolved to the mutual satisfaction of the team and sponsor as soon as possible. Negotiate to change the initial mission, broaden or narrow its scope, or shift its focus. The team charter provides a common vision that keeps a team focused on its objective.

During the Project: the charter:

  • Serves as a contract between the team and the sponsor
  • Defines objectives and intent of the team - assures a common objective among team members
  • Defines the work effort and its intended results to the rest of the program - avoids redundancy and "holes"
  • Keeps the team focused - allows the team to determine if its activity is relevant and on-track or off on a tangent.
  • Defines boundary conditions and helps the team determine when to raise an issue
  • Helps control scope of team's efforts and re-negotiate its objectives or boundary conditions