Introduction

Multi-field estimation feature is available in Interactive and Asynchronous sessions. It allows estimating several Jira fields at once and, optionally, calculating a final value (called "final score") based on those estimates.

The most common cases for using the feature are the following: 

• 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

Final score

In most cases, the outcome of a multi-field estimation is not the estimates themselves, but rather a final value calculated based on those estimates. That is why there is an optional Final score feature that can be used to store the final result.

The final score is saved to a selected Jira field, and that's why once it is enabled, it is mandatory to specify a corresponding Jira field.

Each template has a preset formula: for the Custom template it is a weighted sum, for ICE it is I*C*E, and so on. 

Each field has an alphabetic identification: A, B, C, D, or E, that is used in the final score formula: 

You can multiply a value by changing its weight on the Custom and WSJF prioritization templates:

Estimation values

Estimation values that are suggested during estimation for all the fields are configured below the multi-field configurations. Currently there is no way to set up different estimation values (or cards layouts) for different fields:

If you need to have different estimation values for different fields, consider the following approaches:

1. You can change the Estimation values from inside the session. For example, for the Interactive session, you can estimate field #1 first, then change the estimation values and proceed with estimates for field #2.
2. You can have several sets of values at once, like this: 

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:

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.

Check the detailed guide on this topic.

Saving configuration as personal default

Multi-field estimation configuration can be saved and pre-populated during the next session creation by using the "Save this configuration as my personal default" option:

Session flow

The Multi-field session flow is pretty similar to the standard Interactive and Asynchronous sessions' flows. The main difference is that a field, not an issue, becomes an estimation focus. It means that:

• each issue has several tabs with the estimation fields;
• pressing "Save and next" takes to the next field, not to the next issue;
• triangulation and reference issues show values for the selected estimation field;
• during the personal estimation phase of the Async session, the personal progress is tracked based on the number of fields submitted; 
• each estimation field for each issue has its own comment field in the Async session;
• the backlog view now shows 2 types of values: 
  • a final score if it's enabled for the Interactive session and Final estimation phase of the Asynchronous session;
  • estimates for all the estimation fields during the personal estimation phase of the Asynchronous session or in all the cases if the final score is disabled;
    Note that a session moderator can navigate to any tab (field) of any issue by clicking on the corresponding field from the backlog.

In case the final score is enabled for the Multi-field estimation session, it will be shown on the right to the estimation field tabs:

Whenever all the criteria of the final score formula are estimated, the final score will be calculated, shown to all of the participants, and saved to the corresponding Jira field. It will be automatically recalculated upon further changes of the estimates in Agile Poker. In case you are interested in automatic field re-calculation outside Agile Poker in Jira please check Automating final score calculation outside Agile Poker page for the instruction.

Note that if the final score formula contains a denominator, like in the case of WSJF or Impact/Ability templates, it has to be a non zero numeric value so that the final score can be calculated. 

Grid view

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: