Skip to content

Getting Started — Joining a Session

As a developer, you join an estimation session created by your host.


  • A session code from your host (e.g. FUNKY-CAT-X2B9)
  • A web browser and a free account — no downloads
  1. Open TwoWeeks in your browser
  2. Click the Join a session tab
  3. Enter the session code your host shared with you
  4. Enter your display name (e.g. your first name)
  5. Click Join session

You’ll land in the session lobby. You’ll see who else is in the room.

When the host selects a ticket for estimation, you’ll see:

  • Ticket card — title and description of the ticket
  • Estimation tiles — colorful poker-chip buttons with values (e.g. 1, 2, 3, 5, 8, 13)
  • Timer bar (optional) — countdown showing time remaining to estimate
  • Vote counter — how many developers have submitted an estimate

Click a tile to submit your estimate. You can change your mind and click a different tile until the host locks estimates. Your current selection is highlighted.

If the host starts a timer, you’ll see a countdown bar. When time runs low, it turns yellow and then red with a pulsing animation. The host may lock estimates manually or let the timer auto-lock.

When the host locks estimates:

  1. A lock icon appears briefly
  2. All estimates are revealed with confetti
  3. You see the low, median, and high values
  4. Individual votes are shown per developer

The host decides what happens next:

  • Re-estimate — start a new round for the same ticket
  • Finalize — confirm the estimate and move on
  • Next ticket — skip to the next ticket

While the host decides, you’ll see a “Waiting for the host” message.

If you close your browser or lose connection, you can rejoin:

  • Open TwoWeeks again
  • Use the same session code and display name
  • If you rejoin from the same browser, your previous user token is stored and you’ll reconnect automatically

If you registered as a host, you can change your password from the account settings. See Accounts & Login for details on account management, password changes, and deactivation.

Developers sign in with their own account to join a session; only hosts need host access to create one.

  • Estimate based on complexity, not time — story points are relative
  • Don’t be afraid to pick the “wrong” value — discussion after reveal is healthy
  • The timer is there to keep things moving, not to stress you out (much)