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 (or just 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 voting stage 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:

Next step - select issues to be estimated, use filters to access required issues easily. Press 'Next' when all required issues are selected:

Then, select participants and share the session link with them. Use the copy option next to the link to share it via any messenger or send an invitation email. Please note, that the email invitation requires Jira contact emails of participants to be shared with the app, here you can find more details about it.

Once ready, click on 'Start async' to proceed:

Please note, that both the list of issues to be estimated and the list of participants can be adjusted afterward from the session menu by using the Estimate scope option:

Estimation process

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

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:

    • Skip - jumps to the following unestimated issue from the Backlog list, submitting no estimation from you for this issue;

    • Next - jumps to the following unestimated issue from the Backlog list saving selected estimation;

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

  • New area added for comments for a particular issue;

  • Backlog indicates value you selected for an issue;

Reviewing personal estimates

When all the participants have submitted their votes or when the time comes even if someone’s votes are missing, a moderator has to use the Review personal estimates option from the voting section or session menu:

Once it's done, Asynchronous mode switched to the interactive mode with all the issues having Reviewing status and ready for the final estimation.

Agile Poker will suggest a final estimation value if:

  • Consensus is selected in the settings and all the votes are similar;

  • Average is selected in the settings;

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

The moderator should use Save or Save&next options to save the final estimation 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 should use the Leave session option from the Session menu. In this case, the member is removed from the Participants list, his avatar is gone from the participants' area. This colleague can easily re-join the session later.

  • In the case of closing the tab, the user stays in the participant list and affects the estimation process: Final estimation process will not be automatically launched upon submitting all other votes.
  • If a person left the session, she or he can be removed from the Participants menu.
  • 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?

Now it's time to check Agile Poker for Cloud Session types: 

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

  • No labels

This page has no comments.