Child pages
  • Asynchronous session


Agile Poker Cloud

This part of the documentation relates to Agile Poker for Jira Cloud. If you use Jira Server go to the Agile Poker for Jira Server documentation.


Asynchronous (shortly: Async) session is designed for teams that can't or don't want to estimate simultaneously, but also it is widely used by teams who want all members to check out the estimation scope and put questions before the joint team estimation. The flow for asynchronous sessions is based on the Wideband Delphi estimation method:

  1. The session moderator selects the issues to estimate and people that will participate in the session.

  2. The session link is shared with all the participants.

  3. Participants estimate issues in the scope of the estimation session whenever they find it convenient, optionally putting down their comments, questions, and concerns to support the chosen estimation.

  4. Moderator closes the personal estimation phase and proceeds to the final estimation phase.

  5. The session moderator saves the estimates for issues in scope based on the estimation result or proceeds with further discussion interactively.

Starting and configuring Asynchronous session

Asynchronous session is started from the Session selection page of Agile Poker, check out Navigation for Classic and Next-Gen projects instructions to find out how to get here:

3-steps wizard will be shown next, and the following information should be provided:

  • Session name
  • Session type: public or private, see Public vs. Private sessions for the details
  • Estimation values: choose one of the commonly used sets of estimation values, like Fibonacci sequence, Modified Fibonacci, T-shirt sizes, SML (mini T-shirt sizes), or use any custom set your team prefers.
    Although the estimation field must be numeric, you can display a string for voting values, just use the following format of a string equals a number: “Small=1”

  • Timer values: during the estimation session, a moderator might launch a timer to limit discussion or voting time. This is the place where timer options are configured.

  • Suggested estimate: Select what suggested estimate you will see once all voles are done: Consensus, Average, or Average Integer

  • Session participants: a moderator who controls an estimation session flow, and participants who provide estimates
  • Select issues to be estimated, use JQL filter to access required issues easily

Once ready, click on 'Start session' to proceed.

There is a possibility to send email notification to session participants and invite them to Async session. This option will be available at "Manage participants" session creation step, only in case if session moderator is set to a single person, and that person has public email visibility configured in Jira. Check How to configure Jira+Cloud+to+send+Agile+Poker+session+notifications for details.

Session configuration can be updated after it was started from the session's menu - check out Participants and Estimate scope options:

Estimation process

In Async session, every participant should solely estimate all provided issues optionally writing down comments backing up the estimate.

The asynchronous estimation process is pretty similar to Interactive estimation, but with several differences:

  • Participants section has an ASYNCHRONOUS MODE indicator, avatars have a progress icon, that changes to a checkmark once a team member finished his or her estimations;

  • Your estimation for Story Points part has the following options:

    • Skip - jump to the next un-estimated issue from the issue list, submitting no estimate from you for this particular issue;

    • Next - jump to the next un-estimated issue from the issue list saving a selected estimation option;

    • Finish & Review - for moderators only, proceed to the Final estimation stage even if some of the participants have not submitted estimations; it is highlighted is all the participants finished their estimations;

  • New area added for a comment for a particular issue;

  • Estimated value you selected for an issue will appear in the issue list.

Reviewing personal estimates

When all the participants have submitted their estimates or when the time is over then even if some participants' estimates are missing, a moderator has to chose the Review personal estimates option from the voting section or session menu:

Once it's done, Asynchronous mode will switch into the Interactive mode with all the issues set to Reviewing status and ready for the final estimation.

Agile Poker will suggest a final estimation value if:

  • Consensus option was selected in the settings and all the estimates are similar;

  • Average option was selected in the settings;

All the comments are also shown here. All saved individual estimates might be removed now, use the Reset button on the right.

The moderator should use Save or Save & next options to save the final estimate and proceed further. Once all the issues are estimated, you’re done!

Leaving and finishing the session

  • When a team member steps out of the estimation process, he/she should use the Leave session option from the session menu. In this case, the member is removed from the Participants list, their avatar is gone from the participants' area. This colleague can re-join the public session later. But in order to join a private session a moderator has to re-invite the user.

  • In case of closing the browser's window, the user remains a session participant. That has a direct impact on estimation process: Final estimation process will not be automatically launched upon submitting estimates by other participants.
  • If a person left the session, she or he can be removed from the Participants menu (for private sessions: only a moderator can do that!)
  • In case all issues have been estimated, a moderator can finish the session for all participants by using the Finish session option:

What's next?

Check out other estimation sessions offered by Agile Poker for Cloud: 

Please let us know if this article was helpful, your feedback is appreciated:

  • No labels

This page has no comments.