Team Charter

A written agreement created by the team that outlines shared values, working norms, and ground rules, and clearly sets expectations for acceptable conduct among project team members.

Key Points

  • Captures team values, norms, ground rules, and behavioral expectations.
  • Often includes decision-making methods, conflict resolution steps, and escalation paths.
  • Co-created early by the team and approved by key stakeholders to build buy-in.
  • Used as a living reference to guide day-to-day interactions and updated as needed.

Example

At the kickoff of a software project, the team drafts a charter stating values like transparency and respect, rules such as daily standups at 9:00 AM, code reviews before merges, decision-making by consensus with a tie-break by the tech lead, and a two-step conflict resolution process. The document is shared with all members and revisited during retrospectives.

PMP Example Question

Which project artifact primarily defines team values, working agreements, and acceptable behavior guidelines?

  1. Team charter
  2. Project charter
  3. Stakeholder engagement plan
  4. RACI matrix

Correct Answer: A - Team charter

Explanation: The team charter documents the team's values, agreements, operating guidelines, and behavior expectations. The project charter authorizes the project; the stakeholder plan addresses stakeholder strategies; the RACI clarifies roles and responsibilities.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Build the Sprint Reporting System, Not Another Prompt

AI Systems with Claude is our own course for Scrum Masters and Agile Project Managers, taught against one running project across eight teaching sections. You build five working systems and keep them: the sprint report machine, the retro intelligence system, the stakeholder comms engine, the backlog health monitor, and the risk and dependency tracker. Direct from HK School of Management and Technology, not on Udemy.

See What Is Included