methodatlas
Session Builder

Plan my session

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

Method session1-5 min per item, typically 60-90 min for refinement sessionWorkshop or asyncPoint Estimates

Session: Story Points

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 Point Estimates. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Calibrate reference stories

    10 min

    Walk through reference stories per point value. Team confirms or corrects. New team members get explanation for each value. Hint: Without calibration, points are meaningless within team. When team changes (>30% new), reset references instead of keeping old ones.

    FacilitatorPoint Estimates
  2. 2

    Phase 2: Item estimation

    2-5 min per item

    Present item, clarify questions, estimate (Planning Poker or direct). Points refer to relative size against reference, not hours. Hint: If someone asks "how many hours is that?", method was not understood. Explain patiently: points are relative complexity unit, velocity later enables forecasting.

    FacilitatorReference Stories
  3. 3

    Phase 3: Split large items

    5-10 min per item

    Mark items with 13+ points as splitting candidates. For each item, define proposal with owner and deadline. Items over 20 points do not enter sprint without split. Hint: Large points are not wrong, but risky. Splitting reduces uncertainty and enables finer velocity forecast. If team cannot split, solution understanding is unclear.

    FacilitatorVelocity Data
  4. 4

    Phase 4: Velocity evaluation

    10 min

    After sprint end, document completed points per sprint. Use velocity of last 3-5 sprints as range (for example "22-31 points/sprint"). Forecast with this range, not with average. Hint: Velocity is team-internal. Never use it to compare teams, otherwise points inflate. Recalibrate velocity trend after team change or tech migration.

    OwnerPoint Estimates
  5. 5

    Publish artifact

    10 min

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

    OwnerPoint Estimates
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Story Points

Goal

Artifact: Point Estimates

Working Question

How large is this item relative to our reference stories, considering scope, complexity, risk and uncertainty?

Context

Reference stories from real delivery history with assigned points; shared scale definition (for example "1 = trivial, 13 = larger story under splitting suspicion"); Definition of Done.

Setup

  • Format: Method session
  • Duration: 1-5 min per item, typically 60-90 min for refinement session
  • Mode: Workshop or async
  • Participants: One moderator (Scrum Master or Tech Lead); one Product Owner for scope; implementing team (3-9 people); one scribe for assumptions if needed.
  • Owner: One moderator (Scrum Master or Tech Lead)
  • 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 Point Estimates. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Estimation tool (Planning Poker, Miro, Linear/Jira with Story Point field); visible reference-story list; scale poster (typically Fibonacci 1, 2, 3, 5, 8, 13, 20); backlog items with description and criteria.

Preparation

Reference stories visible as anchors on wall or board (for example "3 = SSO Google, 5 = API endpoint client export, 8 = self-service portal slice"). Scale poster. State rule: points include scope, complexity, risk and uncertainty, not only time.

Agenda

  1. Phase 1: Calibrate reference stories (10 min) Owner: Facilitator Action: Walk through reference stories per point value. Team confirms or corrects. New team members get explanation for each value. Hint: Without calibration, points are meaningless within team. When team changes (>30% new), reset references instead of keeping old ones. Output: Point Estimates

  2. Phase 2: Item estimation (2-5 min per item) Owner: Facilitator Action: Present item, clarify questions, estimate (Planning Poker or direct). Points refer to relative size against reference, not hours. Hint: If someone asks "how many hours is that?", method was not understood. Explain patiently: points are relative complexity unit, velocity later enables forecasting. Output: Reference Stories

  3. Phase 3: Split large items (5-10 min per item) Owner: Facilitator Action: Mark items with 13+ points as splitting candidates. For each item, define proposal with owner and deadline. Items over 20 points do not enter sprint without split. Hint: Large points are not wrong, but risky. Splitting reduces uncertainty and enables finer velocity forecast. If team cannot split, solution understanding is unclear. Output: Velocity Data

  4. Phase 4: Velocity evaluation (10 min) Owner: Owner Action: After sprint end, document completed points per sprint. Use velocity of last 3-5 sprints as range (for example "22-31 points/sprint"). Forecast with this range, not with average. Hint: Velocity is team-internal. Never use it to compare teams, otherwise points inflate. Recalibrate velocity trend after team change or tech migration. Output: Point 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: Point Estimates

Closeout

  • Update result artifact: Point 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

Point Estimates: Story Points

Working Question

How large is this item relative to our reference stories, considering scope, complexity, risk and uncertainty?

Context

Reference stories from real delivery history with assigned points; shared scale definition (for example "1 = trivial, 13 = larger story under splitting suspicion"); Definition of Done.

Participants

  • Owner: One moderator (Scrum Master or Tech Lead)
  • Participants: One moderator (Scrum Master or Tech Lead); one Product Owner for scope; implementing team (3-9 people); one scribe for assumptions if needed.

Input

Estimation tool (Planning Poker, Miro, Linear/Jira with Story Point field); visible reference-story list; scale poster (typically Fibonacci 1, 2, 3, 5, 8, 13, 20); backlog items with description and criteria.

Template

Story Points Working Template

Goal

Relative unit for estimating scope, complexity, risk, and uncertainty of backlog items.

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

  • Point Estimates:
  • Reference Stories:
  • Velocity Data:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Point 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

Story Points Working Template

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

story-points-working-template.md

Compact working template for Story Points with context, input, output artifacts, and next step.

Story Points Working Template

Goal

Relative unit for estimating scope, complexity, risk, and uncertainty of backlog items.

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

  • Point Estimates:
  • Reference Stories:
  • Velocity Data:

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 Point Estimates.
  • Story Points maintained per item. Re-estimation as comment with date and reason. Velocity history as sprint log with point sum and sprint date. Reference-story list with change date.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet