methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session2-5 min per itemWorkshop or asyncRelative Estimates

Session: Planning Poker

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 3-9. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Relative Estimates. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    0-2 min: Present item

    2 min

    PO reads title, description, and acceptance criteria. Team asks clarifying questions. No solution discussion, no task breakdown in this phase. Hint: If basic questions are still unresolved after 2 min, return item to refinement. Estimation without clear scope produces garbage.

    FacilitatorRelative Estimates
  2. 2

    2-3 min: Estimate in secret

    1 min

    Each person selects a card from the Fibonacci scale in private. Participants submit values simultaneously. No one talks about their estimate. Hint: If someone shows or comments on their card before reveal, discard the round and restart. This preserves estimation integrity.

    FacilitatorAssumption Notes
  3. 3

    3-4 min: Reveal and inspect spread

    1 min

    Reveal cards simultaneously. If the spread is smaller than two Fibonacci steps (for example 3-5), take the higher value. Otherwise move to discussion. Hint: Consensus is not the goal; sufficient alignment is enough. Anyone hardening on one value blocks refinement.

    FacilitatorSplit Candidates
  4. 4

    4-7 min: Discuss divergence

    3 min

    Highest and lowest estimators explain assumptions without justifying. Others add risks or assumptions. Then estimate privately again. Hint: Timebox discussion strictly. After at most two rounds, either park or split. Endless estimation debates are a signal of unclear requirements.

    OwnerRelative Estimates
  5. 5

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerRelative Estimates
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Planning Poker

Goal

Artifact: Relative Estimates

Working Question

How large is this item relative to our reference stories, and which assumptions or risks drive variance within the group?

Context

Backlog items sorted by priority; acceptance criteria per item; definition of done; reference stories with assigned point values; known dependencies and risks.

Setup

  • Format: Method session
  • Duration: 2-5 min per item
  • Mode: Workshop or async
  • Participants: One facilitator (Scrum Master or PO proxy); one Product Owner as item presenter; the delivery team implementing the work (3-9 people); optionally one QA or design participant who also estimates.
  • Owner: One facilitator (Scrum Master or PO proxy)
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Relative Estimates. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Planning poker cards (physical or a tool such as PlanningPokerOnline, Scrum Poker, Miro plugin); open backlog in ticket system; timer; visible list of reference stories; low-noise environment or calm call channel.

Preparation

Set max number of items per session (experience baseline: 6-12 in 60 minutes). Announce timeboxes: 2 min clarification, 1 min estimation, 3 min discussion for deviations. Ensure cards or tool is available for everyone.

Agenda

  1. 0-2 min: Present item (2 min) Owner: Facilitator Action: PO reads title, description, and acceptance criteria. Team asks clarifying questions. No solution discussion, no task breakdown in this phase. Hint: If basic questions are still unresolved after 2 min, return item to refinement. Estimation without clear scope produces garbage. Output: Relative Estimates

  2. 2-3 min: Estimate in secret (1 min) Owner: Facilitator Action: Each person selects a card from the Fibonacci scale in private. Participants submit values simultaneously. No one talks about their estimate. Hint: If someone shows or comments on their card before reveal, discard the round and restart. This preserves estimation integrity. Output: Assumption Notes

  3. 3-4 min: Reveal and inspect spread (1 min) Owner: Facilitator Action: Reveal cards simultaneously. If the spread is smaller than two Fibonacci steps (for example 3-5), take the higher value. Otherwise move to discussion. Hint: Consensus is not the goal; sufficient alignment is enough. Anyone hardening on one value blocks refinement. Output: Split Candidates

  4. 4-7 min: Discuss divergence (3 min) Owner: Owner Action: Highest and lowest estimators explain assumptions without justifying. Others add risks or assumptions. Then estimate privately again. Hint: Timebox discussion strictly. After at most two rounds, either park or split. Endless estimation debates are a signal of unclear requirements. Output: Relative Estimates

  5. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Relative Estimates

Closeout

  • Update result artifact: Relative Estimates
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Relative Estimates: Planning Poker

Working Question

How large is this item relative to our reference stories, and which assumptions or risks drive variance within the group?

Context

Backlog items sorted by priority; acceptance criteria per item; definition of done; reference stories with assigned point values; known dependencies and risks.

Participants

  • Owner: One facilitator (Scrum Master or PO proxy)
  • Participants: One facilitator (Scrum Master or PO proxy); one Product Owner as item presenter; the delivery team implementing the work (3-9 people); optionally one QA or design participant who also estimates.

Input

Planning poker cards (physical or a tool such as PlanningPokerOnline, Scrum Poker, Miro plugin); open backlog in ticket system; timer; visible list of reference stories; low-noise environment or calm call channel.

Template

Planning Poker Working Template

Goal

Collaborative estimation method where team members choose cards privately and discuss differences.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Relative Estimates:
  • Assumption Notes:
  • Split Candidates:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Relative Estimates is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Planning Poker Working Template

View templateCompact working template for Planning Poker with context, input, output artifacts, and next step.
markdown

planning-poker-working-template.md

Compact working template for Planning Poker with context, input, output artifacts, and next step.

Planning Poker Working Template

Goal

Collaborative estimation method where team members choose cards privately and discuss differences.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Relative Estimates:
  • Assumption Notes:
  • Split Candidates:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Relative Estimates.
  • Keep estimates on the item. For re-estimation after scope change, document in comment thread without overwriting silently. Keep assumptions and risks as item comments.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet