There are three Effort Modes available within Resources module. Those are:
- 'Original Estimate' Mode – if chosen the allocation is based on Original Estimate
- 'Remaining Estimate' Mode – if chosen the allocation is based on Remaining Estimate and Log Work
- 'Story Points' Mode – if chosen the allocation is based on Story Points
The Resources Effort Mode drop-down button can be easily spotted out on the Resource's header.
'Original Estimate' Mode
While this option is selected Original Estimate of a Task is being evenly distributed over Task's duration taking into account Resource's Workload Plan.
Let's have a look at Angela Hambleton's Task assignment as an example. She will help us understand how the things work.
Angela is assigned to 'EVIX-17' Task that is estimated to take 1w 2d which corresponds to 56h of her work.
As we can notice in the following screenshot Original Estimate of 'EXIV-17' is evenly distributed over 7d of this Task's duration.
It is a very simple calculation:
56h / 7d = 8.0h
Edge cases of 'Original Estimate' Mode:
If the Task does not have Original Estimate then the warning shows up (a red line that contours the Task) - considering 'Show warnings' feature is enabled
'Remaining Estimate' Mode
a) When work has not been logged
In case no work has been logged the allocation of the past days is being displayed as '0'. Those days are not being taken into account during the Effort calculation.
Starting from the current day (31 March) the allocation will be displayed as Remaining Estimate evenly distributed over the days that are left (remaining). In this case the math would be:
56h / 2d = 24.0h
b) When work has been logged
In this scenario the allocation of the past days will be displayed as Log Work (1w 1d = 6d = 48h of Angela's work) divided by the number of days that went by (based on the current day):
48h / 5d = 9.6h
Starting from the current day (31 March) the allocation will be displayed as Remaining Estimate evenly distributed over the days that are left (2 April and 3 April) meaning:
8h / 2d = 4.0h
Users may wonder why we decided not to display Log Work entries exactly as they were entered - for simplicity. Nothing prevents Users from logging their work on days that are outside of Start date - End date period of a Task.
If that is the case, how the add-on is supposed to know the way to display such entries? For instance:
The Task starts on 25 January but there are some Log Work entries on 20 January, or even in December. If the User displays only January in the Resource's Grid, the User simply misses out all the entries from December.
That is the main reason why we decided to sum all entries and divide them evenly over the past days, and we believe that this way the add-on may provide the User with a nice overview of what is the average effort put into the Task.
Edge cases of 'Remaining Estimate' Mode:
1) If the Task does not have Remaining Estimate then Original Estimate is used (if available)
2) If the Task is entirely in the future (Start date >= today) then only Remaining Estimate is shown (evenly distributed over Task's duration)
2.1) If there is no Log Work then the warning shows up - considering 'Show warnings' feature is enabled
3) If the Task is entirely in the past (today > end date) then we show only Log Work
'Story Points' mode
Angela estimated 'EVIX-17' Task to be accomplished in 7 Story Points as it is outlined in the screenshot below:
When this Effort Mode is chosen, the story is pretty same as when 'Original Estimate' Mode is selected. What means that the allocation is being evenly distributed over the Task's duration.
Considering the example below the math couldn't be more simple:
7 Story Points / 7d = 1.0 Story Point
Although Story Point velocity has been pre-defined globally (settings applied per all Programs) within Administration section (the User can find it under BigPicture drop-down menu on Jira's header) as shown in the first of the following screenshots, we allowed ourselves to overwrite this value for 'Objectively unleash extensive ideas' Program in its Configuration.
This option gives the User some flexibility when it comes to defining different Story Point velocity per Program.
Edge cases of 'Story Points' Mode:
If the Task does not have Story Point value then the warning shows up - considering 'Show warnings' option is selected
What the User should definitely remember is that selecting 'Show tasks from all Programs' feature while being in 'Story Points' Effort Mode may result in receiving misleading information regarding Resources' capacities and over/under allocations.
Above is possible because the same Resource may have different capacity expressed in Story Points depending on the Program (this in turn is possible because the capacity in Story Points is calculated based on Story Point velocity, which may have different value for each Program).
As the result while showing data from other Programs there might be different capacities in Story Points for each Resource to choose from. In such case the add-on always chooses capacity according to the current Program, but please keep in mind that this may lead the User to a false conclusion in regard to Resources' over/under allocation from other Programs.
Quick overview of Effort Modes:
|Effort Mode||How is the allocation being calculated?||Additional notes|
|Original Estimate||Based on Original Estimate - evenly distributed over Task's duration taking into account Resource's Workload Plan||Task have no Original Estimate - the warning is returned|
a) Work has been logged
Start date until yesterday - The allocation on the past days is displayed as '0'
Current date (today) to End date - The allocation on the remaining duration is displayed as Remaining Estimate evenly distributed over these days
b) Work has not been logged
Start date until yesterday - The allocation is displayed as Log Work evenly distributed over the past duration
Current date (today) to End date - The allocation is an even distribution of Remaining Estimate over the remaining duration
1) Task does not have Remaining Estimate value (--) then Original Estimate is used if available
2) Task is entirely in the future (Start date > = today) then only Remaining Estimate is shown (evenly distributed over Task's duration)
2.1) If there is no Log Work then the warning is returned
3) Task is entirely in the past (today > end date) then we show only Log Work
|Story Points||Based on Story Points - evenly distributed over Task's duration taking into account Resource's Workload Plan||Task have no Story Points - the warning is returned|