...

• a team calculates effort based on several estimations, like:
  • development and QA activities
  • frontend and backend estimates
  • research and development
  • The most pessimistic, the most optimistic, the most likely estimates (as a part of PERT estimate); 
• a team uses both Story Points and Time estimates for planning;
• a team uses a calculated value for work prioritization, using one the following frameworks:
  • WSJF
  • ICE
  • RISE
  • Impact/Ability
• when estimates for several numeric fields are required.

...

Creating multi-field session

Overview

Before starting a multi-field estimation session, you must select a Jira field for every estimation value, as well as for the final score (if you opted to use it). Since Agile Poker operates with existing Jira fields, you need to specify fields for estimation even if your goal is to get a single final score field updated.

In order to create a multi-field estimation session, navigate to Agile Poker from a selected board and click on Create session under Interactive or Asynchronous sessions: 

Turn ON the Multi-field estimation toggle to configure the multi-field session:

Templates

Once the multi-field toggle is activated, the multi-field estimation configuration appears below so you can select a template for estimation/prioritization. By default, the Custom template is selected.

The Custom template is weighted sum formula that allows the estimation from 2 to 5 numeric fields. Use "Add criteria" and Remove (the bucket) options to control the number of fields to estimate. Note that all the field selectors are mandatory, and you will be able to proceed to the next step only when all of them are selected.

Prioritization templates support specific prioritization frameworks. Estimation fields are labeled with framework criteria names, and the number of fields is predefined. The supported frameworks are:

• WSJF - Weighted Shortest Job First
• ICE - Impact, Confidence, and Ease
• RISE - Reach, Impact, Confidence, and Effort
• Impact/Ability or Impact/Effort

...

In the session, it will look like this:

Time estimates

Since Jira doesn't provide a way to create custom fields of time type, the time estimates will be combined with numeric fields estimation on Multi-field estimation. So, for example, if you need to sum up DevEstimate (numeric field) with QAEstimate (numeric field) to get a final estimate saved in the Original estimate (time field), we recommend the following approach: 

1. Find out your Default unit for time tracking from Jira → Settings → Issues → Issue features → Time tracking (it might be Minute, Hour, Day, or Week)
2. Use Agile Poker's ability to label estimation values: use the format of "label=value"
3. Combine #1 and #2 to create an estimation layout. For example, for Minutes as the default unit for time tracking:

...

Such a format will align with the standard Jira's time format and make time estimation easier for Agile Poker users. 

Please note that estimating Time format values is also available from 100.4.2 version. Use values like "1w" for 1 week, "1d" for 1 day, "1h" for 1 hour", "1m" for one minuter, or their combination like "1w 2d 3h 4m". You can also choose Time estimates template:

 Image Added

Session scope

You'll be able to estimate only those issues that support all of the selected estimation fields. If, for example, a specific issue type is missing at least one of the selected estimation fields, it won't appear in Agile Poker's Multi-field estimation session.

...

During the final estimation phase of both the Interactive and Async sessions, participants can see a grid with all the personal estimates. To see it you must click on the grid view icon next to the participants: