Behavior-focused proposals
Capture observable ways of working instead of abstract values that mean different things to everyone.
MAKE EXPECTATIONS EXPLICIT
Create team working agreements with examples and live voting
Working agreements turn invisible expectations into behaviors the team can discuss and improve. Participants propose concrete norms, vote on what matters and use the strongest signals to build a small agreement set the team can remember.
Start free ↗No login · Share one link · Live collaboration
What you can do with team agreements
Team voting
Let the group signal which proposed agreements deserve commitment and discussion.
Editable shared record
Update language as the team learns, with author and Scrum Master moderation controls.
Five working agreement examples to adapt together
Start with one behavior your team wants to improve. Discuss exceptions and agree when you will review it; votes start a conversation, and concerns still deserve to be heard.
- Focus time: we protect two agreed hours without optional meetings and mark urgent exceptions clearly.
- Code reviews: we acknowledge a review request within one working day and flag when we need help.
- Blocked work: we raise a blocker in the shared board as soon as we notice it and name the next person who can help.
- Decisions: we record the decision, its owner and the reason in a place everyone can find.
- Retrospectives: we leave with at most two experiments and review their outcomes at the next retro.
FACILITATOR PLAYBOOK
How to run it well
Keep the mechanics simple so the team can focus on the conversation.
- Surface friction and needs
Ask where coordination, feedback, focus or decision making currently breaks down.
- Propose observable behavior
Write what teammates will actually do when the situation occurs.
- Agree and revisit
Choose a small set, define how the team will notice drift and review them after a few sprints.
SCRUM MASTER TIPS
Small choices that make the activity better
- Use language the whole team can explain.
- Include what happens when an agreement is missed.
- Retire agreements that no longer solve a real problem.
Frequently asked questions
What makes a good working agreement?+
A strong agreement is specific, observable, relevant to a real team need and easy to revisit.
Can the team vote on agreements?+
Yes. Participants can support proposals so the group knows where alignment is strongest.
Can agreements change later?+
Yes. The board supports editing and is intended to evolve with the team.
BETTER RETROS · STRONGER TEAMS
Start this tool ↗