methodatlas
Session Builder

Plan my session

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

Method session15-60 minWorkshop or asyncIdeal Day Estimates

Session: Ideal Days

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

  1. 1

    Phase 1: Sharpen definition and references

    10 min

    Review the Ideal Day definition together. Review reference items with values and adjust where needed. Record team consensus. Hint: If someone says "my ideal day is 6 h, I have kids", the definition is too personal. Ideal Day is a methodological unit, not a real working day.

    FacilitatorIdeal Day Estimates
  2. 2

    Phase 2: Estimate items

    20-30 min

    Estimate items in ideal days as a team. Discuss large differences similarly to planning poker. Document assumptions (for example, "uses existing library X"). Hint: If an item is larger than 5 ideal days, split it or run a spike first. Larger values are not reliable because assumption variability becomes too high.

    FacilitatorAssumption Notes
  3. 3

    Phase 3: Record dependencies and caveats

    10-15 min

    For each item, make dependencies that could inflate calendar time explicit. Record caveats (for example, "requires review from external team", "compliance approval required"). Hint: Ideal days without caveats are converted into calendar days. Caveats are a methodological safeguard against misinterpretation.

    FacilitatorCapacity Caveats
  4. 4

    Phase 4: Apply calendar time factor

    5-10 min

    For planning, translate Ideal Days into calendar time with an empirical factor (typically 1.5-3x). Derive the factor from team history and communicate a range rather than a single number. Hint: If no historical factor exists, start with 2x as a conservative default and calibrate after 2-3 sprints. The factor is team-specific and changes with organizational context.

    OwnerIdeal Day Estimates
  5. 5

    Publish artifact

    10 min

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

    OwnerIdeal Day Estimates
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Ideal Days

Goal

Artifact: Ideal Day Estimates

Working Question

How many ideal days are needed for this item under focused work, and what assumptions about interruptions, dependencies, and uncertainty are made?

Context

Item list with acceptance criteria; Ideal Day definition (for example "8 h of focused work with no meetings, waiting, context switching"); two to three reference items from real delivery history with Ideal Day values.

Setup

  • Format: Method session
  • Duration: 15-60 min
  • Mode: Workshop or async
  • Participants: One facilitator who keeps the definition consistent and collects values; the implementing team (2-9 people); a scribe for assumptions and caveats; optionally a PO for scope clarification.
  • Owner: One facilitator who keeps the definition consistent and collects values
  • 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 Ideal Day Estimates. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Estimation sheet with columns Item, Ideal Days, assumptions, dependencies; visible "Ideal Day" definition; list of reference items with Ideal Day values; timer.

Preparation

Post the Ideal Day definition at the wall: "One day of focused work, no interruptions, no meetings, no blockers." Make reference items with values visible. Note that Ideal Day ≠ calendar day.

Agenda

  1. Phase 1: Sharpen definition and references (10 min) Owner: Facilitator Action: Review the Ideal Day definition together. Review reference items with values and adjust where needed. Record team consensus. Hint: If someone says "my ideal day is 6 h, I have kids", the definition is too personal. Ideal Day is a methodological unit, not a real working day. Output: Ideal Day Estimates

  2. Phase 2: Estimate items (20-30 min) Owner: Facilitator Action: Estimate items in ideal days as a team. Discuss large differences similarly to planning poker. Document assumptions (for example, "uses existing library X"). Hint: If an item is larger than 5 ideal days, split it or run a spike first. Larger values are not reliable because assumption variability becomes too high. Output: Assumption Notes

  3. Phase 3: Record dependencies and caveats (10-15 min) Owner: Facilitator Action: For each item, make dependencies that could inflate calendar time explicit. Record caveats (for example, "requires review from external team", "compliance approval required"). Hint: Ideal days without caveats are converted into calendar days. Caveats are a methodological safeguard against misinterpretation. Output: Capacity Caveats

  4. Phase 4: Apply calendar time factor (5-10 min) Owner: Owner Action: For planning, translate Ideal Days into calendar time with an empirical factor (typically 1.5-3x). Derive the factor from team history and communicate a range rather than a single number. Hint: If no historical factor exists, start with 2x as a conservative default and calibrate after 2-3 sprints. The factor is team-specific and changes with organizational context. Output: Ideal Day 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: Ideal Day Estimates

Closeout

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

Ideal Day Estimates: Ideal Days

Working Question

How many ideal days are needed for this item under focused work, and what assumptions about interruptions, dependencies, and uncertainty are made?

Context

Item list with acceptance criteria; Ideal Day definition (for example "8 h of focused work with no meetings, waiting, context switching"); two to three reference items from real delivery history with Ideal Day values.

Participants

  • Owner: One facilitator who keeps the definition consistent and collects values
  • Participants: One facilitator who keeps the definition consistent and collects values; the implementing team (2-9 people); a scribe for assumptions and caveats; optionally a PO for scope clarification.

Input

Estimation sheet with columns Item, Ideal Days, assumptions, dependencies; visible "Ideal Day" definition; list of reference items with Ideal Day values; timer.

Template

Ideal Days Working Template

Goal

Estimates work in idealized work days without interruptions, meetings, or waiting time.

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

  • Ideal Day Estimates:
  • Assumption Notes:
  • Capacity Caveats:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

Completion Check

  • Ideal Day 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

Ideal Days Working Template

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

ideal-days-working-template.md

Compact working template for Ideal Days with context, input, output artifacts, and next step.

Ideal Days Working Template

Goal

Estimates work in idealized work days without interruptions, meetings, or waiting time.

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

  • Ideal Day Estimates:
  • Assumption Notes:
  • Capacity Caveats:

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 Ideal Day Estimates.
  • Keep Ideal Day values per item. Preserve old values as comments on re-estimations. Maintain the calendar-time factor centrally, with evidence from history (for example last 5 items with Ideal Day estimate and actual delivery time).
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet