How we communicate

Which channels, reply times and availability should we agree?

Urgent issues go in the team channel with a mention, never in a direct message.
We reply to direct messages within half a working day.
Core hours are 10:00 to 15:00 in each person's time zone, and nobody expects replies outside them.
How we work together

How should we run meetings, reviews and handoffs?

Every meeting has an agenda in the invite, or it gets declined.
Meetings start on time and finish five minutes early.
Reviews get picked up within one working day.
How we decide

How will we make, record and own decisions?

The person doing the work makes the call on implementation details.
Decisions that affect other teams go through the weekly sync.
We log decisions with the date and the reason in the team wiki.
When we disagree

What do we do when we disagree or slip?

Disagree in the meeting, then commit to the decision once it's made.
Give feedback to the person directly, in private, before raising it with anyone else.
Assume good intent and ask questions before judging.

What are team working agreements?

Every team runs on rules nobody wrote down: how fast people reply, whether cameras stay on, what happens when two people disagree. Team working agreements write those rules down. They are a short list of norms the whole team proposes and signs up to, so long-standing members and new joiners work to the same expectations. Teams also call them team agreements, team norms or a social contract. Most working agreement and team agreement templates are a document one person fills in. Here, the whole team builds the list in one retrospective. The board has four columns: How we communicate, How we work together, How we decide and When we disagree. Everyone adds proposed agreements privately, then the team groups similar proposals and votes for the ones it wants to keep. In the discussion, the facilitator adds each winning proposal to the team's agreements in TeamRetro. If the facilitator allows it, participants can propose agreements too, and the facilitator accepts or rejects each one. Your team's agreements then appear in the Agreements panel of every TeamRetro meeting and on the team's page, so they stay in front of the people who made them. A team charter covers more ground, such as purpose, goals and roles. Working agreements are its day-to-day part. Run this template again when people join or leave, when the way you work changes, or when the same agreement keeps getting broken.

Working agreements retrospective format

How we communicate

Which channels, reply times and availability should we agree?

Cover how people reach each other, such as which channel to use for what, how quickly people should reply, core hours and how to show you're unavailable. Ask for each proposal to be worded as an agreement, such as "We reply to direct messages within half a working day", so every card is ready to vote on.

How we work together

How should we run meetings, reviews and handoffs?

Turn to the habits around shared work, such as meetings, reviews, handoffs, pairing and focus time. Ask what slowed the team down recently and which agreement would have prevented it. Keep proposals about the whole team's behavior, not one person's.

How we decide

How will we make, record and own decisions?

Agree who decides what, and how. Teams often argue about outcomes when the real gap is the process, such as who needs a say, when a quick call is fine and where decisions get written down. Agreements here prevent the "I thought we agreed" conversations later.

When we disagree

What do we do when we disagree or slip?

Agreements only last if the team knows what to do when one gets broken. Ask how people want to raise disagreement, give feedback and remind each other of the list. Anonymous ideas in TeamRetro help here, because these are the agreements people find hardest to propose out loud.

When to use this retrospective

  • A new team is forming, or two teams are merging, and nobody has said out loud how the team will work together.
  • The same friction keeps coming up in retrospectives, such as slow replies, meetings that overrun or decisions nobody wrote down.
  • Several people have joined or left, and the expectations the team used to share no longer match.
  • The team has moved to remote or hybrid work and needs new norms for availability, meetings and channels.
  • Your team has working agreements, but they are old enough that nobody can remember what they say.

Suggested icebreaker questions

  • What's one unwritten rule from a past team that you wish someone had written down?
  • What's a small habit of a teammate that made your work easier?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Ask for proposals worded as behavior the team could see, such as "Meetings start on time", not values such as "Be respectful". A value is hard to keep and harder to check.
  • Keep the final list short. Vote, then accept the top handful of proposals. A list nobody remembers isn't a working agreement.
  • Before you accept an agreement, ask whether anyone can't live with it. One objection nobody voiced is enough to make it fail.
  • Give everyone a few minutes to add proposals privately before the discussion starts, so quieter people and new joiners are heard.
  • Include everyone who works in the team day to day, including the product owner and remote members. Agreements written by part of the team only bind that part.
  • Plan the next review before you finish. Revisit the list when people join or leave, and drop the agreements the team no longer keeps.

Frequently asked questions

What is a team working agreement?
It's a short list of norms a team writes together about how it works, such as how people communicate, run meetings, make decisions and handle disagreement. The team keeps it visible and changes it when an agreement stops helping. Teams also call it team agreements, team norms or a social contract.
Can you provide an example of a working agreement?
"Core hours are 10:00 to 15:00 in each person's time zone, and nobody expects a reply outside them." It names the behavior, when it applies and what others can expect, so anyone on the team can tell whether it's being kept.
What are some good team agreements?
Good team agreements are specific enough that anyone can tell when one is broken. Common ones include "Every meeting has an agenda in the invite," "Reviews get picked up within one working day," "Decisions made in a call get written up in the team channel" and "We raise disagreements in the meeting, not afterward."
How do you create a team working agreement?
Get the whole team in one session. Everyone proposes agreements privately, the team groups similar proposals and votes, then discusses the top few until everyone can live with the wording. This template follows those steps in TeamRetro, and the facilitator adds each winner to the team's agreements.
What should be included in a team contract?
A team contract, often called a team charter, usually covers the team's purpose and goals, who it serves, roles, how decisions get made, how people communicate and how conflict is handled. Working agreements are the day-to-day part. To check later how well your team keeps its charter and agreements, run the Team Charter & Working Agreements Check health check.
Ready to run this retrospective?Try this retrospective live