methodatlas
Session Builder

Establish practice

Define cadence, owner, participation, and success signals for a recurring team practice.

Practice CharterweeklyOperating practice

Establish the practice

Define cadence, owner, participation, and success signals so the method works as a recurring team practice.

Derived automatically

Variant for Operating practice. The plan is derived from method form, method steps, and runsheet.

Runsheet
Cadence logic
Rhythm before scope

An operating practice works through repetition. The cadence should be small enough to hold reliably.

Iteration flow
One run, reusable each time

The steps describe one repetition and are adjusted after review.

  1. 1

    Phase 1: Collect context and expectations

    15-20 min

    Facilitator describes context. Solo phase: every person writes at least three expectations and one observation. Place in Expectation column.

    OwnerSolo writing prevents dominance by loud voices. Observations are often more concrete and honest than general expectations.
  2. 2

    Phase 2: Formulate proposals

    20-30 min

    Cluster expectations. Formulate one rule proposal per cluster. Concrete, observable, checkable.

    TeamAvoid negative rules. Prefer "We start standup on time even if not all are there".
  3. 3

    Phase 3: Discussion and commitment

    15-25 min

    Discuss per proposal: livable, important? Dot-vote to max 7-10 rules. Rephrase or discard contested rules.

    TeamCommitment is not majority vote. If one person cannot carry a rule, rephrase or leave it out.
  4. 4

    Phase 4: Review cadence and ownership

    5-15 min

    Define who monitors agreements, when they are reviewed, where they are visible, and what happens on repeated break.

    TeamAgreements without review become wallpaper. Check at least once per retro.
Usable artifact

Practice Charter

Copyable charter with purpose, cadence, owner, participation, flow, success signals, and review.

practice-charter.md

Practice Charter: Working Agreements

Purpose

The method helps clarify backlog, sprint work, and team flow concretely. It sorts work by value, risk, and delivery fit. The result is captured as working agreements, team norms, and a review cadence.

Cadence

weekly

Owner and Participation

  • Owner: open
  • Participants: 3-12
  • Mode: synchronous

Flow per Iteration

  1. Phase 1: Collect context and expectations (15-20 min) Facilitator describes context. Solo phase: every person writes at least three expectations and one observation. Place in Expectation column.
  2. Phase 2: Formulate proposals (20-30 min) Cluster expectations. Formulate one rule proposal per cluster. Concrete, observable, checkable.
  3. Phase 3: Discussion and commitment (15-25 min) Discuss per proposal: livable, important? Dot-vote to max 7-10 rules. Rephrase or discard contested rules.
  4. Phase 4: Review cadence and ownership (5-15 min) Define who monitors agreements, when they are reviewed, where they are visible, and what happens on repeated break.

Success Signals

Working Agreements, Team Norms, Review Cadence

Review

4 weeks