✦ For everyone, free.

Practical knowledge for real and everyday life

Home

Team Working Agreements

Team Working Agreements define how agile teams collaborate, ensuring clarity, accountability, and alignment in project management practices.

Team Working Agreements are the explicit, collectively agreed norms and expectations that a team establishes for itself regarding how members will collaborate, communicate, and conduct their shared work, ranging from practical matters such as core working hours and preferred communication channels to deeper commitments such as standards for quality and how disagreements will be resolved. Because self-organizing Agile teams determine their own operational practices rather than following externally imposed rules, working agreements provide the mechanism through which a team converts its autonomy into concrete, shared expectations that hold members accountable to one another for how the team actually functions day to day.


The Purpose of Working Agreements

Converting Autonomy into Concrete Expectations

Team autonomy grants a team the freedom to determine its own working practices, but without an explicit agreement, that freedom can produce inconsistent, unstated assumptions among members about how the team should actually operate; working agreements make these expectations concrete and shared rather than left implicit.

Reducing Friction from Unstated Assumptions

Many sources of team friction arise from differing, unstated assumptions about acceptable behavior, such as response times or meeting punctuality; surfacing and agreeing on these expectations explicitly reduces the likelihood of recurring, low-grade conflict rooted in mismatched assumptions.

Team Friction = 1 Shared Understanding of Norms

Common Areas Covered by Working Agreements

Communication Expectations

Agreements often specify preferred channels for different types of communication, expected response times, and norms around availability, helping the team coordinate effectively without relying on inconsistent, individually assumed standards.

Meeting and Collaboration Practices

Working agreements frequently address how team events should be conducted, such as expectations for punctuality, preparation, and active participation, supporting the effectiveness of recurring Agile ceremonies.

Quality and Technical Standards

Teams often agree on shared standards for work quality, such as what constitutes acceptable completion of a task, aligning closely with the team's broader definition of done and supporting consistent technical excellence across contributions from different members.

Conflict Resolution Norms

Establishing an agreed approach for how disagreements within the team will be raised and resolved provides a constructive pathway for handling inevitable friction, rather than leaving conflict resolution to chance or avoidance.


Establishing Working Agreements

Collaborative Development by the Whole Team

Effective working agreements are developed collectively by the team itself, rather than imposed by an external party, since genuine buy-in depends on team members having a real voice in shaping the expectations they will be held to.

Keeping Agreements Specific and Actionable

Vague or overly general agreements provide little practical guidance; effective working agreements are specific enough that team members can clearly recognize when an agreement is being honored or violated.

Shared Working Agreements

Maintaining and Evolving Working Agreements

Revisiting Agreements Periodically

Because team circumstances and membership can change over time, periodically revisiting working agreements, often during retrospectives, helps ensure they remain relevant and genuinely reflect the team's current needs rather than persisting as outdated commitments no longer well suited to the team's actual situation.

Holding One Another Accountable

Working agreements only function effectively if team members are willing to reference and uphold them in practice, gently reminding one another when behavior drifts from what was agreed, rather than allowing the agreements to exist only as an unreferenced document.


Risks of Poorly Managed Working Agreements

Agreements That Exist Only on Paper

When working agreements are established but never genuinely referenced or reinforced in day-to-day practice, they fail to provide the practical benefit they are meant to deliver, reducing to a symbolic exercise disconnected from actual team behavior.

Agreements Imposed Rather Than Genuinely Adopted

Working agreements handed down without meaningful input from the team members expected to follow them often lack genuine buy-in, reducing the likelihood that they will actually be honored consistently in practice.