A working agreement is a small but powerful artifact: a set of shared behavioral expectations that the team writes for itself. When a team authors its own norms, self-organization gets stronger, because the rules belong to everyone instead of being handed down. The catch is that a working agreement only works if it's alive. Revisit it regularly, and always revisit it whenever the membership changes, because a new person didn't agree to anything they weren't there to shape.

Prompts for building one#

The blank-page problem is real, so I start a working-agreement session with prompts rather than an empty list:

• What's genuinely important to us as a team?
• What behaviors are we willing to commit to?
• What did the best teams we've each been on actually do?
• What are our working hours, and how do we prefer to reach each other?
• What makes a meeting successful for us?
• What mistakes do we want to make sure we avoid?

Those questions pull out norms people already hold but have never said aloud, and saying them aloud is most of the value.

Agreements that tend to earn their place#

Every team's list is its own, but a handful of agreements show up again and again because they work:

• Assume positive intent. Read the generous interpretation first.
• Pair every problem with a proposed solution. Raising an issue is fine; raising it with a suggested fix is better.
• Be transparent. Surface information rather than guarding it.
• Give constructive feedback. Specific, kind, and actionable.
• Join meetings on time. Respect for everyone else's hour.
• Enforce a WIP limit. Finish things before starting new ones.
• Surface blockers immediately. A blocker kept quiet is a blocker that costs the whole team.
• Keep the shared calendar current, so people can actually plan around each other.

The bookends of a story: Ready and Done#

Working agreements pair naturally with two definitions that bracket a story's lifecycle. A Definition of Ready says when a story is well-formed enough to start, and a Definition of Done says when it's truly finished. Together they're the bookends that keep work from starting half-baked or ending ambiguously.

The three C's of a story#

It helps to remember what a story even is. Ron Jeffries' three C's capture it well:

• Card — just enough written down to spark a conversation. The card is a promise to talk, not a spec.
• Conversation — the discussion of what's needed and why, where the real understanding forms.
• Confirmation — the acceptance criteria that tell you when it's satisfied.

A story that skips the conversation and tries to live entirely on the card is a story headed for rework.

Definition of Done is layered#

One nuance worth internalizing: Definition of Done isn't a single checklist. It's layered. There's a Done at the story level, a Done at the sprint level, and a Done at the increment level, each adding expectations the smaller unit doesn't carry. A story can be done without the increment being releasable, and conflating the two is a common source of "but I thought we finished that" friction.

Keep it living#

The failure mode for working agreements is the laminated poster nobody reads. The fix is treating the agreement as a living document the team returns to, especially when someone joins or leaves and the implicit context shifts. An agreement that gets revisited stays real. One that gets written once and forgotten was just a team-building exercise, not a working agreement at all.