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.