# Team Agreements and Purpose Establishing a shared understanding of the team's agreements, identity, and purpose is crucial for fostering a cohesive and effective team. This involves defining the team's core values, clarifying the purpose behind their product, and establishing guidelines for collaboration. ## Example At a SaaS company like GitLab, the Product Manager might lead a team workshop focused on collectively defining the team's shared values, aligning on the team's purpose, and establishing working agreements. During a dedicated session in the team's weekly meeting, the Product Manager guides the discussion on decision-making processes and communication norms. To ensure efficiency, the Product Manager, along with the engineering manager, outlines high-level items in advance. The team covers topics such as what their team goals are, the product areas of focus, and current objectives for the quarter or month. These objectives are directly tied to the projects, features, and improvements the team is working on, as well as the company's overarching objectives. The outline may also include details on team-wide meetings, Definition of Done agreements, agreeing to have every piece of work tracked with a ticket, and criteria for complete and detailed product and engineering tickets. ## Pain Points Ensuring that all team members feel heard and represented during the process of defining the team's identity, purpose, and agreements can be challenging. Regularly revisiting and updating these aspects is crucial to accommodate changes and support team growth. ## Practical Exercise Initiate a discussion with your team to define or reassess your team's identity, purpose, and agreements. Evaluate how well these align with your product goals and make any necessary adjustments. ## Related Research Topics * Team charter \[ [Google](https://www.google.com/search?q=Team%20charter%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Team%20charter%20in%20product%20management) ] * Value alignment \[ [Google](https://www.google.com/search?q=Value%20alignment%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Value%20alignment%20in%20product%20management) ] * Team-building exercises \[ [Google](https://www.google.com/search?q=Team-building%20exercises%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Team-building%20exercises%20in%20product%20management) ] * Team agreement \[ [Google](https://www.google.com/search?q=Team%20agreement%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Team%20agreement%20in%20product%20management) ] * Acceptance criteria \[ [Google](https://www.google.com/search?q=Acceptance%20criteria%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Acceptance%20criteria%20in%20product%20management) ] * Definition of done \[ [Google](https://www.google.com/search?q=Definition%20of%20done%20in%20product%20management) | [Perplexity](https://www.perplexity.ai/?q=Definition%20of%20done%20in%20product%20management) ] --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://www.pmguidebook.com/people-skills/building-relationships/team-agreements-and-purpose.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.